I have a Pixel 7 and the same (recent) problem, however my gf has an iPhone and has also been experiencing this (recent) problem, so something changed on the HA or HA app side that is causing this.
This is my “arrived Home” automation, but the problem definitely seems to be the fact that my last known location was from 2 whole hours ago. My gf’s, just now, was 35 minutes, which also seems way too high, given that the sensors are set to the usual 15-minute update intervals. I also followed the steps in the link, but they’re pretty common sense and the automation worked flawlessly until recently. For whatever reason, on both iOS 17/18 and Android 14, this has started happening. Given that I still haven’t received the Android 15 update and that my gf’s app has the same behavior both before and after the update to iOS 18, it must be smthn in the app code, no?
alias: Florin Home
trigger:
- platform: state
entity_id:
- person.florin
from: not_home
to: home
action:
- data:
message: Florin is Home
action: notify.telegram_florin
initial_state: "on"
mode: single
iOS and Android are not the same, you need to troubleshoot each one separately.
for android as mentinoed earlier in this thread start with these steps https://companion.home-assistant.io/docs/troubleshooting/faqs/#device-tracker-is-not-updating-in-android-app
They are 2 different apps, but the problems started pretty much at the same time for both phones…and from what I see here, on the Android side it’s perhaps more of a Pixel issue?
there can be multiple reasons why location tracking doesnt work which is why we ahve steps and ask users not to skip them. We provide tools like location tracking history to help troubleshoot these issues. But none of that helps if the steps and guides are not followed.
All the steps regarding the settings have been followed, so I guess the next step is getting some logs recorded and opening a Github issue…
no you skipped the location history which are still mentiond as part of the same steps
I’ve gone through all the steps and posted different scenarios where i showed my location history entries.
I have no idea how to proceed
for your particular scenario you can open a bug in github, please provide the screenshots of the gaps in time and make sure to fill out the issue template completely with things like app version number etc… https://github.com/home-assistant/android/issues/new?assignees=&labels=bug&projects=&template=Bug_report.md&title=
I’ve opened a bug report and gave as much info as i could
Well, at least on my Pixel I think I figured it out, it’s this complete garbage setting that had been ON by default, likely enabled by a recent monthly update from The All-Powerful Google, who knows what notifications you should get better than you.
What a ridiculous concept…and in the previous menu it shows that the Battery Saver is Off, so I didn’t think to actually enter there, the UI doesn’t even indicate that there is a sub-menu, while when you enter this setting is also hidden under a drop-down.
in my own setup adaptive battery is left on, however i did turn off adaptive charging
I think it depends on how much you actually use the mobile app…I normally use the HA via the web UI when I’m at my PC at home, so what probably happened is that “learns from your phone usage to continuously optimise” crap put the mobile HA app on some list I don’t have access to. I only changed this one setting and it’s been fine all day on multiple errand trips away from home.
I can confirm that we see the same issue on both our Google Pixel 8 Pro phones linked to our HA. Locations sometimes stops updating, even with the mobile application open. I’ve tried all the troubleshooting steps mentioned above, and even tested with triggering manual update using the notification function but no luck. It might be slightly better after turning off all battery saving etc but its not reliable at this moment.
may or may not have found the culprit
https://issuetracker.google.com/issues/370069681
are all those impacted Pixel users on the same Sept update?