What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Presence | presence | — | read only |
| Detection range | detection_range | m · 1.5…6 | settable |
| Radar sensitivity | radar_sensitivity | 68…90 | settable |
| Target distance | target_distance | cm · 0…1000 | read only |
| Indicator | indicator | — | settable |
| Fading time | fading_time | s · 3…1799 | 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,
"detection_range": 4,
"radar_sensitivity": 79,
"target_distance": 500,
"indicator": false,
"fading_time": 901,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"indicator":true}'
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.