Help Needed: FCM Notifications Not Working on Mobile App

Mobile Apps
1

Setup Details

  • Home Assistant Installation: Raspberry Pi 4 (8GB)
    • Core Version: 2024.11.2
    • Supervisor Version: 2024.11.4
    • Operating System Version: 13.2
    • Frontend Version: 20241106.2
  • Mobile App: Google Pixel 8 Pro
    • App Version: 2024.10.2-full

Issue Description

Push notifications using the `mobile_app` integration have stopped working. The last successful notification via FCM was sent three days ago, and since then, all attempts to send notifications fail with the following error in the automation trace:

Device not connected to local push notifications

This issue persists despite multiple attempts to resolve it. Here’s what I have tried so far:

Steps I’ve Tried

  1. Confirmed Notifications Are Enabled:

    • Verified that notifications are enabled in the Home Assistant mobile app and on the phone’s system settings.
    • Checked that notifications for the app are not blocked or silenced.

  2. Restarted Devices and Services:

    • Restarted both the Raspberry Pi running Home Assistant and the Google Pixel 8 Pro.
    • Restarted the Home Assistant Core and Supervisor.

  3. Checked App Version:

    • Confirmed that the Home Assistant app on the phone is up-to-date (version 2024.10.2-full).

  4. Tested Notification Service:

    • Sent a test notification using `notify.mobile_app_yannic_pixel` via Developer Tools > Services.
    • The test notification fails, and no push notification is received on the phone.

  5. Checked Notification History:

    • Verified in the app’s settings that no notifications have been successfully sent via FCM in the last three days.

  6. UI Limitations Encountered:

    • Persistent Connection: I was unable to find a “Persistent Connection” toggle in the Home Assistant app’s App Configuration > Connection settings.
    • Manually Edited `mobile_app.json`: Could not locate the `.storage/mobile_app.json` file in the File Browser Add-on to clear the `push_token` and re-register FCM.

  7. Read and Tried Other Forum Fixes:

    • I’ve reviewed several related posts on the forums and attempted the suggested solutions, but none of them resolved the issue. For some reason, it just doesn’t work for me.

  8. Logs Pending Review:

    • I haven’t yet checked Settings > System > Logs for errors related to `mobile_app` or FCM but can do so if this would help narrow down the issue.

What I Want to Avoid

I prefer not to delete the `mobile_app_yannic_pixel` integration or entities in Home Assistant. The device is associated with numerous automations, and re-adding it would require significant rework.

Request for Assistance

I’m seeking guidance on:

  1. How to resolve the FCM notification issue without removing the `mobile_app` integration or device entities.
  2. Additional troubleshooting steps I can try to re-establish FCM push notifications.

Any help or insights would be greatly appreciated!

2

I’m just checking in to say that

  • I have the same phone as you do (albeit running with a custom rom, in case that matters)
  • I have the same issue since around the same time
  • I am also interested in finding a solution.

If I can be of any help please let me know!

3

Thanks for the update. hopefully this gets more traction!

4

For some reason the issue does not persist since about three days. I did nothing to fix it, it just started working again, seemingly out of nothing.
I hope you’re having the same experience…

5

not yet, im installing v14 and see if the update fixes it

6

It’s been a little while, updating both the phone and HA and all of the apps and many restarts did not fix it.

I’ve resorted to using pushbullet as a workaround which actually works in our favour since it also gives us browser notifications and works across all devices.