What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Presence | presence | — | read only |
| Illuminance | illuminance | lx | read only |
| Detection delay | detection_delay | s · 0…10 | settable |
| Detection distance | detection_distance | cm · 0…1000 | read only |
| Sensitivity | sensitivity | 0…10 | settable |
| Keep time | keep_time | s · 5…3600 | settable |
| Minimum range | minimum_range | m · 0…1000 | settable |
| Maximum range | maximum_range | m · 50…1000 | 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:
{
"presence": false,
"illuminance": 120,
"detection_delay": 5,
"detection_distance": 500,
"sensitivity": 5,
"keep_time": 1803,
"minimum_range": 500,
"maximum_range": 525,
"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.