All my Notifications Fail to send as of 2 days ago - works for a second after reboot

Ltek · March 15, 2025, 1:01am

Mobile Notifications sometimes, not most of the time, send after the first few seconds after reboot… after the first one or two are sent, it fails to send any others. Most of the time, that doesnt even work.

New HA install of of 2 weeks ago, 3 phones and all was working perfectly until 2 days ago. All phones are Android … Pixel6a, Pixel7, Samsung S23

I have not changed anything with the phones, logins, or entities.

Persistent notifications to the web UI work fine.

Tried a ton of stuff over 2 hours spent.

blueprints and Developer tools
notify.notify and specific devices
removed one of the phones completely and re-added it… did not help.

I verified firebase DNS is not blocked in any way.

Core log…

Logger: homeassistant.components.mobile_app.notify
Source: components/mobile_app/notify.py:202
integration: Mobile App (documentation, issues)
First occurred: 5:04:15 PM (55 occurrences)
Last logged: 6:57:35 PM

Timeout sending notification to https://mobile-apps.home-assistant.io/api/sendPush/android/v1

debug log, last few lines…

laste few lines…

2025-03-14 18:48:20.979 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2727, in async_call
    raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Action notify.device_tracker_sm_t870 not found
2025-03-14 18:48:20.981 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2727, in async_call
    raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Action notify.device_tracker_pixel_6a not found
2025-03-14 18:48:20.983 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2727, in async_call
    raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Action notify.device_tracker_pixel_7 not found
2025-03-14 18:48:20.985 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2727, in async_call
    raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Action notify.device_tracker_sm_s911u1 not found

Didgeridrew · March 15, 2025, 1:37am

Is that a custom notifier, like a notify group, or a typo? It is unusual to see notify.device_tracker... and you seem to have 3 of them.

Ltek · March 15, 2025, 1:41am

Pretty sure that is ‘stock’ from the Mobile Integration… all devices are ‘device_tracker’ entities. I have 3 phones. I didnt create anything manually or custom

Didgeridrew · March 15, 2025, 1:43am

The mobile app’s notifiers are not entity-based and they normally appear as notify.mobile_app_..., you need to check in the Action tool to see if those notifier actions actually exist.

Ltek · March 15, 2025, 1:45am

I was using the Action tool to test with, it failed every time. The debug log is from when I tested using the Action tool screen. Here’s the list it shows me…

Ltek · March 15, 2025, 2:09am

maybe I should try to roll back to 2025.3.1 or .0?

Ltek · March 15, 2025, 2:30pm

Update… I rebooted again after my last message (had rebooted 3 times prior that day). Its been working ever since.

attached is a debug log from this mornings tests (blueprint and Action tool) for comparison to the prior debug log where we got errors doing the exact same tests. There was something funky with it for a few days. I hope it was an anomaly but will update if it comes back.

I opened a ticket here… Mobile Notifications fail, worked fine 2 days ago. Sometimes reboot fixes it for a few seconds · Issue #140636 · home-assistant/core · GitHub

Ltek · March 17, 2025, 3:25pm

@Didgeridrew this is still a huge problem… after working until late last night, no notifications have happened for at least 10 hours.

I setup 2 new, and different, automations for a motion sensor I know works perfectly (triggers lights-on instantly). They both send to mobile (notify.notify and notify.s23) and 1 sends a Persistent Notification.

I get the Persistent Notification but never the mobile.

Didgeridrew · March 17, 2025, 3:32pm

Post one, or more, of the configs for the failing automations… from everything you have posted, it just looks like you are using a non-existent action.

notify.notify shouldn’t be used. Choose a specific action to make sure your message goes to the right place.

Are you using shorthand here, or is that the actual “action” you wrote into your automation? If that’s actually what you are using, what integration platform created it?

Based on the screenshot you provided previously, the action ID should be:

notify.mobile_app_s23

Are there any errors shown in the debug traces?

Ltek · March 17, 2025, 3:44pm

in the Mobile Integration…

After I rebooted several times ~24hours ago, my devices were receiving multiple notifications (about 10 of them) until around midnight, last one was 11:30pm (I went to sleep) after that nothing.

both Blueprints used an HA selection box that just shows what the Mobile Integration shows… I selected ‘S23’ for both of them

*** Automation #1 ***

alias: "Notify Motion : Theater test"
description: ""
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.sensor_theater_bosch_motion_occupancy
    to: "on"
conditions: []
actions:
  - action: persistent_notification.create
    metadata: {}
    data:
      message: "Motion - Theater Back "
  - action: notify.all_mobile_devices
    metadata: {}
    data:
      message: Theater Motion test ALL
  - action: notify.mobile_app_s23
    metadata: {}
    data:
      message: Theater Motion test S23
mode: single


*** Automation using Blueprint... https://community.home-assistant.io/t/entity-state-notification/448007


alias: "Notify Motion : Theater back"
description: ""
use_blueprint:
  path: panhans/entity_state_notification.yaml
  input:
    input_entities:
      - binary_sensor.sensor_theater_bosch_motion_occupancy
    input_entity_states:
      - "on"
    input_notify_devices:
      - 4c405513584e73a3a8a3a9996bc35562
    input_group: motion-basement
    input_notification_color:
      - 238
      - 255
      - 0
    input_led_color:
      - 238
      - 255
      - 0
    input_entity_state_duration:
      hours: 0
      minutes: 0
      seconds: 0
    input_persistent_notification: true
    input_ha_notification: true
    input_title: Motion
    input_message: "{{ entity_name }} "
    input_notification_auto_delete: false
    input_channel: motion-basement


