What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Carbon monoxide | carbon_monoxide | — | read only |
| CO | co | ppm | read only |
| Gas | gas | — | read only |
| Gas value | gas_value | LEL | read only |
| Silence | silence | — | settable |
| Self test | self_test | checking, check_success, check_failure, others | read only |
| Fault | fault | none, fault, serious_fault, sensor_fault, probe_fault, power_fault | read only |
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:
{
"carbon_monoxide": false,
"co": 0,
"gas": false,
"gas_value": 0,
"silence": false,
"self_test": "checking",
"fault": "none",
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"silence":true}'
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.