rhizomatics/supernotify v2.12.1-beta2 on GitHub

✨ Enhancements

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

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

State icons now defined for each of the published entities, in line with the 'gold' level Home Assistant component quality scale, contributed by @lollox80

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, now using the file system ctime creation time rather than examining the JSON
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.

Full Changelog: v2.12.0...v2.12.1-beta2