rhizomatics/supernotify v2.13.0-beta5 on GitHub

✨ Enhancements

These enhancements support the Supernotify Cards dashboard panels, and work too in the regular Home Assistants Actions page.

### Fallback Deliveries

A delivery can now have one or more other deliveries list under a fallback: key
If the main delivery fails each of these is tried in turn
This also forces the primary delivery into wait-for-response rather than the usual fire-and-forget Home Assistant action calls

There are now two duplicate tracking caches, to make working with the recent simulation / dry_run feature easier

Simulated notifications go into their own tracking cache and are ignored by real notifications
Simulated notifications check both caches, so you debug what would happen right now for real with that notification

Sequence	Second Call
Dry run → Live	Sent (was suppressed as a dupe in 2.12.0)
Live → Dry run	Reported as DUPE, as a live send would be
Dry run → Dry run	Reported as DUPE, so dupe handling can still be tried with dry runs alone

enquire_archive has a new verbosity option
- summary - what happened to each notification in brief, the same as the Assist / MCP tools give
- standard - the archived notification without the debug_trace, the default for a list
- full - everything stored, the default when asking for one notification by id
enquire_archive has a new period option
- Pick a time ending now - last hour, 12 hours, day, week or month, simpler than setting after by hand. Remains limited by the max results set.
- If you also set after, the latter gets priority
after and before time filters now use the Home Assistant time zone settings to be a local time
Faster archive scans, using the file system ctime creation time rather than examining the JSON and combining file read / json parse and filter into a single faster background task for up to 30x speedup

State icons now defined for each of the published entities, in line with the 'gold' level Home Assistant component quality scale, contributed by @lollox80
Switch entities now have an overridden attribute to expose if they have been manually changed

enquire_archive now not so fussy about case when filtering for notification outcome.
enquire_archive no longer opens and parses archive files from outside the after / before times
enquire_configuration was failing when deliveries had conditions with JSON serialization error
Scenario binary_sensor state is now unknown unless live scenarios are switched on with scenario_control: {refresh: true}
- Previously it showed whatever the conditions evaluated to at start up and never changed, so looked live when it wasn't
- enquire_active_scenarios is unaffected, and always evaluates the scenarios as of now
Conditional scenario entities report state as unknown if scenario auto refresh left at the default off setting. Refresh control switch logged at startup.

feat: enquire_archive verbosity daily - counts per local day, with no default limit by @lollox80 in #251
feat: 'overridden' attribute on the scenario, recipient, delivery and transport switches by @lollox80 in #250
feat: supernotify.snooze action - snooze, silence or resume from scripts and dashboards by @lollox80 in #249
refactor: snooze, silence and unsnooze as three actions instead of one with a command by @lollox80 in #252
feat: per-delivery fallback - if this delivery fails, try the next in its list by @lollox80 in #258

Full Changelog: v2.13.0-beta2...v2.13.0-beta5