Reporting just stops working on app, recorder shows reports #1898
Assignees
Labels
Comments
voryzen
changed the title
|
Do you have any app logs? |
|
Sure do, sanitised. well.. I wish there was an easier way to do that.. 😛 |
|
I've been lucky enough to get it working again, minor subset of my original post (pretty much without the reinstall, and cache clearing).. Not sure how long it will last for now, as it hasn't done this before. Here's the logs, if it helps (sanitised) |
|
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 them. What I've found is that Owntracks isn't actually connected to MQTT. After a while, I'll see a "Connection Lost" message in Owntracks logs and then the reconnection happens. Once the connection is made, the messages all get sent immediately to MQTT. |
|
I have the same issue v2.5.3 (Google Play) with a Pixel 8 on Android 15. The fix for me is to "force close" the app and then open it again and then instantly it publishes all the events that were sitting in the recorder. Sometimes it could be hundreds of events from many days of activity if I haven't noticed the app has stopped publishing to the broker. It seems like the app gets into a persistent offline state. Btw, I found the issue on previous versions too. |
|
I am also seeing this issue. App needs to be force closed and reopened and then everything is good for a day or two. Owntracks v2.5.3 (google play), Motorola One Ace, Android 11 |
|
Seems like the issue is with either way.. pubs and subs. I'm definitely getting pubs to the broker, as evident in the locations updating on the recorder. But subs regarding android devices.. thats another story |
|
Can you see if you get the same behaviour if you explicitly reconnect with the "reconnect" button in the Connection preferences screen? It does sound like the client is getting into some sort of state where it can't send messages, but doesn't disconnect / reconnect. |
|
@growse just tried it. After hitting reconnect the status menu says connected, but nothing has updated and it isn't actually connected (still shows my tag in town but I'm on my couch). It also has a message stuck in the endpoint queue |
|
4I have what may have or may not be the same issue. From op it seems like the reconnect is working but then disconnects almost immediately again. In my case (and possibly the same with other commentors) I seem to be hitting a race condition where there is a connection error, then disconnect is called, disconnect complains that "already disconnected" and a reconnect job is scheduled, then disconnect proper happens (from the connection error?) and this seems to trigger the reconnect job to be cancelled. Then the one time reconnect job is gone and never rescheduled. This all can be seen in the attached log at 0821. Then for potentially days after, the message queue will be repeatedly attempted every time with the endpoint@notconnectedexception. It will NEVER try to reconnect again or schedule another ONETIME_TASK_MQTT_RECONNECT job. I have to manually force close the app and restart it. Then it flashes the entire queue (rather annoying if days worth of location updates flush all at once). This most recent time I turned off mobile data and turned it back on, that triggered a reconnect. I suspect it might also be related to another issue someone has where the sim gets redirected to their car and the connection handoff is ... hitting edge cases. I suspect this because I just got a new car at around the same time I started having this issue. I have now found the "reconnect" button in the mqtt settings page at the top round arrows icon. I'll try this next time it happens and see if that also works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1-2 days after installation, the OwnTracks app will stop reporting. The fix is tedious:
Wait 1-2 days, until the process needs to be done again..
Recorder however, shows all reports made.
The text was updated successfully, but these errors were encountered: