Troubleshooting failure to send location info

[sour linden]

Hi all. Is there a way to troubleshoot those failure to send errors? How can I get more info about the reason?
Thanks

[silent sparrow]

the logs may not go back as far, but Settings > companion app > troubleshooting > show and share logs would have it but you may need to replicate the issue. You can also check HA core logs at the time of occurrence

[sour linden]

Using show and share I've only few minutes of log... Any way to have a longer time stored?

[sour linden]

OK. I've been lucky. I got a failure to send covered by logs.

12-19 07:42:08.353 17602 25078 E LocBroadcastReceiver: Could not update location for 9.
12-19 07:42:08.353 17602 25078 E LocBroadcastReceiver: io.homeassistant.companion.android.common.data.integration.IntegrationException: java.io.InterruptedIOException: timeout
12-19 07:42:08.353 17602 25078 E LocBroadcastReceiver: at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl.updateLocation(IntegrationRepositoryImpl.kt:265)
12-19 07:42:08.353 17602 25078 E LocBroadcastReceiver: at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl$updateLocation$1.invokeSuspend(Unknown Source:15)

Nothing found at server side. I'm using external access through duckdns and letsencrypt.

[sour linden]

To check for HA core logs do I have to set some logging level or the default settings should be enough?

[silent sparrow]

default should be good enough there, the timeout error is not really one we can fix, we expect valid responses

[sour linden]

Thanks. In "Could not update location for 9" what does this 9 mean?
In any case do you know how can I set the debug level for that part at HA server side?

[silent sparrow]

9 is just the internal server id taht was assigned, not really important more for multi server logic

[silent sparrow]

you need to enable debug logging for mobile_app integration

[sour linden]

Thanks for the info. I'll give it a try. Another question. Today I've been always home. Checking the troubleshooting logs I see that sometimes it takes seconds between position checking sometimes 10 -15 minutes. I've seen even more than 30 minute delay between checks.
Why? Is it possible to set a standard checking time of let say 1 minute ?

[silent sparrow]

any gaps you see are caused by Google not sendng updates to the app....its a known issue and we are hoping they will fix it. You can try to use high accuracy mode with the interval set to 60 seconds if you desire but it will drain more battery as it uses GPS directly https://github.com/home-assistant/android/issues/4679 there are some suggestions in this thread as well. Also the app will not send updates if location has not chagned for 15 min

location tracking depends on updates to comes from Google so if there is a play services bug which we currently suspect we have to wait for them to fix

[sour linden]

Hi @silent sparrow , app is using FusedLocationProviderClient API, right? I suppose the issue (or feature) we're facing is described here. https://developer.android.com/about/versions/oreo/background-location-limits am I correct?
At the end of that page looks like they suggest to use the batch mode of FLP or the geofencing API to get more frequent updates. Did you try all of this hints?
Thanks

[silent sparrow]

Geofencing is done via location zone sensor and batching is something we already do. High accuracy mode is another one we have that meets another set of criteria on that page

[sour linden]

@silent sparrow what do you mean with: "another day of criteria on that page"?
Btw: to setup debug mode for the mobile app the following is the right syntax in configuration.yaml, correct?

logger:
default: warning
logs:
mobile_app: debug

[sour linden]

ops... found... this one is better:
homeassistant.components.mobile_app: debug

[silent sparrow]

Day = set

[sour linden]

Hi @silent sparrow do you think that the tailed to send error I'm getting are caused by my network setup or can be a some sort of bug?
I followed the guide and gave all the required permission.
Any idea?

[silent sparrow]

timeouts are from the server end, do yu see them that frequently?

[sour linden]

Hi. Today I had almost 40 sent location updates and 30 failures.

I've a lot of those entries in mobile app logs:
24:43.410 9346 3752 E GPUAUX : [AUX]GuiExtAuxCheckAuxPath:674: Null anb
Do you know the reason?

[silent sparrow]

Safe to ignore

[sour linden]

Oks. If I show and share logs I get less than 2 minutes of time coveted. Is it possible to increase this time? Last failed to send happened 3 minutes ago... So it's lost (just to double check they're always timeout related)

[silent sparrow]

no we cant increase the time it all depends on the pid given to the app ad taht can change at anytime

yuo can try annother app like logcat reader which gets historical logcat

[sour linden]

I'm not sure I get you. Tell me if I'm wrong: logs are written using some standard android api. The mobile app has no control on the amount of logs that can read (and display). There are standard apps that can display such logs. Am I right?

[silent sparrow]

yes we dont save the logs we just read them based on our assigned pid which can change at anytime

[sour linden]

Clear. This logcat reader only shows logs that are generated when it's running or can also show logs that have been generated in the past?

[silent sparrow]

want to say about 24 hours or so?