What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Water leak alarm 1 | water_leak_alarm_1 | — | read only |
| Water leak alarm 2 | water_leak_alarm_2 | — | read only |
| Tamper | tamper | — | read only |
| Low battery | battery_low | — | read only |
| On / off (2) | state_2 | — | settable |
| On / off (3) | state_3 | — | settable |
| On / off (4) | state_4 | — | settable |
| On / off (5) | state_5 | — | 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:
{
"water_leak_alarm_1": false,
"water_leak_alarm_2": false,
"tamper": false,
"battery_low": false,
"state_2": "ON",
"state_3": "ON",
"state_4": "ON",
"state_5": "ON",
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_2":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_3":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_4":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_5":"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_2
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.