Push notifications not working, after changing phones

[ionv3n0m]

The problem

The wife and I updated our Pixel 6 pros within the past couple days, where notiifcations were 100% operational, to Pixel 8 pros, where we're not getting notifications now.

I've tried to roll back to 12.1, uninstall android app and reinstall, add all notification functionality on the android app, checked my pihole for any DNS blocks around "firebase".

What version of Home Assistant Core has the issue?

2024.1.2

What was the last working version of Home Assistant Core?

2024.1.2

What type of installation are you running?

Home Assistant Core

Integration causing the issue

notify.notify

Link to integration documentation on our website

https://www.home-assistant.io/integrations/notify/

Diagnostics information

No response

Example YAML snippet

service: notify.notify
data:
  message: gredf

literally just trying to test functionality, this is pasted from Developer Tools > services.

Anything in the logs that might be useful for us?

Logger: homeassistant.helpers.script.websocket_api_script
Source: helpers/script.py:1792
First occurred: 2:09:10 PM (41 occurrences)
Last logged: 2:45:30 PM
websocket_api script: Error executing script. Error for call_service at pos 1: Device not connected to local push notifications

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (notify) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `notify` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign notify` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

notify documentation notify source _{^{(message by IssueLinks)}}

[ionv3n0m]

Just incase it was anything further on my network, IE: router, I updated the firmware and did a full reboot on it. Router is an Asus RT-AX88U running merlin firmware.

[gfn256]

As per the documentation : "Be aware that you might want to change the actual service to whatever service you are actually using since notify.notify is shorthand for the first notify service the system can find and might therefore not be working as intended."

Have you tried choosing your actual notify service for your specific phone, for example (mobile_app_pixel8pro or whatever its called, you can check it in the list of available notify services):

service: notify.mobile_app_pixel8pro
data:
  message: >-
    Some message

[ionv3n0m]

Okay, I just tested that again, using Notifications: Send a notification via mobile_app_james (example). And it sent, and notified/worked with no issues.

Now, I guess with that addressed, Is there a way I could've traced this down, for my own troubleshooting on why notify.notify wasn't selecting a service, or if it really was firebase errors? I couldn't really find much to work with.

[gfn256]

As I quoted above notify.notify will choose the "first" notify service it finds. In your case this may very well be your old phones, or some other notify service. Check them in your HA system, and delete/remove as necessary. Hope I managed to help you.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.