What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| On / off | state | none, presence, move | read only |
| Presence | presence | — | read only |
| Distance | distance | m | read only |
| Illuminance | illuminance | lx | read only |
| Move sensitivity | move_sensitivity | 0…10 | settable |
| Presence sensitivity | presence_sensitivity | 0…10 | settable |
| Detection distance min | detection_distance_min | m · 0…8.25 | settable |
| Detection distance max | detection_distance_max | m · 0.75…9 | settable |
| Presence timeout | presence_timeout | s · 1…1500 | 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:
{
"state": "none",
"presence": false,
"distance": 0,
"illuminance": 120,
"move_sensitivity": 5,
"presence_sensitivity": 5,
"detection_distance_min": 4,
"detection_distance_max": 5,
"presence_timeout": 751,
"linkquality": 120
}
The device only reports data and takes no commands.
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: "Light on motion"
mode: single
triggers:
- trigger: state
entity_id: binary_sensor.my_device_presence
to: "on"
conditions:
- condition: sun
after: sunset
actions:
- action: light.turn_on
target:
entity_id: light.hallway
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.