What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Limits calibration | limits_calibration | start, end, reset | settable |
| Automatic calibration | automatic_calibration | calibrate | settable |
| On / off | state | — | settable |
| Curtain speed | curtain_speed | % · 1…100 | settable |
| Manual open close | manual_open_close | — | settable |
| Adaptive pulling speed | adaptive_pulling_speed | — | settable |
| Manual stop | manual_stop | — | settable |
| Reverse direction | reverse_direction | — | settable |
| Status | status | closing, opening, stopped, blocked | read only |
| Last manual operation | last_manual_operation | open, close, stop | read only |
| Curtain position | curtain_position | % · 1…100 | read only |
| Traverse time | traverse_time | sec | read only |
| Calibration status | calibration_status | not_calibrated, half_calibrated, fully_calibrated | read only |
| Calibrated | calibrated | — | read only |
| Identify beep | identify_beep | short, 1_sec, 2_sec | settable |
| 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:
{
"limits_calibration": "start",
"automatic_calibration": "calibrate",
"state": "OPEN",
"curtain_speed": 51,
"manual_open_close": false,
"adaptive_pulling_speed": false,
"manual_stop": false,
"reverse_direction": false,
"status": "closing",
"last_manual_operation": "open",
"curtain_position": 51,
"traverse_time": 0,
"calibration_status": "not_calibrated",
"calibrated": false,
"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 '{"limits_calibration":"end"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"manual_open_close":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"adaptive_pulling_speed":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"manual_stop":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: "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.