What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| On / off | state | — | settable |
| Climate | current_heating_setpoint, local_temperature, local_temperature_calibration, running_state | heating setpoint, room temperature, local_temperature_calibration, running state | settable |
| Mode | mode | manual, program, temporary | settable |
| Child lock | child_lock | — | settable |
| Fault | fault | — | read only |
| Upper temperature limit | upper_temperature_limit | °C · 15…95 | settable |
| Frost protection | frost_protection | — | settable |
| Work days | work_days | two-day weekend, single day off, no rest, turn off programming | settable |
| Sound | sound | — | settable |
| Sensor selection | sensor_selection | in, out, all | settable |
| Temperature variation | temperature_variation | °C · 0.5…10 | settable |
| Sensor temperature limit | sensor_temperature_limit | °C · 25…95 | settable |
| Weekly schedule | weekly_schedule | — | read only |
| Backlight | backlight | off, micro light, medium light, high light | settable |
| Direction mode | direction_mode | — | 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:
{
"state": false,
"current_heating_setpoint": 21,
"local_temperature": 20.5,
"mode": "manual",
"child_lock": false,
"upper_temperature_limit": 55,
"frost_protection": false,
"work_days": "two-day weekend",
"sound": false,
"sensor_selection": "in",
"temperature_variation": 5,
"sensor_temperature_limit": 60,
"backlight": "off",
"direction_mode": false,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"current_heating_setpoint":21.5}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"mode":"program"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"child_lock":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"frost_protection":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: "Cooler at night"
mode: single
triggers:
- trigger: time
at: "23:00:00"
actions:
- action: climate.set_temperature
target:
entity_id: climate.my_device
data:
temperature: 18
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.