Send a persistent notification

The Send a persistent notification action shows a notification in the Home Assistant interface. Use it for messages you want to keep visible in Home Assistant until someone dismisses them.

Persistent notifications are useful for local reminders, maintenance messages, and other information that should stay available in the notifications panel.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To show a persistent notification from an automation or a script:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create to start a new one.
  3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
  4. In the Then do section, select Add action.
  5. From the search box, search for and select Send a persistent notification.
  6. In Message, enter the notification text.
  7. Optional: In Title, enter a title for the notification.
  8. Optional: In Data, add integration-specific data such as a notification ID.
  9. Select Save.

Options in the UI

Message (Required)

Message body of the notification.

Title (Optional)

Title of the notification.

Data (Optional)

Additional data for the notification. You can include a notification_id to update an existing notification instead of creating a new one.

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.

In YAML, refer to this action as notify.persistent_notification. A basic example looks like this:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: notify.persistent_notification
data:
  title: "Reminder"
  message: "Check the laundry."

This shows a notification in the Home Assistant notifications panel.

Options in YAML

message string Required

Message body of the notification.

title string

Title of the notification.

data map

Additional data for the notification. You can include notification_id to update an existing notification instead of creating a new one.

Good to know

  • Persistent notifications appear in the Home Assistant notifications panel, not as push notifications on a phone or browser.
  • A persistent notification stays visible until someone dismisses it or another action updates or removes it.
  • If you include notification_id in data, Home Assistant updates the existing notification with that ID instead of creating a new notification.
  • To send a message to a notify entity, use Send a notification message.

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

More examples

Real scenarios where this action shows up in automations and scripts. Copy any example and adapt it to your setup.

Tip

You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the automation editor in Home Assistant, and press Ctrl+V (or Cmd+V on Mac). Home Assistant automatically converts the pasted YAML into the visual editor format, whether it’s a full automation, a single trigger, a condition, or an action.

Automation: show a notification when a leak is detected

When a leak sensor detects moisture, show a notification in Home Assistant.

  • Trigger: State
    • Entity: Kitchen leak sensor (binary_sensor.kitchen_leak)
    • To: On
  • Action: Send a persistent notification
    • Title: Water leak detected
    • Message: The kitchen leak sensor detected moisture.
YAML example for a leak notification
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Show a kitchen leak notification"
triggers:
  - trigger: state
    entity_id: binary_sensor.kitchen_leak
    to: "on"
actions:
  - action: notify.persistent_notification
    data:
      title: "Water leak detected"
      message: "The kitchen leak sensor detected moisture."

Automation: keep one water leak notification updated

If a leak sensor reports moisture, show or update one persistent notification with the same notification ID.

  • Trigger: State
    • Entity: Kitchen leak sensor (binary_sensor.kitchen_leak)
    • To: On
  • Action: Send a persistent notification
    • Title: Water leak detected
    • Message: The kitchen leak sensor detected moisture.
    • Data: notification_id: kitchen_leak
YAML example for updating one leak notification
AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]
alias: "Show a kitchen leak notification"
triggers:
  - trigger: state
    entity_id: binary_sensor.kitchen_leak
    to: "on"
actions:
  - action: notify.persistent_notification
    data:
      title: "Water leak detected"
      message: "The kitchen leak sensor detected moisture."
      data:
        notification_id: kitchen_leak

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.

Tip

AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.

Related actions

These actions work well alongside this one: