Android Companion 2022.2: Local Push Notifications!

[e-raser]

@dshokouhi

did you get any errors in the app logs at the time of the HA core error? that would help pin down what happened.

Unfortunately I can neither remind nor check that, I’m sorry.

@dshokouhi

In any case you may need to start fresh to re-register things if the service call is still missing

Thx, I know that Troubleshooting | Home Assistant Companion Docs section very well

A shorter path worked too:

1. Log out of the app
2. Log in again
3. Use same device name
4. Ignore “Firebase warning” message (I have the full version of the app installed)
5. Show all sensors, filter for “only active”
6. Tap every sensor once to trigger transmission to HA
7. Optional: rename entity names in HA

The service notify.mobile_app_my_device_name has been created. Tested and: phenomenal, it’s working! On a Fire OS device, great. Awesome, really. Finally Thank you so much.

[nick2525]

The one who chose Local Push Always, what is the battery consumption?

[dshokouhi]

Personally I did not have to change my charging habits. Others also have a similar experience, yours may be different. Its all about the device and battery.

Android Companion 2022.2: Local Push Notifications!

I’ve run a bare android on a pixel from 100% charge to 0 a few times with and without websockets on and I haven’t seen much of a difference in battery times. With and without i’ve gotten the same +/-. Just though i’d share. This isn’t to say there isn’t a difference in battery use but it isn’t causing wakelocks. It does show in battery stats as using much more % of time but I attribute that to simply running in a notification which adds time to the foreground app. If anything battery use, s…

[Minglarn]

Haven’t seen any difference. Same battery life on a Samsung Note 10+ …

[callifo]

Pixel 6 here, and had to turn it off, doubled my battery drain, was seeing battery down to 40% on a 12 hour day. Normally it wouldn’t break 60%. HA was at the top of the list for battery drain, and it was something like 32%.

[devilclarke (Rhys Clarke)]

Same experience S10 5G

[Minglarn]

Strange thing happend…
Since core-2022.3.0 no LOCAL notifications are sent to my device…
Anyone else with same experience?

[dshokouhi]

any errors in HA core or the app logs?

[Minglarn]

Just did some testing… Local Push do actually work fine… It’s the MQTT events witch is not working.
Have to do some debugging here…

In other words… All is gut!

[klogg]

Local Push doesn’t work for me…

It appears that…
If I have it set to Always then I don’t get the notifications,
If I have it set to Only when the screen is on then whenever I send a notification it crashes the app
If I have it set to Off then I get normal service.

Is there anything I can give you to help troubleshoot this?

[dshokouhi]

Open an issue on GitHub and make sure to get the requested logs for the issue template.

[h27rolf]

So far I have not configured remote access and in my Double NAT infrastructure (Cable Modem/router, WLAN router/ Raspberry / Container) seems I need to investigate on port forwarding, reverse proxy etc…
Nor do I use HA Cloud.

But, how could it be that I am receiving notifications on my HA companion app, even after I left home wifi?? Opening the app itself fails for sure because I configured the local HA address only.

Not unsatisfied about the behaviour, but would like to understand…

[SkechyWolf]

If you are on the full version of the Home Assistant app such as from the Play store notifications will also be sent over FCM (Firebase Cloud Messaging) when notifications can’t be sent locally

[nick2525]

The Telegram messenger also has its own implementation of push notifications, it would be great if you take a piece of code from there, combine your work and distribute your library for bypassing push notifications from Google. And you would make such an open source library and use it yourself