What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Humidity | humidity | % | read only |
| Temperature | temperature | °C | read only |
| CO₂ | co2 | ppm | read only |
| Alarm ringtone | alarm_ringtone | melody_1, melody_2, OFF | settable |
| Backlight | backlight_mode | 1…3 | settable |
| Battery state | battery_state | low, medium, high | read only |
| Air quality | air_quality | excellent, moderate, poor | 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:
{
"humidity": 46.2,
"temperature": 21.6,
"co2": 640,
"alarm_ringtone": "melody_1",
"backlight_mode": 2,
"battery_state": "low",
"air_quality": "excellent",
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"alarm_ringtone":"melody_2"}'
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.