---
title: "Supernotify"
description: "Supernotify is a Marketplace integration for Home Assistant. It has 61 installs sharing analytics, works locally and was last updated October 26, 2026."
canonical: "https://vulpo.app/integrations/marketplace/rhizomatics-supernotify"
url: "https://vulpo.app/integrations/marketplace/rhizomatics-supernotify.md"
last-updated: "2026-10-22"
version: "1.4"
---

# Supernotify

> Supernotify is a Marketplace integration for Home Assistant. It has 61 installs sharing analytics, works locally and was last updated October 26, 2026.

Supernotify is an integration that routes and groups notifications across multiple channels from a single notify action. One call can reach mobile apps, e-mail, voice announcements, chimes and other notify platforms, with adaptors adjusting the data for each one. It discovers mobile app devices and recipients from Home Assistant person entities, and it can attach camera snapshots to messages. Notifications can be snoozed or silenced for everyone or one person, limited by delivery, transport, priority, camera or tag. Duplicate detection, an optional archive with MQTT publishing, and debugging actions that show the last notification and the active scenarios are included. It adds buttons, switches, sensors for notifications sent and failures, and tools for Assist, and it is set up in the UI.

Automatic summary of the README and code of rhizomatics/supernotify. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact)

[Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=rhizomatics&repository=supernotify&category=integration)

On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=rhizomatics&repository=supernotify&category=integration)

## Supports

- **Works locally**: Talks to your devices on your own network. No vendor cloud in between.
- **From the Marketplace**: Installed through the Marketplace, formerly HACS.
- **Actively maintained**: Its author released or pushed a change in the last six months.

## Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

### Environment

- **Name**: Determines the registered notify action name (notify.NAME) - change only if you need something other than notify.supernotify, e.g. to match an existing automation
- **Template Path**: Optional location where Jinja2 templates for HTML email are to be found. Relative paths are resolved within the Home Assistant config directory
- **Media Path**: Storage path for media created during notifications, for example camera snapshots created for attachments. Relative paths are resolved within the Home Assistant config directory
- **Media URL Prefix**: URL path prefix under which stored media, such as camera snapshots, is served
- **Mobile Device Discovery**: Automatically discover mobile app devices registered in Home Assistant for push notifications
- **Recipient Discovery**: Automatically discover recipients from Home Assistant person entities

Also asked when changing the connection.

### After setup

- **Enabled**: Turn on the notification archive
- **Archive Path**: Storage path for archived notifications, useful for debugging configuration, scenarios etc. Relative paths are resolved within the Home Assistant config directory
- **Retention Days**: How many days of archived notifications to keep
- **Purge Interval (minutes)**: Minimum interval in minutes between automatic archive purges
- **MQTT Topic**: Optional MQTT topic to publish archived notifications to
- **MQTT QoS**: MQTT quality of service level used when publishing archived notifications
- **MQTT Retain**: Whether archived notifications published to MQTT are retained
- **Event Name**: Home Assistant event name fired for archived notifications
- **Event Selection**: Which notification outcomes fire an event
- **Diagnostics Selection**: Which notification outcomes are recorded with full diagnostic detail
- **Time To Live (seconds)**: How long a notification is remembered for duplicate detection
- **Cache Size**: Maximum number of recent notifications remembered for duplicate detection
- **Duplicate Policy**: How strictly notifications are compared to detect duplicates
- **Housekeeping Time**: Time of day (HH:MM:SS) that scheduled housekeeping, such as media purge, runs
- **Media Storage Days**: How many days of stored media, such as snapshots and attachments, to keep
- **Action tools**: Send notifications, and snooze or silence them
- **Diagnostic tools**: Explain recent notifications, dry-run who a notification would reach, list snoozes, and look up the Supernotify documentation online
- **Built-in agent sentences**: English and Italian sentences for the built-in agent, such as 'tell Alice that dinner is ready' or 'snooze my notifications for 30 minutes'
- **Delivery Inclusion**: Control how Deliveries are considered for inclusion in notifications
- **Spoken delivery occupancy**: Limit when spoken deliveries, such as TTS or Alexa Devices, are considered for notifications, based on home occupancy

