hastyeagle

hmmm, I'm not seeing `allowRemoteLocation` in the config.

OK, we're getting farther now! Now when the app receives the message it says `"[...] Received incoming message: MessageCmd on [...]`. It's not pushing a location, though. Could it be...

Gotcha on `allowRemoteLocation` only being on iOS. The app is definitely connected to MQTT. It's seeing the MessageCmd come through, and I see it has an updated location. It's just...

I do: > 2023-11-10 10:38:05.049 I MessageProcessor: Received incoming message: MessageCmd on owntracks/user/device 2023-11-10 10:38:05.051 D BackgroundService: On demand location request 2023-11-10 10:38:05.052 D GMSLocationProviderClient: Removing location updates clientcallback=201885842 2023-11-10...

Thanks @growse for fixing this! Looking forward to v2.5.0. Thanks @jpmens for the help as well!

Thanks, @growse. I installed the latest beta and _cmd is now working in non-manual modes. One thing I noticed is that if manual mode is set, Owntracks will refuse to...

@ckrey Yea, but there are "manual" and "quiet" modes. I could see not sending an update in quiet mode, but sending the update in manual mode still makes sense to...

I'm seeing something similar on v2.5.3 (420503003). My logs will show it successfully pushing locations to MQTT (and status shows 0 messages in the queue), but MQTT isn't actually receiving...

I downgraded from v2.5.3 to v2.5.0 on two devices to see if it had this issue and v2.5.0 has been working fine since I switched to it. So it seems...

> [@hastyeagle](https://github.com/hastyeagle) , can you confirm v2.5.0 is still working fine for you? I also don't remember seeing these issues on v2.5.0. I'll try to pinpoint the commit that broke...