rhizomatics/supernotify v2.3.0

on GitHub

Dedicated Notify Action

• The existing notify action is offered via the HA notify platform, so Supernotify acts as a 'sub-platform'. This has several consequences:
  • The web page in Tools | Actions or the Automations dialog is unfriendly to use with lots of things to put into data section with no help
  • The context for the notification isn't passed down by Home Assistant, since the notification platform doesn't follow the curretnt guidelines
  • This usage of the notification platform is legacy, replaced by Notify Entity which has a very limited action, just title and message
• A new dedicated notify action is now available directly from the Supernotify platform
  • Options otherwise buried in notify.supernotify's generic data: field (priority, delivery, require_scenarios, media, etc) are promoted to their own typed, selector-driven fields, for a richer Developer Tools/automation editor UI, to make configuring even sophisticated notifications hugely easier
  • Camera and image/video URLs are broken out into separate fields to make them easier to use, and also allow the Home Assistant Camera selector to be used
  • Separate optional field for custom targets, like e-mail addresses, Telegram IDs that won't work with Home Assistant built-in selectors. Optional but unnecessary for YAML use, since the target field usage is unchanged.
  • The original context is preserved, so you can trace from a trigger like motion PIR, all the way thru to an alert call and camera PTZ movement
  • No change to the original notify.supernotify action, so nothing breaks, and there's a choice (maximum compatibility with legacy notify, so can easily switch between notify providers, or ease of use and insulated from future deprecations of HA notify)

Tracing Activities

• Home Assistant Context is propagated to all Home Assistant services used
  • For example, if a security camera has a PTZ movement, the Home Assistant Activity view can show what triggered this
  • One important limitation - Home Assistant's own notify platform doesn't pass on the Context it receives, however the newer Notify Entity does.
  • See the 2026.9 Release Blog for more on the new UI support for this
  • An end to end integration test test_integration.test_context_propagates_to_camera_ptz_and_mobile_push demonstrates this working
• New supernotify.notify action propagates any context it rexeives
• Context IDs ( context id, parent context id, user id ) are saved with the archive notification JSON object for debug or analysis

### Technical

• ty type checker reinstalled, and several type usages tightened up
• Avoided the mkdocsalypse by switching docs generation to properdocs

Full Changelog: v2.2.3...v2.3.0