What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Power | power | W | read only |
| Voltage | voltage | V | read only |
| Current | current | A | read only |
| Energy t1 | energy_t1 | kWh | read only |
| Energy t2 | energy_t2 | kWh | read only |
| Energy t3 | energy_t3 | kWh | read only |
| Energy t4 | energy_t4 | kWh | read only |
| Measurement period | measurement_period | sec · 10…600 | settable |
| Device address | device_address | 0…99999999 | settable |
| Temperature | temperature | °C | 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:
{
"power": 12.4,
"voltage": 230,
"current": 0.06,
"energy_t1": 0,
"energy_t2": 0,
"energy_t3": 0,
"energy_t4": 0,
"measurement_period": 305,
"device_address": 50000000,
"temperature": 21.6,
"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: "Room too warm"
mode: single
triggers:
- trigger: numeric_state
entity_id: sensor.my_device_temperature
above: 26
for: "00:10:00"
actions:
- action: notify.notify
data:
message: "Temperature above 26 °C"
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.