*** Automation using Blueprint... https://community.home-assistant.io/t/state-notifications-actions/612617/2?u=blacky

alias: "Notify Motion : Theater"
description: ""
use_blueprint:
  path: Blackshome/state-notifications-and-actions.yaml
  input:
    start_trigger_state: "on"
    start_trigger_state_entity:
      - binary_sensor.sensor_theater_bosch_motion_occupancy
    include_start_notify: enable_start_notify_options
    start_notify_device:
      - 4c405513584e73a3a8a3a9996bc35562
    start_title: " {{ states[trigger.entity_id].attributes.friendly_name }}"
    start_notify_data:
      - channel
      - sticky
      - high_priority
    start_action_button_1: Disable
    include_start_auto_actions: []
    start_action_1:
      - action: input_boolean.turn_off
        metadata: {}
        data: {}
    include_start_action_buttons:
      - enable_start_action_button_1
      - enable_start_action_button_2
    start_notify_channel: motion-basement
    start_action_2:
      - action: input_boolean.turn_on
        metadata: {}
        data: {}
    start_action_button_2: Enable
    start_action_button_confirmation_title: Action...
    start_action_button_confirmation_message: Entry Motion Notifications Disabled
    start_action_button_2_confirmation_message: Entry Motion Notifications Enabled
    start_time_delay:
      hours: 0
      minutes: 0
      seconds: 0
    start_message: " "
    global_conditions:
      - condition: state
        entity_id: input_boolean.bypass_entry_motion
        state: "off"
      - condition: state
        entity_id: timer.bypass_timer_entry_motion
        state: idle

Ltek · March 17, 2025, 5:24pm

I just updated to HAOS 15.0 and after it restarted, all mobile notifications are working.

If the actions were non-existent, none of this would ever work, rebooting or not.

Below shows all 3 different automations, and the Persistent Notification from one of them…

Ltek · March 20, 2025, 2:32am

notifications stopped working again, after working for about a day. there is some bug I must be hitting

Liveforlaughs76 · March 20, 2025, 3:15pm

@Didgeridrew Totally understand the confusion of the non-standard notify names but I’m pretty sure @Ltek is right that this is an issue, because I’ve been experiencing similar and there are other instances of this issue as well: https://www.reddit.com/r/homeassistant/comments/1jetuk9/notifications_timing_out/?rdt=42319. All cases agree the error thrown is “Timeout sending notification to https://mobile-apps.home-assistant.io/api/sendPush/android/v1” and things are temporarily fixed by restarting home assistant.

Will check next time the error happens whether it impacts iOS devices or if it’s only android, and if it’s all android devices or device specific.

Davecl · March 23, 2025, 10:08am

I have been having the same issue for a couple of weeks.
Changed nothing and suddenly notifications only work once or twice before needing a restart to get them working again.

Now this may be a coincidence or not but 2 days ago I updated ESPHome after it showed up as a pending update.
After this update all my notifications are working normally.
I have no idea if it was ESPHome causing the problem or not but at the moment all notifications are working again.

Ltek · March 23, 2025, 3:19pm

This morning I decide to try the only thing I know of which I had not yet tried. I have been monitoring it, and the IP has never changed, since Day 1 but I sett the IP as static in HA and entered a DHCP Reservation in the router… then rebooted.

So far, been working for over an hour. Lets see…

Ltek · March 23, 2025, 5:31pm

stopped working again… so it lasted an hour or two today

note the “105 occurrences”

Logger: homeassistant.components.mobile_app.notify
Source: components/mobile_app/notify.py:202
integration: Mobile App (documentation, issues)
First occurred: 9:53:30 AM (105 occurrences)
Last logged: 11:30:37 AM

Timeout sending notification to https://mobile-apps.home-assistant.io/api/sendPush/android/v1

theBasher91 · March 26, 2025, 3:05pm

I am also getting the same issue. Clearing app data fixes the issue but it comes back.

Ltek · March 26, 2025, 3:57pm

[Possible solution] for 2 days Notifications have been working!!!

on a whim I decided to have ChatGPT check the CONFIGURATION.YAML (even though it never has give me an error, manual checking or during reboots)

I replaced the current YAML code with the ChatGPT code and its been working ever since, even with updates to some Integrations and Blueprints.

The ‘fixes’ CGPT gave looked harmless but its working now (so far). I’d hope HA would have caught YAML config issues but seems HA may have inadequate checking methods.

✅ Summary of Changes & Fixes:

Corrected template indentation:

Fixed misaligned sensor: blocks under each trigger:.

Added availability checks:

Ensures lock event sensors are only active when data is available.

Improved consistency:

Streamlined state and attributes templates for better reliability.

ShadowFist · March 26, 2025, 9:10pm

If you really wanna help others, show your before & after yaml files. That way others won’t repeat your mistakes

Ltek · March 27, 2025, 2:59am

I posted the fix… have AI check your formatting. If it was a “mistake”, HA didnt think it was. Its probably some odd formatting bug in HA. I only have 2 templates in the config, thus, not much code at all. I try to avoid putting code in there since its ‘hidden’ and, as issues like this clearly shows, difficult (or nearly impossible) to troubleshoot if an issue arises. HA has some general design issues, which problem like this highlight.