What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Presence | presence | — | read only |
| Battery value | battery_value | % | read only |
| Illuminance | illuminance | lx | read only |
| Brightness value | brightness_value | % · 5…100 | settable |
| Presence time | presence_time | s · 0…60 | settable |
| Presence delay | presence_delay | s · 5…120 | settable |
| Illuminance trigger | illuminance_trigger | 0…10000 | settable |
| Detection cycle | detection_cycle | s · 10…1200 | 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,
"battery_value": 0,
"illuminance": 120,
"brightness_value": 53,
"presence_time": 30,
"presence_delay": 63,
"illuminance_trigger": 5000,
"detection_cycle": 605,
"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.