0.20.0

0.20.0: The Upstream Event Release

Your automations can now react to the failure of your ZHA or Zigbee2MQTT bridge, your MQTT broker, or an integation going down. When the broker stops or a bridge goes down, Device Sentinel tells you on the to-do list and in the daily brief. Now it says so on the event bus as well, so you can act on it.

Added

• Two new events: device_sentinel_upstream_down and device_sentinel_upstream_restored. One fires when a broker or bridge goes down, the other when it comes back. Use either as an automation trigger.
• The events tell you how much is behind the failure. Each carries kind (broker or bridge), name, since, and devices, the number of watched devices that upstream is carrying. So an automation can wake you for a bridge with seventy devices behind it and stay quiet for one with two.
• The recovery says how long it was gone. for_seconds on the restored event.
• Both halves are paired. Every down is answered by a restored, and a restored never arrives without a down before it, so an automation holding a fault always gets to close it.
• Nothing is announced during startup. Device Sentinel stays silent while the rest of your system is still coming up. An upstream that fails during that window and is still down when it ends is announced then, carrying the time it actually failed.

Nothing else changed. Detection, storage, the reports and the to-do list all behave exactly as they did in 0.19.14.