Texts from the code of [rhizomatics/supernotify](https://github.com/rhizomatics/supernotify).

## Entities

- **Buttons**: Reset overrides
- **Sensors**: Notifications sent, Notification failures

## Actions

- **Reload**: Reloads supernotify services.
- **Notify**: Send a notification via Supernotify to one or more notification platforms via a single, unified interface.
  Fields: Message, Title, Target, Custom Targets, Priority, Delivery Selection, Delivery, Required Scenarios, Apply Scenarios, Constrained Scenarios
- **Enquire Configuration**: Debugging assistant to show the currently loaded Supernotify configuration
- **Enquire Deliveries By Scenario**: Debugging assistant to show list of deliveries for each scenario, including default usage
- **Enquire Implicit Deliveries**: Debugging assistant to show the deliveries used automatically by default for each transport
- **Enquire Last Notification**: Debugging assistant to show the contents of the last notification sent
  Fields: Diagnostics
- **Enquire Recipients**: Debugging assistant to show the currently configured recipients
- **Enquire Scenarios**: Debugging assistant to show the currently configured scenarios and their attributes
- **Enquire Active Scenarios**: Debugging assistant to show which scenarios are currently active
  Fields: Trace
- **Enquire Occupancy**: Debugging assistant to show the current occupancy status used for delivery targeting
- **Enquire Snoozes**: Debugging assistant to show the currently active snoozes
- **Refresh Entities**: Refresh every entity Supernotify exposes for introspection and control
- **Reset Overrides**: Put every scenario, recipient, delivery and transport switched on or off at runtime back to its configured state
  Fields: Kind
- **Clear Snoozes**: Clear all currently active snoozes
- **Snooze**: Snooze notifications for some minutes - for everyone or one person, everything or only some deliveries, transports, priorities, cameras or tags
  Fields: Scope, Name, Person, Minutes, Reason
- **Silence**: Silence notifications until they are unsnoozed - for everyone or one person, everything or only some deliveries, transports, priorities, cameras or tags
  Fields: Scope, Name, Person, Reason
- **Unsnooze**: Remove the snooze or silence with this scope, name and person
  Fields: Scope, Name, Person
- **Purge Media**: Delete stored media files older than the configured (or given) number of days
  Fields: Days
- **Purge Archive**: Delete archived notification records older than the configured (or given) number of days
  Fields: Days
- **Enquire archive**: Return archived notifications. Without 'id' returns a list (newest first); with 'id' returns one notification's full detail.
  Fields: Notification id, Limit, After, Before, Outcome, Period, Verbosity, Priority

## Troubleshooting

- **Diagnostics**: Downloads a diagnostics file to attach to a bug report.
- **Repair notices**: Notices it can show in Settings, Repairs:
  Supernotify YAML configuration needs to move, Supernotify YAML configuration must be migrated manually, Python 3.13 no longer supported, Invalid Delivery for Scenario, Invalid Mobile Action Group for Scenario, Invalid Condition for Scenario, Unknown Transport for Delivery, Media Path Cannot be Used, Delivery Has Reserved Delivery Name, Delivery Has Invalid Action, Deprecated Generic Transport Action, Mobile App Not Found for Recipient, Notify Entity Already Exists, Delivery Has Invalid Condition, Delivery No Longer Included By Default

## From the README

> Unified Notifications for Home Assistant
>
> !!! tip inline end "Recipes" Get started quickly, or get inspired, with one of the notification recipes, try making Alexa whisper low priority notifications, set off sirens for critical alerts, make the Frigate blueprint send e-mail with attached images, move and zoom a camera to take a snapshot or even have spooky notifications on Halloween.
>
> - One Action -\> Multiple Notifications
> - Remove repetitive config and code from automations
> - Adaptors automatically tune notification data for each integration
> - For example, use with a Frigate Blueprint to get camera snapshots by e-mail instead of, or as well as, mobile notifications. See the Frigate Recipe for more info.
> - Automated set-up
> - Delivery configuration auto-discovered, including for Alexa Devices, Mobile Push, Email (SMTP).
> - Mobile Apps automatically discovered, including Manufacturer and Model of the phone, which can be used to customize delivery
> - Alexa Devices for sending chime noises automatically discovered from Home Assistant
> - Go beyond notify integrations
> - Chimes, sirens, SMS, TTS, Alexa Announcements and Sounds, API calls, MQTT devices, Gotify, ntfy, LaMetric, Pushover, Telegram
> - All the standard notify and notify.group implementations available, including the modern NotifyEntity based ones
> - Greatly simplified use of Mobile Push notifications, e.g. for iPhone

From the README of [rhizomatics/supernotify](https://github.com/rhizomatics/supernotify#readme), [Apache License 2.0](https://spdx.org/licenses/Apache-2.0.html). Shortened.

## At a glance

- Kind: Marketplace integration
- Category: [Messaging and notifications](https://vulpo.app/integrations/category/messaging-and-notifications.md)
- Number: 61 installs sharing analytics; 23 GitHub stars
- Connection: Works locally
- Upkeep: Updated in the last 6 months
- Needs: Needs the Marketplace (HACS on 2026.10 and older)
- Latest version: v2.16.0, last updated October 26, 2026
- Domain: `supernotify`
- Source: <https://github.com/rhizomatics/supernotify>
- Issues: <https://github.com/rhizomatics/supernotify/issues>
- Screenshot: https://vulpo.app/integrations-img/817ba0a28384e0ab.webp (from rhizomatics/supernotify's README)

In Vulpo: Quick Toggle card, Button card, Chart card, Apple Watch, Control Center

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about)

Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/rhizomatics-supernotify

---

- HTML version of this page: https://vulpo.app/integrations/marketplace/rhizomatics-supernotify
- Site index for agents: https://vulpo.app/llms.txt
- Everything in one document: https://vulpo.app/llms-full.txt
- All pages: https://vulpo.app/sitemap.xml
