What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| On / off (1) | state_1 | — | settable |
| After power loss (1) | power_on_behavior_1 | off, on, toggle, previous | settable |
| Power type | power_type | low, medium, high | settable |
| Wall switch type (1) | switch_type_1 | rocker, button, decoupled | settable |
| Action (button press) | action | on_, off_, toggle_ | 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_1": "ON",
"power_on_behavior_1": "off",
"power_type": "low",
"switch_type_1": "rocker",
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_1":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"power_on_behavior_1":"on"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"power_type":"medium"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"switch_type_1":"button"}'
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: "Off at night"
mode: single
triggers:
- trigger: time
at: "23:30:00"
actions:
- action: switch.turn_off
target:
entity_id: switch.my_device_1
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.