-
Notifications
You must be signed in to change notification settings - Fork 0
ZHA
Device Sentinel recognizes ZHA natively. A device whose integration domain is zha means ZHA is running, and Device Sentinel classifies it correctly.
On a ZHA house, everything built on the Home Assistant event bus works identically to any other stack. This includes rhythm learning, freeze detection, unavailable detection, and unknown detection. It includes battery threshold and falling detection, and signal recording where devices expose signal entities. The problem list, the daily brief, and all reports work properly for ZHA right now.
Because Device Sentinel is currently built only for Zigbee2MQTT, a ZHA house does not ship with certain features today.
You do not get pairing-window recognition, so a hand re-pair during a pairing window is not set aside and is instead learned as the device's rhythm, unless you use Maintenance Mode. You do not get coordinator outage recognition, so a bridge going down blames the devices for silences instead of explaining them. You also miss the availability of a second opinion beside freeze verdicts, and you do not get a Bridge sensor.
The Zigbee2MQTT versions of these features are described on Zigbee2MQTT and The Bridge and Broker Sensors.
Device Sentinel runs fine on a ZHA house today, but the ZHA-specific features cannot be built without a ZHA user's help. The author has no ZHA devices and refuses to build against documentation alone.
To build these missing features, the project needs a volunteer to provide a reference system with real reference data.
A volunteer will help answer a few open questions. Does ZHA expose a readable coordinator state? What does ZHA emit when a pairing (permit join) window opens and closes? What do its devices' last-seen and signal entities look like in the registry? Finally, what happens on the bus when the coordinator drops and returns?
A volunteer can provide three things.
First, a diagnostics download. Go to Settings, Devices and Services, Device Sentinel, select the three-dot menu, and click Download diagnostics. This file contains device names but no passwords or tokens. It is shared privately, not posted publicly. A private channel will be arranged after you open an issue.
Second, answers to a few questions about your ZHA setup. Provide your coordinator model, roughly how many devices you have, and your mains versus battery mix.
Third, a willingness to run a few small experiments and report what happened with timestamps. You will open and close a pairing window at a noted time. You will restart Home Assistant at a noted time. You will briefly unplug and replug the coordinator at a noted time. Each takes minutes, and none of them harms a Zigbee network. Lastly, you may be given a shell command to run in your terminal.
Start the process by using the open an issue link, titled "ZHA reference system".
Device Sentinel is brought to you by James Lander at The Thinking Home. Read the story behind it: Reliable Home Assistant Dead Sensor Detection.
Repository · Report an Issue · Releases · Blueprints
Licensed under GPL-3.0-or-later. Copyright © 2026 James Lander.
Start Here
Configuration
- The Device Page
- Notifications and Daily Brief
- Exclusions and Muting
- Low Battery
- Signal Strength
- Freeze Detection
- Advanced
The Reports
Automations
Understanding
- How Device Sentinel Learns
- Maintenance Mode
- The Bridge and Broker Sensors
- What Is Recorded About Your House
- Built to Be Efficient
Coordinator Stacks
Help