Not sure what/how your Pi is currently configured, but if you set the recorder up via Docker, did you set it up via Docker Compose? If so, send me your current Docker Compose via PM & all the bits & bobs for you.
If you set it up from the command line, there are web sites where you can paste a FUNCTIONING Docker Compose (mine is functioning) & it will spit out the command line to use. You may just have to adapt to you port preference.
I don't think the HE app has the option to delete +follow regions any more...I believe he hid the +follow regions. I don't see any +follow regions in the HE app on 1.6.22 (most recent).
I set up Recorder from the command line following @lpakula's instructions in the app, it's running in a Docker container w/default settings from that setup, did not use Compose.
Thanks for the update @danabw was seeing the same issue, but it never occurred on my C5 hub (don't know if there are underlining differences?) In the later versions, that was changed to a number so re-setting that value would fix it.
The HE app generates a +[number]follow region, with the [number] being the locater interval from the advanced mobile location settings. By default, that will be '+60follow', with a lat/lon starting at 0,0. When an iPhone moves, it updates those coordinates to match it's current location. That someone keeps the iOS app from sleeping and missing movement.
Is there only '+follow' region on the iPhone right now? You need to delete all except the one that keeps getting sent back (+60follow if it's using defaults).
I removed the ability to delete or see these in the HE app, since they need to exist for optimal iOS operation.
Currently is 'off to the side' while I wait for the actual Play Store version to get background service in it. I'll post here when I add in the address display. The current HE app/driver already supports this, it just needs to come from the phone. That change I'll do a pull request so that the official versions get them -- of course that is highly dependent on when they cut those releases.
It seems like if you change the locator interval in the advanced settings that it generates a new +follow w/that number but the existing ones persist on the phone. Might be something to check...I had three (original 60), plus a 30 and 45 from two changes I had made to the interval on HE.
That is one problematic thing. If I leave it at '+follow' then it defaults to 30 seconds, regardless of what you set the locater interval at. If I allow you to change it, then there is no means to delete the old one off the phone.
Stuck in a chicken & egg situation. Might go back to +follow to eliminate the confusion is causes when you switch settings though....
@dnickel ok I think I see what happened. Seems to be an issue when a user leaves home that this gets triggered. I'll remove the warning on the next version to stop the spam in the log.
I get it, it's a nightmare to maintain, that's why I asked. Just let us know when we should migrate to the Play Store version and relieve you from that burden
Yes, my wife just left and I got this:
app:16332024-01-22 11:00:16.123warnOwnTracks: Pixel 5 OT's mobile app 'Home' region lat/lon/radius does not match 'Home' in the Hubitat OwnTracks app. Select this member to have their regions updated or confirm the mobile app region matches.
Maybe just need a bit of text in that spot, or a pop-up if it's changed, saying that the previous +follow needs to be deleted if that setting is changed. Everyone won't handle it as request, but maybe better than losing the option.