Was that installed from the Hubitat package manager? Can you to update again?
I did miss up-reving the driver version which probably caused this. There were breaking changes in the names that its complaining about between the app and driver.
Sorry fr the delay.
HPM updated at 10:00 PST and no log errors so far.
All good.
1 Like
It should be fine now. If you look at the member devices, they should all show 1.8.14 as the version.
Been getting these all day regardless of whether I'm home or away, Lyle. No changes to any of my settings. Our arrival home after being on all day was correctly tracked/reported.
Do you have it sending data to the recorder or secondary hub? That is usually it not responding.
What do you set your device "to many thresholds" to? It's on the device info tab:
Yes, Recorder is set up. Thanks, I'll go look at that...
OK, looks like some idiot (and I think we all know who!) shut down the Pi running Recorder when he was troubleshooting an unrelated issue, and forgot to start the Pi up again.
Thanks...I'm off to sit in the (way too familiar) doofus corner. 
4 Likes
I'm not sure if I can keep you company.
My logs are set to 500, too little? Changed to 1K.
Normally I don't get any load message at that setting.
2 Likes
That would do it. Nice easy fix though! 
1 Like
How do you get to this intermediate state?
The person has left home, the LAT and LON data point to a region that is not home. The icon is red, the distance from home is significant, the status is "departed", the presence is "not present", and yet the Location is "Koti" which means home in Finnish.
Is that running the latest version? Anything in the logs around that time?
Latest version yes. Nothing unusual in log ;(
No worries, let me check to see what might have happened there.
Looks like the official OwnTracks got a bump to 2.5.6 this morning with a couple of potentially good updates. Less battery drain during poor connections being one. Will you be updating your fork @lpakula?
<insert comical comment from @danabw here about a spork> 
1 Like
Let me check. If they just pulled in the PR I have up the fork would basically equal the Google release.
Are you seeing the transition region changing? I'm wondering if I broke something there....
I just updated and I saw this in the logs:
app:29052026-03-02 06:49:46.511 PM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_app_lpakula_OwnTracks_1270.getSmallUnits() is applicable for argument types: () values:
Possible solutions: smallUnits() (getSmallUnits)
app:29052026-03-02 06:49:46.457 PM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_app_lpakula_OwnTracks_1270.getVelocityUnits() is applicable for argument types: () values:
Possible solutions: velocityUnits() (getVelocityUnits)
app:29052026-03-02 06:49:46.367 PM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_app_lpakula_OwnTracks_1270.getLargeUnits() is applicable for argument types: () values:
Possible solutions: largeUnits() (getLargeUnits)
Can you check what the driver version is showing for a member? It should be 1.8.14. If you do a "repair" it would fix it, but I'd like to confirm the version first.
