Yep that’s my exact problem.
It's my understanding that the roll back versions available are the last release of any major version which is available via the endpoint listed in a previous post by @lpakula or the versions that are still stored on your hub. If you were in the beta and .138 is still on your hub, you can roll back to it. If you were in the beta and .138 is no longer on your hub, then you are SOL just like those of us that weren't in the beta. I'm sure they will figure it out next week and those of us not in the beta that rolled back to 2.3.9 will be back to playing with the new UI.
1 Like
Similar. We were gone and came back and I couldn't get either of ours to update for a good bit. I have a virtual switch of "everyone" gone so I could override my automations. Manually forcing an update wouldn't work. Just eventually went on it's own.
There is a way to select versions directly when they are no longer displayed. I remember seeing it on the beta forum when someone asked. Let me see if I can find that thread.
1 Like
If you're having the issue with OwnTracks on 2.4.0, can you send me the hub ids?
For those participating in beta, can you confirm that 2.4.0.138 is the last version that didn't have this issue?
4 Likes
Yes that is correct. .138 was the last version that is working properly for me.
4 Likes
I just now updated my Hubitat platform to 2.4.0.144 from 2.3.9.x and then went into Hubitat Package Manager and noticed an update pending for Owntracks to 1.8.9 which seems to be some major change as the update is noted as "Changed app to single threaded".
However, when checking this post for reported issues with OT updates, as I typically do, I saw there seems to be some major problems with the latest Hubitat release and OT. I do not seem to be experiencing any of these problems, as I can find no errors in logs.
My question is @lpakula: Should I update OT to 1.8.9 or keep my current version at 1.8.7 (my gut feeling)?
The issue others are experiencing has nothing to do with the OT changes -- there is no risk in updating to this version. This was happening on 1.8.7 as well if you have devices reporting a high number of locations per hour.
1 Like
Hi @lpakula,
Season’s greetings! 
.
I’ve definitely noticed that OwnTracks has been trudging along like a reindeer stuck in a snowdrift since the recent Hubitat updates. 
Case in point: my wife arrived home, settled in, and probably had time to contemplate life’s mysteries before I got the notification saying she was home. On top of that, my maps are lagging so much they might as well be hand-drawn by a cartographer on vacation. 
This is pretty unfortunate because my wife had me set up a bunch of automations based on location, and now none of them are firing at the correct time. Let’s just say my "automation genius" status is under review at home. 
Do you happen to know if Hubitat has been looking into this and whether there’s a solution in sight?
For reference, I’m running OwnTracks version 1.8.9 and Hubitat version 2.4.0.144. Fingers crossed there’s light at the end of this slow-moving tunnel! 
Cheers,
David
2 Likes
Yes, gopher.ny is aware. If you PM him your Hub ID, that would be helpful for them to troubleshoot.
2 Likes
Not sure that's possible.
I believe the hub only keeps 3 versions stored and there's no direct endpoints available for specific levels, so if you don't have 2.4.0.138, you're SOL.
3 Likes
I'm on the latest HE build and since updating I'm seeing this in the logs.
I don't think there are any issues but just thought I'd report it just in case there is something awry.
[app:12661](http://192.168.0.24/logs#)2024-12-28 20:36:23.981infoOwnTracks: Location update for user Gill is 12 minutes old. Skipping presence update.
For me it was. I first reported the issue to @lpakula
Just to confirm - you sent your hub's UID to Victor?
1 Like
No, just go back from vacation and saw the request but not fully processed. ;0
Will do.
1 Like
Wait - we're allowed to take vacation when there is a new release?! Did not know that... 
1 Like
Ha, it's if you're over 65. Not worth getting here for time off. 
I got home and my OT phones didn't trip the I'm Back.
I rebooted on .138 and Now I get a present:
dev:21382024-12-28 13:52:37.024errorcom.hubitat.app.exception.LimitExceededException: App 1633 generates excessive hub load on line 443 (method generatePresenceEvent)
dev:21422024-12-28 13:48:12.296errorcom.hubitat.app.exception.LimitExceededException: App 1633 generates excessive hub load on line 443 (method generatePresenceEvent)
app:17632024-12-28 13:26:33.242warn ║ Hub Event! Device: HomeC8 - Severe hub CPU load detected - Sat, Dec 28 2024 @ 1:26:33 PM PST
sent mine if it helps
2 Likes
I updated my C7 today to 2.4.0.144 and on my latest trip shortly after I am receiving this error on my 3 phones devices using OT. Hubitat is not recognizing that I am home.
Yes. You have to revert to 138 if you're a beta tester. This is the last know working version until a fix is in place.
