What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Climate | occupied_heating_setpoint, unoccupied_heating_setpoint, local_temperature, system_mode, pi_heating_demand, running_state | heating setpoint, unoccupied_heating_setpoint, room temperature, mode, pi_heating_demand, running state | settable |
| Thermostat occupancy | thermostat_occupancy | unoccupied, occupied | settable |
| Second display mode | second_display_mode | auto, setpoint, outdoor temp | settable |
| Thermostat outdoor temperature | thermostat_outdoor_temperature | °C · -99.5…99.5 | settable |
| Outdoor temperature timeout | outdoor_temperature_timeout | s · 30…64800 | settable |
| Enable outdoor temperature | enable_outdoor_temperature | — | settable |
| Temperature display mode | temperature_display_mode | celsius, fahrenheit | settable |
| Time format | time_format | 24h, 12h | settable |
| Backlight auto dim | backlight_auto_dim | on_demand, sensing | settable |
| Keypad lockout | keypad_lockout | unlock, lock1 | settable |
| Main cycle output | main_cycle_output | 15_sec, 15_min | settable |
| Eco mode | eco_mode | °C · -10…10 | settable |
| Power | power | W | read only |
| Voltage | voltage | V | read only |
| Current | current | A | read only |
| Energy | energy | kWh | 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:
{
"occupied_heating_setpoint": 21,
"local_temperature": 20.5,
"system_mode": "heat",
"thermostat_occupancy": "unoccupied",
"second_display_mode": "auto",
"thermostat_outdoor_temperature": 0,
"outdoor_temperature_timeout": 32415,
"enable_outdoor_temperature": false,
"temperature_display_mode": "celsius",
"time_format": "24h",
"backlight_auto_dim": "on_demand",
"keypad_lockout": "unlock",
"main_cycle_output": "15_sec",
"eco_mode": 0,
"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"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"thermostat_occupancy":"occupied"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"second_display_mode":"setpoint"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"enable_outdoor_temperature":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.