What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Reliability | reliability | no_fault_detected, unreliable_other, process_error | read only |
| Fault | fault | — | read only |
| Temperature | temperature | °C | read only |
| Battery | battery | % · 0…100 | read only |
| Voltage | voltage | mV | read only |
| Smoke | smoke | — | read only |
| Low battery | battery_low | — | read only |
| Supervision reports | supervision_reports | — | read only |
| Restore reports | restore_reports | — | read only |
| Test | test | — | read only |
| Warning | warning | — | read only |
| Max duration | max_duration | s · 0…600 | settable |
MQTT: state and commands
Zigbee2MQTT publishes the device state to zigbee2mqtt/my_device (my_device is the name you give the device). An example message:
{
"reliability": "no_fault_detected",
"fault": false,
"temperature": 21.6,
"battery": 87,
"voltage": 2950,
"smoke": false,
"battery_low": false,
"supervision_reports": false,
"restore_reports": false,
"test": false,
"max_duration": 300,
"linkquality": 120
}
The device only reports data and takes no commands.
Watch the topics live from the browser: MQTT client.
Home Assistant automation example
Zigbee2MQTT creates Home Assistant entities from the device name. If it is called my_device, an automation in automations.yaml can look like this:
- alias: "Smoke alarm"
mode: single
triggers:
- trigger: state
entity_id: binary_sensor.my_device_smoke
to: "on"
actions:
- action: notify.notify
data:
message: "Smoke detected!"
Check the YAML: YAML checker.
How to pair it
- In Zigbee2MQTT click Permit join.
- Put the device in pairing mode: usually a long press of the reset button (5–10 s) until the LED blinks; bulbs: switch the power off and on 5–6 times.
- Keep the device close to the coordinator or a router while pairing.
- Give it a clear name: MQTT topics and Home Assistant entities are built from it.
Exact procedure and model notes: the device page in the Zigbee2MQTT docs. No coordinator yet: coordinator picker.