Android 14, do notifications work?

I’ve updated my Oneplus 11 to Android 14 a few days ago. Since that moment I have not seen a single notification from the companion app from any of my automations. Is it compatible with A14?

I’ve checked Android’s notification settings for this app, but everything is allowed. They’re not set to silent.

So I went to developers tools to manually call the notification service. The companion app produces a green tick, meaning everything went well. But no notification is produced.

How can I fix this?

If you have a new phone, you have to set up the notifications for that new phone. Although the old phone might not be in use, the notifications are being sent to it.

Notifications are working to both of the Android 14 Pixels in this household. As suggested, you should check that the phone ID didn’t change during the upgrade.

Thanks both!
It is indeed the same phone, just updated to a new Android version. If I go to an automation, add a new action > service and then type “notification”, the companion app proposes notify.mobile_app_cph2449. CPH2449 is and was the ID for my phone. But such an action does not trigger a notification. Should I do something to reset or reload that?

any errors in the HA core logs? is the companion app showing the notification in notification history?

There are no errors in HA’s system log. The companion app says the last notification was on 2 December, which corresponds with my observation. It also shows that I’ve used 11 from 500 notifications.

I’ve removed my phone as device under Devices > Mobile App. That didn’t fix it unfortunately.

try to start fresh to clear up bad data, removing the device is not a good step actually

Try manually calling the Notify service from Dev tools:

  • HASS → Developer Tools → Services → Service = notify

Start typing notify, and a list of your devices should appear, as well as the generic notify.notify to send to everything.

Thanks. Yes, that’s what I did already. No notification appears on my phone. Not in the history either.

Clearing data of the app and then login again solved the problem indeed! Thanks so much!

2 Likes