What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| On / off | state | — | settable |
| Voltage | voltage | V | read only |
| Power | power | W | read only |
| Energy | energy | kWh | read only |
| Produced energy | produced_energy | kWh | read only |
| Temperature | temperature | °C | read only |
| Current a | current_a | A | read only |
| Power a | power_a | W | read only |
| Power factor a | power_factor_a | % | read only |
| Energy a | energy_a | kWh | read only |
| Reverse energy a | reverse_energy_a | kWh | read only |
| Current b | current_b | A | read only |
| Power b | power_b | W | read only |
| Power factor b | power_factor_b | % | read only |
| Energy b | energy_b | kWh | read only |
| Reverse energy b | reverse_energy_b | kWh | read only |
| Current c | current_c | A | read only |
| Power c | power_c | W | read only |
| Power factor c | power_factor_c | % | read only |
| Energy c | energy_c | kWh | read only |
| Reverse energy c | reverse_energy_c | kWh | read only |
| Power setting a | power_setting_a | W · 0…3680 | settable |
| Power setting b | power_setting_b | W · 0…3680 | settable |
| Power setting c | power_setting_c | W · 0…3680 | settable |
| Power alarm a | power_alarm_a | — | read only |
| Power alarm b | power_alarm_b | — | read only |
| Power alarm c | power_alarm_c | — | read only |
| Voltage calibration | voltage_calibration | V · 0…260 | settable |
| Current a calibration | current_a_calibration | mA · 0…100000 | settable |
| Current b calibration | current_b_calibration | mA · 0…100000 | settable |
| Current c calibration | current_c_calibration | mA · 0…100000 | settable |
| Power a calibration | power_a_calibration | W · 0…3680 | settable |
| Power b calibration | power_b_calibration | W · 0…3680 | settable |
| Power c calibration | power_c_calibration | W · 0…3680 | 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:
{
"state": "ON",
"voltage": 230,
"power": 12.4,
"energy": 3.21,
"produced_energy": 0,
"temperature": 21.6,
"current_a": 0,
"power_a": 0,
"power_factor_a": 0,
"energy_a": 0,
"reverse_energy_a": 0,
"current_b": 0,
"power_b": 0,
"power_factor_b": 0,
"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: "Turn off when idle"
mode: single
triggers:
- trigger: numeric_state
entity_id: sensor.my_device_power
below: 2
for: "00:15: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.