What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Climate | system_mode, preset, local_temperature, occupied_heating_setpoint, occupied_cooling_setpoint | mode, preset, room temperature, heating setpoint, occupied_cooling_setpoint | settable |
| Valve status | valve_status | — | read only |
| Humidity | humidity | % | read only |
| Battery | battery | % · 0…100 | 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:
{
"local_temperature": 20.5,
"occupied_heating_setpoint": 21,
"system_mode": "heat",
"valve_status": false,
"humidity": 46.2,
"battery": 87,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"occupied_heating_setpoint":21.5}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"system_mode":"heat"}'
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.