What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Fan | fan_state | — | settable |
| Fan speed | fan_speed | 0…9 | read only |
| PM2.5 | pm25 | µg/m³ | read only |
| Air quality | air_quality | excellent, good, moderate, poor, unhealthy, hazardous, out_of_range, unknown | read only |
| Led enable | led_enable | — | settable |
| Child lock | child_lock | — | settable |
| Replace filter | replace_filter | — | read only |
| Filter age | filter_age | minutes | read only |
| Device age | device_age | minutes | read only |
| Identify | identify | identify | 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:
{
"fan_speed": 5,
"pm25": 8,
"air_quality": "excellent",
"led_enable": false,
"child_lock": false,
"replace_filter": false,
"filter_age": 0,
"device_age": 0,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"led_enable":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"child_lock":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: "Off at night"
mode: single
triggers:
- trigger: time
at: "23:30:00"
actions:
- action: switch.turn_off
target:
entity_id: switch.my_device
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.