I did a little more digging. I still think that the events are reporting correctly for both iOS and Android, at least for me.
If I click on the member location map links in the Owntracks HE app the maps display. It seems to be some issue with the members location attribute used for the dashboard. I could fix it by using the links in Iframes but will hold off and see if what we have been using can be fixed.
What I've noticed in the last week or more is that the tile always seems to be one location update behind. If we go out for a walk and get back one hour later, the tile seems to be showing the location of the last update just before we arrive at home (about 350 metres away). Once home we're not moving so there are no further updates (as we're stationary) so we're never 'Present' unless I manually update it once home.
Just an update
Since rolling back to a pervious working version other than .143
Since leaving the house today
Android and ios
Everything in regards to OT is working again
Could you be specific as to what version you rolled back to? Beta testers may have had potentially many versions between the one that is now working for you, and .143.
It isn't clear to me that we are all talking about the same issue. I'm not getting and errors in the log but location updates have been very sluggish (15-90 minutes behind, I might guess).
I Restored version 2.3.9.201
So to give a little time-line
I downlaoded uploaded .143 yesterday afternoon
We got home from relatives house around 5pm
Android presence worked
ios stopped reporting prob 5 miles away and wouldnt update.
I left the house to go into work around 645pm. I didnt realize something wrong with OT presence until all the Lights Off automation occurred while iOS was still away when it was supposed to be home.
Then noticed it never detected ios arriving to home. Thats when i messed around with OT app and Hubitat devices page and noticed ios wasnt reporting...it just stopped and android reporting was a little weird.
I referred to this thread and read the comments of 143 and somone mentioned they resored rolled back to previous version.
I did the same thing and restored to 2.3.9.201 from my saved folder on desktop.
ios left the house this morning and eveything is confirmed working correctly. EVEN when i check on the ios location and android location .....it reports correctly and timing of reporting as it should.
OK, thanks. That's the symptom I'm seeing as well. My geofence is about a 1 mile radius so it has us home well before (several minutes) before we actually get here. Lately, we've beat it home every time and observed it finally notices we are home 15 minutes or more later.
Let me know how it goes.....
No errors here but location reporting is definitely messed up. I hadn't seen it previously but I watched my bride make a 40 mile drive in and out of a couple of regions and there is something messed up. I am thinking of going back to 2.3.9 until this is resolved.
UPDATE: We went for a short Christmas color light ride and by the time we got home our locations were completely borked. I rolled back to 2.3.9.201. After sending a manual location update from each device everything looks right again, Even the messed up dashboard is correct. I haven't seen that since updating. I'm going to stay on 2.3.9 until 2.4 and Owntracks play nice together. 
I think it will take awhile before everything works correctly in this major update.
I found you only need to go back to 2.4.0.138. Versions after this are the ones having issues.
I'm not seeing this right now since I rolled back. @gopher.ny if you haven't gotten a PM with a hub ID, let me know and I'll update again so that it's in this state.
I think that version is only available to those that participated in the beta.
Same here
@gopher.ny @ipakula
Thank you both. If there is code you would like me to test and confirm, let me know. I'm able to get Presences working for everyone as a worker around in place. So if you need me to do anything let me know.
I don't know if any further debugging is needed from us, but just in case. Spousal unit and I were away and came back about 2:55 pm. About 15-20 minutes later, neither had posted an event within the geofence. I went into the OwnTracks mobile app and forced an update. That seemed to open a floodgate (for me).
Is there any easy way to get to 138? I only see last few versions as choices in diagnostic section
I know I've seen how to do it before (it is doable), I found this, but never tried it:
"You can try <hubIP>/hub/advanced/downloadPlatform/234 , wait a few minutes, then use the Diagnostic Tool to actually install it (it will be an option there if this works)."
That will get you the last official release of a major version...so above will get you the last official (non-beta) release for 2.3.4.
There isn't a path to 2.4.0.138 for someone who wasn't in the beta when that was released.
This implies there is a path for those who were. I'm seeing only the option for the last two 2.4.0.x and what I guess was the last 2.3.9.x release. How would I get to .138?
Download the Hubitat app
