your next step was to look at the logs because you said you had already checked those steps
unfortunately, dontkillmyapp.com is several version behind the current version of Android and their information is stale for Pixel phones. However, I decided to grab my old pixel phone and try the Home Assistant app on it… so far I haven’t had any issues on this phone… and no issue on another android. Therefore, I’m tempted to wipe my new phone and see if that resolve the issue… however, that a pain in the… to do.
on a pixel phone you just need to make sure the background access tile is granted in the companion app settings…thats all i have on all my pixel devices and it works fine for me.
Yep… that’s enabled. I suspect something funky is going on. I will have to transfer everything to my old phone, wipe this one and start over… cross your fingers for me!
2 Likes
Let me know how you get on with that,
I’ve checked all setting both in the companion app and on the device it’s self, I can’t find any issue in the logs,
And here was me being told IOS was the hardest one to do. So far my wife’s apple phone has been the easiest device to set on on the hole system,
as you have a samsung device your steps are going to be different than a pixel device, look for settings like power saving, data saving etc… and turn all those off for the app. Samsung likes to add extra things that are not documented anywhere and users need to check and disable such features that prevent background work.
Hay dude,
These are all steps I followed to start with.
I un installed the companion app and cleared all sensors to do with the device before re installing it, this seams to have worked.
Ill test it out again once im at work tomorrow.
1 Like
ah so you more or less followed our start fresh steps
https://companion.home-assistant.io/docs/troubleshooting/faqs/#starting-fresh-with-the-android-app
that was next after logs and checking the app has proper permission to run in the background
1 Like