I’m having lots of issues with this sensor not updating. I use it to trigger certain automations and it used to work OK. For some reason now it will take minutes to update. I noticed today it didn’t update at all in half an hour despite it being connected disconnected several times. When I opened the app and checked the phone in the mobile app ha integration, I could see all the sensors going mad. Almost as if the app has frozen up. This is the logbook:
I’ve just checked the logs and I can only see back as far as when I’ve just opened the app (14:08). 30 mins after the event.
I can see lots of these errors, not sure what they mean? mpanion.android: Invalid resource ID 0x00000000.
The latest crash was earlier this morning. Way before the issues with sensors not updating.
Phone is Pixel 9 Pro. Latest Android 15.
App version 2025.4.3-full
Sensor update frequency is set to Fast always.
We have similar issues with a Pixel 9 Pro and Pixel 8 Pro - this sensor and location (both have background access etc. switched on - been using the app for many years so well versed with the settings).
location issue is separate from the sensor issue, the location one is on Googles end based on research. For this sensor in particular if you have confirmed background access for the app, try to enable the last notification sensor and grant the required permission.
do you have background access enabled for the app?
Yes
For this sensor in particular if you have confirmed background access for the app, try to enable the last notification sensor and grant the required permission.
High accuracy mode doesn’t seem to trigger hardly ever, which means when arriving home it will take a while to set as home. Leaving, it seems to trigger away OK when walking or by car but again I don’t get high accuracy mode triggering. I’ve resorted to automations firing to force high accuracy mode when someone is on my drive in Frigate and when Android auto is disconnected, which is why I’m now having this issue. It used to work great.
you may need to try and go out to the car, connect android auto and then look at the companion app logs, for this sensor in particular we wait for the OS to tell the app it is connected and send an update then. Another thing you can try is a different connection to android auto to rule that out like try a cable if wireless looks flakey
It’s not the AA connection, although you’ve reminded me I do need to change my cable as it’s disconnected a few times when it’s been plugged in recently. I don’t have any other way of connecting to my head unit, it’s quite old.
I’ve noticed the location updates not sending anything for long periods of time too. Then all of a sudden sending everything. Like the app is locking up.
I had a ton of these updates with locations where I’d been an hour earlier. At 13:46:29 I had a “too many updates” in the log then at 13:49:30 it finally sent the correct location and marked me as home. I actually arrived in the zone around 13:45. I’m wondering if it’s when I connected to WiFi. Seemed to work ok later on when I was out walking.
It’s not that bad! It’s happened a handful of times and I’m now wondering if it’s an issue with AA app on my phone and not the cable as I’ve just been in to the car, connected moved it around, wiggled the cable, no disconnects. The sensor also updated instantaneously but I had the HA app open. Could it be a low resources issue?
I’d also add when the original issue happened, I had disconnected it by that point and gone into the integration in HA to see why it hadn’t triggered my automation and I saw all these updates happen at once.
