What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Input (l1) | input_l1 | — | read only |
| Input (l2) | input_l2 | — | read only |
| Input (l3) | input_l3 | — | read only |
| Input (l4) | input_l4 | — | read only |
| On / off (l11) | state_l11 | — | settable |
| On / off (l12) | state_l12 | — | settable |
| Pulse duration (l11) | duration_l11 | s · 0…3600 | settable |
| Pulse duration (l12) | duration_l12 | s · 0…3600 | settable |
| Trigger (l11) | trigger_l11 | press | settable |
| Trigger (l12) | trigger_l12 | press | 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:
{
"input_l1": false,
"input_l2": false,
"input_l3": false,
"input_l4": false,
"state_l11": "ON",
"state_l12": "ON",
"duration_l11": 1800,
"duration_l12": 1800,
"trigger_l11": "press",
"trigger_l12": "press",
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_l11":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_l12":"TOGGLE"}'
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_l11
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.