Zigbee2MQTT

Zigbee2MQTT

Device Sentinel reads more from Zigbee2MQTT than from any other stack. Everything on this page works without configuring anything.

What You Get

Every Zigbee2MQTT device is watched the same way as any other device in your house: its own rhythm learned, its freeze window set from it, and freeze, unavailable, unknown, battery and signal detection all applied.

Beyond that, three things come from reading the coordinator itself.

Your coordinator is watched. A Bridge: Zigbee2MQTT sensor reads running, binding, down, or unknown. While it is down, you get one row naming the coordinator and how many devices sit behind it rather than a problem per device, and silences that span the outage are set aside rather than learned.

A re-pair is not mistaken for the device's own behavior. The sensor reads binding while a pairing window is open. A device that returns during one is treated as your hand, so the silence before it does not teach a false rhythm. The episode report marks it no (pairing).

A second opinion on every freeze verdict. Zigbee2MQTT publishes its own view of each device's availability, and Device Sentinel shows it beside its own verdict.

Reading the Second Opinion Correctly

The availability reading confirms; it does not decide.

Zigbee2MQTT allows a mains device ten minutes of silence before calling it offline, and a battery device twenty-five hours, because a battery sensor spends most of its life asleep. On a house that is mostly battery sensors, most devices read online long after they have actually stopped reporting. That is not a fault in Zigbee2MQTT; it is what a twenty-five hour window means.

So an online reading beside a freeze verdict is not a contradiction, and Device Sentinel's own learned window is the sharper of the two. An offline reading is worth more: it is the stack agreeing with a fault already found.

If the availability_enabled attribute on the bridge sensor reads false, this feature is switched off in Zigbee2MQTT itself. Turning it on is what adds the second opinion.

One Zigbee2MQTT Instance

Device Sentinel reads one Zigbee2MQTT instance. If you run two on one Home Assistant, the second is not read separately.

See Also

• The Bridge and Broker Sensors, for what each state means and what the broker sensor adds.
• The Diagnostic Reports, for the episode vocabulary these states produce.
• Maintenance Mode, for hand-fixes outside a pairing window.