What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Motion | occupancy | — | read only |
| Human motion state | human_motion_state | none, active, static | read only |
| Illuminance | illuminance | lx | read only |
| Occupancy distance | occupancy_distance | 2…6 | settable |
| Unmanned duration | unmanned_duration | 0…65535 | settable |
| Sensitivity | sensitivity | low, medium, high | 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:
{
"occupancy": false,
"human_motion_state": "none",
"illuminance": 120,
"occupancy_distance": 4,
"unmanned_duration": 32768,
"sensitivity": "low",
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"sensitivity":"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: "Light on motion"
mode: single
triggers:
- trigger: state
entity_id: binary_sensor.my_device_occupancy
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.