What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| On / off (1) | state_1 | — | settable |
| On / off (2) | state_2 | — | settable |
| After power loss (1) | power_on_behavior_1 | off, on, toggle, previous | settable |
| After power loss (2) | power_on_behavior_2 | off, on, toggle, previous | settable |
| Switch actions (1) | switch_actions_1 | off, on | settable |
| Switch actions (2) | switch_actions_2 | off, on | settable |
| Wall switch type (1) | switch_type_1 | toggle, momentary, multifunction, light_cct_control, light_cct_control_up, light_cct_control_down, light_rgb_control, light_rgb_control_up … | settable |
| Wall switch type (2) | switch_type_2 | toggle, momentary, multifunction, light_cct_control, light_cct_control_up, light_cct_control_down, light_rgb_control, light_rgb_control_up … | settable |
| Operation mode (1) | operation_mode_1 | control_relay, decoupled | settable |
| Operation mode (2) | operation_mode_2 | control_relay, decoupled | settable |
| Scene id (1) | scene_id_1 | 0…255 | settable |
| Scene id (2) | scene_id_2 | 0…255 | settable |
| Group id (1) | group_id_1 | 0…65527 | settable |
| Group id (2) | group_id_2 | 0…65527 | settable |
| Min level (1) | min_level_1 | 1…255 | settable |
| Min level (2) | min_level_2 | 1…255 | settable |
| Max level (1) | max_level_1 | 1…255 | settable |
| Max level (2) | max_level_2 | 1…255 | settable |
| Action (button press) | action | on_1, on_2, off_1, off_2, toggle_1, toggle_2, hold_1, hold_2 … | 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",
"state_2": "ON",
"power_on_behavior_1": "off",
"power_on_behavior_2": "off",
"switch_actions_1": "off",
"switch_actions_2": "off",
"switch_type_1": "toggle",
"switch_type_2": "toggle",
"operation_mode_1": "control_relay",
"operation_mode_2": "control_relay",
"scene_id_1": 128,
"scene_id_2": 128,
"group_id_1": 32764,
"group_id_2": 32764,
"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 '{"state_2":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"power_on_behavior_1":"on"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"power_on_behavior_2":"on"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"switch_actions_1":"on"}'
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.