OwnTracks reporting old location to server

[libreivan]

• App build number: 420412000
• Android version: 14 (Graphene OS, no gms)
• Device: Google Pixel 7a
• Installation source: GitHub (APK)

Hello! I am using OwnTracks 2.4.12 (OSS) to share my real-time location. But, even though it correctly detects where I am, as the blue dot is exactly where it's supposed to be, the location information sent to the server seems to be in this place I was months ago.

I tried everything. I honestly, don't know what to do about it, and logs look just fine to me.

[jpmens]

and logs look just fine to me

They might look fine to you, but not to us. ;-)

Seriously. Send us the logs please, together with a publish you get when you press up-arrow to publish the current location. Kindly do not redact data other than passwords; we will treat your data carefully. Send by email to support@owntracks.org and mention this issue number please.

If you want us to look, that is.

[libreivan]

Done! And thanks for the quick response. :)

[jpmens]

We'll probably have to wait for @growse to say exactly, but I see two distinct location publishes in the logs you sent us, paste here without the GPS coordinates:

2024-04-11 15:56:46.818 D BackgroundService: location result received: LocationResult(lastLocation=Location[hAcc=13.0 et=+1h14m13s421ms alt=85.0 vAcc=21.0 vel=0.0 sAcc=0.90625 {Bundle[{satellites=0, maxCn0=0, meanCn0=0}]}])
2024-04-11 15:56:46.829 D BackgroundService: location result received: LocationResult(lastLocation=Location[hAcc=13.0 et=+1h14m13s421ms alt=85.0 vAcc=21.0 vel=0.0 sAcc=0.90625 {Bundle[{satellites=0, maxCn0=0, meanCn0=0}]}])
2024-04-11 16:12:46.603 D BackgroundService: location result received: LocationResult(lastLocation=Location[hAcc=45.0 et=+1h30m13s197ms alt=78.0 vAcc=84.0 vel=0.0 sAcc=1.046875 {Bundle[{satellites=0, maxCn0=0, meanCn0=0}]}])
2024-04-11 16:12:46.639 D BackgroundService: location result received: LocationResult(lastLocation=Location[hAcc=45.0 et=+1h30m13s197ms alt=78.0 vAcc=84.0 vel=0.0 sAcc=1.046875 {Bundle[{satellites=0, maxCn0=0, meanCn0=0}]}])

It would also appear (if I'm interepreting the logs accurately) that there is not sat reception at that moment.

[libreivan]

Well, my location was accurately being depicted by the blue dot, it's just that the data sent to the server seems always to be that same spot. Also, I had internet data available, so it's sadly not that. :(

[libreivan]

Hey, contributors. I know this issue is kind of dead, but I just realized this might have something to do with the fact that I am using the HomeAssistant integration. Is this a known issue?

[compuguy]

Hey, contributors. I know this issue is kind of dead, but I just realized this might have something to do with the fact that I am using the HomeAssistant integration. Is this a known issue?

Out of curiosity are you sending your location directly to home Assistant or mirroring another MQTT server to Home Assistant?

[libreivan]

Hey, contributors. I know this issue is kind of dead, but I just realized this might have something to do with the fact that I am using the HomeAssistant integration. Is this a known issue?

Out of curiosity are you sending your location directly to home Assistant or mirroring another MQTT server to Home Assistant?

Hello! I'm directly to home assistant with the OwnTracks integration. 🙂

[wir3z]

@libreivan Shouldn't matter what the endpoint the data is sent to (Home Assistant or otherwise). The app just bundles the data and sends it into the "ether".

Have you tried the new 2.5.0-Beta2? There was a lot of fixes around location bugs that may have this addressed.