What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| On / off | state | — | settable |
| Illuminance | illuminance | lx | read only |
| Temperature | temperature | °C | read only |
| Motion | occupancy | — | read only |
| Action (button press) | action | on, off, toggle, brightness_move_to_level, brightness_move_up, brightness_move_down, brightness_step_up, brightness_step_down … | read only |
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": "ON",
"illuminance": 120,
"temperature": 21.6,
"occupancy": false,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state":"TOGGLE"}'
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: "Off at night"
mode: single
triggers:
- trigger: time
at: "23:30:00"
actions:
- action: switch.turn_off
target:
entity_id: switch.my_device
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.
Similar devices
- Schneider Electric 3025CSGZ
- Schneider Electric 41E10PBSWMZ-VW
- Schneider Electric 41E2PBSWMZ/356PB2MBTZ
- Schneider Electric 41ECSFWMZ-VW
- Schneider Electric 545D6514
- Schneider Electric CCT5011-0001/CCT5011-0002/MEG5011-0001
- Schneider Electric NH3526
- Schneider Electric S520530W
- Schneider Electric U201SRY2KWZB
- Schneider Electric U202SRY2KWZB