(Seems) like my HA is being killed in the backgroud (I think)

Got a Pixel 9 Pro XL, running GrapheneOS with Play Services. No other app has any issues at all, expect HA.

One of my automations is taking a hit for this, which is the one that unlocks my front door and turns on some lights if the sun is down, so kinda a PITA that this one has a 50/50 chance of running.

Is there anything (currently) that doesn't work correctly with GOS as far as location or the app staying running? This didn't happen on stock and the GOS things I found when I searched were all old, and there wasn't a mention of people were running with the sandboxed play services or not.

Right now as I said, it's 50/50 whether it'll work or not. If my phone is sitting there locked it almost never does, if it's unlock and I'm on it, it usually will. My half workaround is a MacroDroid automation that runs HA when I get home, which that always works, but seems then I have to unlock the phone when it runs, then HA runs and then the automation will fire which is why I think it (may) be being killed.

HA (full version) has background data permission and unrestricted battery. But what's weird is random notifications throughout the day from HA always make it to me either way. I don't even know how to troubleshoot this one. Since the issues it's having seem to self-contradict themselves.

Plus like I said, I do have the play services installed, and other apps that depend on location work fine, so it's a weird one.

Hi, I have a similar issue with my Google Pixel 10 and GOS.

When I’m not using my device, no sensor updates are performed. If I unlock the device AND open the HA app. The sensors update is OK.

I tested with the app from Aurora Store and Google Play. Neither of them works correctly

HA to battery setting without restriction, full permission on data usage, and background use is enabled.

I set the permanent connection to "Always"

Thanks

1 Like