How far is the trip you made (distance wise?) What you are describing sounds like more of a Google issue than Owntracks based on the settings.
With the settings I posted, the phone would need to see you move 50m before sending a location, and then it would wait 60 seconds, and need to see another 50m move before sending the next location.
With "locatorPriority:2", it's sniffing the air for wifi and cellular access points to determine if you moved. If you are in a place with there is a ton of wifi activity, it's very accurate. If there isn't a lot of wifi activity, or you are not traversing a cell boundary, it won't reflect your movement properly.
If you switch to "locatorPriority:3" then Owntracks will use GPS which solves the above statement, but does sacrifice more battery to do so.
Mine is working spot on, but I did write an Owntracks app that changes the phones to pegLocatorFastestIntervalToInterval: false and locatorPriority: 3 to give me the near home precision when a phone reports back that it's within 750m of home. Once it leaves that geofence, then it switches the phone back to pegLocatorFastestIntervalToInterval: true and locatorPriority: 2 to save battery.
Still working through that code, but so far that has worked great.
Thanks - i didn't understand the difference between locatorPriority 2 & 3. I'm in a town and did around 500m. It also disconnected from my own wifi and then re-connected on getting home, so I would have thought that would have triggered it....
I'm going to leave it on 2 for a bit and see how it goes, but I might bump it to 3, as I charge my phone every night anyway....
That distance should trigger it fine, as long as you didn't trip a locator accuracy limit where it didn't send out a location (you will see those in the logs that it suppressed it).
Might be the wifi though. When I drive where I live it works spot on. If I ride my bike, and go through a green space with poor wifi coverage, I go MIA for 10 minutes.
Are you going to ask for a pull request on these options from the OwnTracks developer(s) when you feel it's ready? Or post that version as a download here for us to try?
Oh, changes were all in an Owntracks Hubitat App. I need some time to document it a bit and then I can post a thread with a version to grab. The "goal" of the app was to replicate a single config source (and mimic Life360). Just need to get the documentation together, and check if any custom additions that I added to the mobile app doesn't break anything for others grabbing it off the playstore.
Will this app work with OwnTracks if I run it on my unraid server for full MQTT functionality? Is there any way to make it look at a server if I set one up?
With my new app + current 2.4.12 Owntracks mobile release, it does work very similar to the Life360 implementation. Only thing that differs is you get no push updates to the mobile app. You need to open the app, and click the "manual update" button to send your location back to Hubitat, at which the app I made will send your family locations (+ image if you configured it) back to your phone.
If you want another update of their location, you'd need to click the "manual update" button again.
Ahh yeh, no, the mobile app won't support that. You can install the Owntracks Recorder locally, and have the locations push through to it, and then you can see past history, speeds, etc:
Yes, if the changes are significant (and sounds like they are) best to open a new [Release]... thread and include link back to this thread which your app was developed from.
