What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Identify | identify | identify | settable |
| CO₂ | co2 | ppm | read only |
| Lifetime | lifetime | Hours | read only |
| Light | state, brightness | on / off, brightness | settable |
| Night onoff backlight | night_onoff_backlight | — | settable |
| Night on backlight | night_on_backlight | Hr · 0…23 | settable |
| Night off backlight | night_off_backlight | Hr · 0…23 | settable |
| Alarm | alarm | — | settable |
| Alarm volume | alarm_volume | 0…10 | settable |
| Alarm level | alarm_level | ppm · 400…5000 | settable |
| Calibration mode | calibration_mode | — | settable |
| Forced recalibration | forced_recalibration | — | settable |
| Factory reset co2 | factory_reset_co2 | — | settable |
| Manual forced recalibration | manual_forced_recalibration | ppm · 0…5000 | settable |
| Invert logic onoff | invert_logic_onoff | — | settable |
| Enable co2 gas | enable_co2_gas | — | settable |
| High co2 gas | high_co2_gas | ppm · 400…5000 | settable |
| Low co2 gas | low_co2_gas | ppm · 400…5000 | 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:
{
"co2": 640,
"lifetime": 0,
"state": "ON",
"brightness": 180,
"night_onoff_backlight": false,
"night_on_backlight": 12,
"night_off_backlight": 12,
"alarm": false,
"alarm_volume": 5,
"alarm_level": 2700,
"calibration_mode": false,
"forced_recalibration": false,
"factory_reset_co2": false,
"manual_forced_recalibration": 2500,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state":"ON","brightness":180}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state":"OFF","transition":2}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"night_onoff_backlight":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"alarm":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"calibration_mode":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: "Light at sunset"
mode: single
triggers:
- trigger: sun
event: sunset
offset: "-00:15:00"
actions:
- action: light.turn_on
target:
entity_id: light.my_device
data:
brightness_pct: 70
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.