What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Report interval | report_interval | 1s, 5s, 10s | settable |
| Sensitivity adjustment | sensitivity_adjustment | high, medium, low | settable |
| Battery | battery | % · 0…100 | read only |
| Voltage | voltage | mV | read only |
| Action (button press) | action | shake, triple_strike, movement | 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:
{
"report_interval": "1s",
"sensitivity_adjustment": "high",
"battery": 87,
"voltage": 2950,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"report_interval":"5s"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"sensitivity_adjustment":"medium"}'
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: "Button"
mode: single
triggers:
- trigger: mqtt
topic: zigbee2mqtt/my_device
value_template: "{{ value_json.action }}"
payload: "shake"
actions:
- action: light.toggle
target:
entity_id: light.living_room
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.