What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| On / off | state | — | settable |
| Battery | battery | % · 0…100 | read only |
| Voltage | voltage | mV | read only |
| Contact (closed) | contact | — | read only |
| Window opening mode | window_opening_mode | two_position, three_position, four_position, reversed_two_position, reversed_three_position, reversed_four_position | settable |
| Status | status | off, on, moving, stuck, middle, micro_ventilation, tilted | 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:
{
"state": "OPEN",
"battery": 87,
"voltage": 2950,
"contact": true,
"window_opening_mode": "two_position",
"status": "off",
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state":"CLOSE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"window_opening_mode":"three_position"}'
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: "Open the curtains in the morning"
mode: single
triggers:
- trigger: time
at: "07:30:00"
actions:
- action: cover.open_cover
target:
entity_id: cover.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.