rhizomatics/supernotify v2.7.0 on GitHub

Scenario and recipients are now real switch entities
Sent/failure notification counters are now real Home Assistant sensor entities
New real entities are grouped under a single SuperNotify device, instead of hand-written state writes with no Entity behind them - same entity_ids, no reconfiguration needed
Fixes the notification/failure counters resetting to 0 on every Home Assistant restart - they now restore their last value
The scenario binary_sensor stays read-only for conditional scenarios, as the place to see whether a scenario's conditions currently apply, while its new switch says whether it is enabled.
- A scenario with no conditions has a Scenario Manual read/write binary_sensor, which stays the way to control it from outside Supernotify: while it is on the scenario applies, as if its conditions held, and its state is restored across a restart
The recipient binary_sensor only mirrors the recipient switch, so is deprecated and will be removed in a future version. It is read-only, and not created on a new install, or for a recipient added to an existing one. A repair is raised once if you have it enabled
Delivery and transport binary_sensors are otherwise unchanged for now - a separate, larger conversion to switch entities is tracked in issue #175 - but now belong to the config entry

The notify entities created for recipients now have the timestamp changed however they were notified by SuperNotify (previously only updated if the Notify Entity itself was used, as in send_message)
Home Assistant context is used for the Notify Entity timestamp, so its possible to look at a sent timestamp on an entity and see why it was notified

Each scenario and recipient now has a switch, switch.supernotify_scenario_<name> or switch.supernotify_recipient_<name>, to enable and disable it
Breaking: writing the state of a scenario or recipient binary_sensor no longer enables or disables it, use the switch instead. The scenario binary_sensor now only reports whether the scenario's conditions hold, and the recipient one mirrors the recipient's enabled flag
Scenario and recipient entity names are translated, and put the type first so each sorts together in the entity list: Scenario <name> and Recipient <name> for the binary_sensors, and Scenario <name> Enabled and Recipient <name> Enabled for the switches

HomeAssistant compatibility moved to 2026.9.3
Fix handling of target specific data, that could lead to targets showing up in other envelopes
If a camera or other image source not available, the mobile push is text only rather than showing with a broken image
Fix a delivery disabled in config but enabled at run-time never being used implicitly or as a fallback
Fix supernotify.refresh_entities failing, as it wrote entity state from outside the event loop

EnityCategory renamed to TargetEntityCategory to avoid naming clash with Home Assistant term

What's Changed

Real entities merge back by @jeyrb in #205
Fix runtime-enabled deliveries in implicit/fallback selection and refresh_entities off-loop write by @lollox80 in #206

Full Changelog: v2.6.0...v2.7.0