Are Persistent Notification supported ?

[db-wally007]

Hi,

as title says, are HASS native persistent notifications supported ?
https://www.home-assistant.io/integrations/persistent_notification/

I read in one of the closed Github issues that HASS alerts are supported but this requires setting up each alert in the card as far as I understood it). My question is if native HASS notifications are supported.

I already have Automations creating native HASS notifications (for battery alerts, for window/door open after 12am and so on ) but at the moment it requires user to have sidebar visible at all times to see them. I'd like to show notifications in a dashboard card (without duplicating each alert in this card).

Is this possible ?

[djdevil]

Hi @db-wally007! 👋

AlertTicker Card can already display HA persistent notifications — no duplication needed.

When a persistent notification is created (via automation, notify.persistent_notification, or a service call), Home Assistant exposes it as a real entity: persistent_notification. with state notifying and attributes title and message. You can monitor all of them with a single entity_filter alert:

type: custom:alert-ticker-card
alerts:

• entity_filter: "persistent_notification."
  operator: "="
  state: "notifying"
  message: "{name}" # shows the notification's friendly name
  theme: notification
  priority: 3
  To show the notification message content instead of the entity name, use the attribute field:

• entity_filter: "persistent_notification."
  operator: "="
  state: "notifying"
  attribute: message # reads the "message" attribute
  operator: "!=" # show as long as message is not empty
  state: ""
  message: "🔔 {state}" # {state} will be the notification message text
  theme: notification
  priority: 3
  Or combine both title and message using a Jinja2 template:

  message: >
  {{ state_attr(entity, 'title') }} — {{ state_attr(entity, 'message') }}
  A few notes:

The filter "persistent_notification." matches all persistent notifications. If you want to be selective, you can use entity_filter_exclude to skip specific ones by entity ID.
Each distinct notification gets its own alert slide — if 3 notifications are active, all 3 cycle through.
When a notification is dismissed in HA (via the bell icon or persistent_notification.dismiss), its entity disappears and the alert automatically clears.
So no need to duplicate your existing automations — just point the card at the persistent_notification.* entities and everything works automatically. Let me know if you hit any issues!

[db-wally007]

Thank you for the response and detailed instructions. I will give it a go this week and report back.

[db-wally007]

Hi @db-wally007! 👋

AlertTicker Card can already display HA persistent notifications — no duplication needed.

When a persistent notification is created (via automation, notify.persistent_notification, or a service call), Home Assistant exposes it as a real entity: persistent_notification. with state notifying and attributes title and message. You can monitor all of them with a single entity_filter alert:

type: custom:alert-ticker-card alerts:

• entity_filter: "persistent_notification."
  operator: "="
  state: "notifying"
  message: "{name}" # shows the notification's friendly name
  theme: notification
  priority: 3
  To show the notification message content instead of the entity name, use the attribute field:
• entity_filter: "persistent_notification."
  operator: "="
  state: "notifying"
  attribute: message # reads the "message" attribute
  operator: "!=" # show as long as message is not empty
  state: ""
  message: "🔔 {state}" # {state} will be the notification message text
  theme: notification
  priority: 3
  Or combine both title and message using a Jinja2 template:
  message: >
  {{ state_attr(entity, 'title') }} — {{ state_attr(entity, 'message') }}
  A few notes:

The filter "persistent_notification." matches all persistent notifications. If you want to be selective, you can use entity_filter_exclude to skip specific ones by entity ID. Each distinct notification gets its own alert slide — if 3 notifications are active, all 3 cycle through. When a notification is dismissed in HA (via the bell icon or persistent_notification.dismiss), its entity disappears and the alert automatically clears. So no need to duplicate your existing automations — just point the card at the persistent_notification.* entities and everything works automatically. Let me know if you hit any issues!

Are you sure about persistent notification creating entities ?

I have a following debug alerting

      - action: persistent_notification.create
        data:
          title: "🔧 DEBUG: Monitored Devices List"
          message: >
            {% set count = states('sensor.monitored_devices_list') | int(0) %}
            {% set devices = state_attr('sensor.monitored_devices_list', 'devices') | default({}, true) %}
            {% if count > 0 and devices | length > 0 %}
            **Currently monitoring {{ count }} device{{ 's' if count > 1 else '' }}:**
            
            {% for device_id, info in devices.items() %}
            - **{{ info.name }}** ({{ info.manufacturer }}) - *Status: {{ info.state }}*
            {% endfor %}
            
            *Manufacturers:* {{ state_attr('sensor.monitored_devices_list', 'monitored_manufacturers') }}  
            *Last updated:* {{ state_attr('sensor.monitored_devices_list', 'last_updated') }}
            
            ---
            **⚠️ REMINDER: Disable this automation after testing!**
            {% else %}
            No devices are currently monitored.
            {% endif %}
          notification_id: "debug_monitored_devices"

I can see the notification in the side bar when I run automation that triggers this action.

However there is no entity such as persistent_notification. or similar

[djdevil]

Hi @db-wally007! 👋

You're absolutely right, and I owe you a correction — my original answer was wrong.

Since Home Assistant 2023.6, persistent notifications were removed from the state machine entirely. persistent_notification.* entities no longer exist anywhere — not in Settings → Entities, not in Developer Tools → States, not in templates. This was a deliberate change (tracked in core #15071) and there's been no reversal since.

So AlertTicker's entity_filter: "persistent_notification." does not work on modern HA — apologies for the incorrect guidance.

Working workaround for modern HA

Since AlertTicker monitors state entities, the cleanest approach is to create a small helper per notification category and set/clear it alongside your existing persistent_notification.create action — no logic duplication, just an extra line per automation:

1. Create a helper (Settings → Helpers → Toggle) — e.g. input_boolean.notify_battery_alert

2. Update your automation:

• action: persistent_notification.create
  data:
  title: "🔋 Battery Alert"
  message: "{{ trigger.to_state.name }} is at {{ trigger.to_state.state }}%"
  notification_id: "battery_alert"
• action: input_boolean.turn_on
  target:
  entity_id: input_boolean.notify_battery_alert

3. Dismiss the helper when the notification clears (add to your dismiss automation or condition):

• action: input_boolean.turn_off
  target:
  entity_id: input_boolean.notify_battery_alert

4. AlertTicker config:

type: custom:alert-ticker-card
alerts:

• entity: input_boolean.notify_battery_alert
  state: "on"
  message: "🔋 Battery alert — check sidebar for details"
  theme: notification
  priority: 3
  It's one helper per notification category rather than fully automatic, but it's the only reliable path on modern HA. Sorry again for the initial wrong answer!