🐛 Bug fixes
titlewas missing as a top level field in the archived notification, now appears next tomessagefields at the top- The name is now spelt
Supernotifythroughout, as in the integration list, rather than sometimesSuperNotify. This changes the device name, and so the friendly names of its entities, e.g.Supernotify Reset overrides, unless the device has been renamed. Entity ids are unchanged - Supernotify's entries in the Activity view now have their own icon
- Integrations now log only at DEBUG level if they are not going to be setup if the underlying integration isn't even installed (removes a good chunk of startup log noise)
- Chime
- Script chimes on a delivery with
debugset were refused by Home Assistant, from an extrawaitfield - A media player or script chime alias with
datano longer has the data of each notification it is used for added to its own, which could carryannounceand the like over to later notifications - An alias entry with an empty
target, or a label with neitherdomainnortarget, no longer stops the whole chime delivery. The label entry is now ignored with a warning at startup - A
groupin an alias entry'stargetis now expanded to its members, as it already was in a notification's target, rather than being skipped - An alias entry's
domainmust now be one the chime transport supports, and is refused at startup if not
- Script chimes on a delivery with
- Supernotify's own notify entities, for a scenario, delivery or recipient, could make a notification loop forever, held back only by dupe checking, when one was in the
targetof a delivery, scenario or recipient, or called by something a delivery ran- In those targets, a recipient's notify entity is now replaced by the recipient, as it already was in the target of an action call, and a scenario's or delivery's is dropped with a warning
- Any of them, or their
notifyactions, called while a notification is being delivered is ignored with a warning
- Notify Entity
- The docs example for switching off the default delivery used
disabled: false, which isn't a valid option and stopped the configuration loading. It is nowenabled: false, as it is for the same examples for Email and Mobile Push, and every transport example in the docs is now checked against the schema - Docs corrected: device targets aren't supported, there's no
data, and the default delivery is only used for notify entities no other transport takes
- The docs example for switching off the default delivery used
✨ Enhancements
original_tracein the archived notification gives the automation or script run that was in progress when the notification was made, as its tracekeyandrun_id, next tooriginal_context.- Left out for a call from outside an automation or script, and for an automation without an
id, since Home Assistant keeps no trace for those
- Left out for a call from outside an automation or script, and for an automation without an
What's Changed
- ci: pin shared admin workflows to rhizomatics/.github 1.0.0 by @jeyrb in #282
- Bump home-assistant/actions/hassfest from 06749dd8c0b54f350bc69c8752456cee498808a3 to 50baf3a307f87100cf550d4ae127746595030d5d by @dependabot[bot] in #288
- Bump actions/github-script from 8 to 9 by @dependabot[bot] in #287
- Add ci-ok job as the single required CI check by @jeyrb in #290
- Update ruff requirement from >=0.16.0 to >=0.16.10 in the astral group across 1 directory by @dependabot[bot] in #286
- Update types-requests requirement from <3.0.0.0,>=2.33.0.20260906 to >=2.33.0.20261006,<3.0.0.0 by @dependabot[bot] in #284
- Bump astral-sh/setup-uv from 10.2.0 to 10.3.0 in the astral group by @dependabot[bot] in #291
- Bump home-assistant/actions/hassfest from 50baf3a307f87100cf550d4ae127746595030d5d to cd6f3635a740c84d8a14f6121a90068b8ece6bf6 by @dependabot[bot] in #292
- Make the supernotify-dev skill visible to Claude Code by @jeyrb in #295
- Keep personal Claude Code permissions out of the repo by @jeyrb in #296
Full Changelog: v2.15.0...v2.15.1-beta3