Thank you for your persistence. At last I have it working! Notify.notify had always worked in the past, so I made the assumption that the fault would be resolved by changing something else, not the messaging service
Thank you. Whitelisting these domains in AdGuard fixed it for me.
For future reference, adding only this worked for me and seems to be enough:
@@||firebaseinstallations.googleapis.com^$important
Error solved, in my case.
Connected from iphone using HA local web url.
- Menu > Settings > Devices > Mobile App > delete old devices
- Menu > User > Log out
- Login again > fixed
[Sorry (not sorry) for the necropost, but I’m having this issue and none of the solutions in this thread have worked…
I followed your instructions, force closed the Companion App (Android), reopened and shared the log - no errors.
I then triggered a notification (manually from inside an automation) which immediately produced the “device not connected to local push notification” error on the HA frontend.
I then shared the log again and this was the error which occurred when I triggered the notif:
10-20 08:24:45.459 29669 29719 E IntegrationRepositoryImpl: Unable to get notification rate limits
10-20 08:24:45.459 29669 29719 E IntegrationRepositoryImpl: java.net.UnknownHostException: Unable to resolve host “mobile-apps.home-assistant.io”: No address associated with hostname
10-20 08:24:45.459 29669 29719 E IntegrationRepositoryImpl: at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
10-20 08:24:45.459 29669 29719 E IntegrationRepositoryImpl: at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
10-20 08:24:45.459 29669 29719 E IntegrationRepositoryImpl: at java.net.InetAddress.getAllByName(InetAddress.java:1152)
…
10-20 08:24:45.459 29669 29719 D SettingsPresenterImpl$getNotificationRateLimits: Unable to get rate limits
I am able to resolve that hostname from PC and phone.
Any help greatly appreciated.
Is this valid for the Play Store version? AFAIK the minimal HA companion app should not use those connections, right?
I’m sorry, I can’t wrap my head around this. You seem to be saying that the local push notifications depend on persistent connection and then advise us to turn them off? Please help me understand.
Also, can you explain what to set it to if using the minimal F-Droid version of the companion app please?
If you need the connection then please check the logs I mentioned earlier.
Settings > Companion App > Show and share logs
Also, this setting / menu doesn’t seem to exist any longer in the companion app, can you please check or explain? I can’t find any menu item related to logs in the companion app settings except related to changelogs.
“Show and share logs” is under “Troubleshooting” now.
Just made an account to say this worked for me.
Here’s what worked for me:
- Open HA app on phone
- Main Menu
- Settings
- Companion app
- Under first section, ("Servers & devices), tap your HA server name
- Under last section, (“Other settings”), tape “Persistent connection”
- Set to “Always”
Notifications began working immediately for me.
Exact same issue for me.
I am using NextDNS and the blocklist “Goodby Ads” had “firebaseinstallations.googleapis.com” blocked. After whitlisting “firebaseinstallations.googleapis.com” notifications are working again.
thx a lot
still an issue here, android with no gplay on a VLAN with no internet access, fresh minimal app installed from github, persistent connections break when the server reboots. only fix is to force stop the app and restart it or reboot the phone.
Same here. In my case:
- I’m on GrapheneOS with no GMS.
- I tested the original app and minimal one.
- It happens when I’m connected to home wifi / connected via Tailscale.
- I have Persistent Connection activated.
Only works rebooting the phone, relaunching the app or sometimes it randomly works…
Same here. I’ve had this issue for a couple of years. Its gotten way worse since I moved to Graphene OS. I’m using the fdroid version the only fix is to toggle the persistent notifications to never than to always or reboot the phone. It breaks randomly but always after my phone is rebooted. Anybody else fix this? I’ve had to change my notifications because of this. I can provide logs if need be. I’m guessing this is strictly an android issue.
I have this problem for a long time now, on a fire tablet which is always plugged in. Installed from F-Droid.
Persistent connection is set to always. Battery optimation is disabled.
It works after a reboot for a few hours.
UPDATE: I believe I figured it out for my case at least. I'm on Graphene OS and use the FDroid version. I also always have tailscale or netbird VPN on since I need to be able to access my homelab when away. When I have "use exit node" ON the notifications would stop working randomly until I restarted the phone. I've turned off the exit node in Tailscale app and the notifications have been working for 2 weeks straight.
on a local VLAN, no VPN, so not a fix for me. reboot your HASS server and let us know if notifications come back on the android client without intervention.
Thanks a lot. This was also my problem when using BlockAds on Android.
Apparently whitelisting the Home Assistant app itself isn't enough. I needed to whitelist this URL specifically, force stop and restart the Home Assistant mobile app, then it made a request to this URL, which I guess connected it to the notification web hook.