What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Action (button press) | action | — | settable |
| Calibrate (l2) | calibrate_l2 | ZERO, SPAN | settable |
| CO₂ | co2 | ppm | read only |
| L2 | l2 | — | read only |
| Temperature (l3) | temperature_l3 | °C | read only |
| L4 | l4 | — | 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:
{
"calibrate_l2": "ZERO",
"co2": 640,
"l2": 0,
"temperature_l3": 21.6,
"l4": 0,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"calibrate_l2":"SPAN"}'
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: "Room too warm"
mode: single
triggers:
- trigger: numeric_state
entity_id: sensor.my_device_temperature
above: 26
for: "00:10:00"
actions:
- action: notify.notify
data:
message: "Temperature above 26 °C"
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.