What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| AC frequency | ac_frequency | Hz | read only |
| Voltage | voltage | V | read only |
| Power a | power_a | W | read only |
| Power b | power_b | W | read only |
| Power ab | power_ab | W | read only |
| Current a | current_a | A | read only |
| Current b | current_b | A | read only |
| Power factor a | power_factor_a | % | read only |
| Power factor b | power_factor_b | % | read only |
| Energy flow a | energy_flow_a | consuming, producing, sign | read only |
| Energy flow b | energy_flow_b | consuming, producing, sign | read only |
| Energy a | energy_a | kWh | read only |
| Energy b | energy_b | kWh | read only |
| Energy produced a | energy_produced_a | kWh | read only |
| Energy produced b | energy_produced_b | kWh | read only |
| Update frequency | update_frequency | s · 3…60 | settable |
| Timestamp a | timestamp_a | — | read only |
| Timestamp b | timestamp_b | — | 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:
{
"ac_frequency": 0,
"voltage": 230,
"power_a": 0,
"power_b": 0,
"power_ab": 0,
"current_a": 0,
"current_b": 0,
"power_factor_a": 0,
"power_factor_b": 0,
"energy_flow_a": "consuming",
"energy_flow_b": "consuming",
"energy_a": 0,
"energy_b": 0,
"energy_produced_a": 0,
"linkquality": 120
}
The device only reports data and takes no commands.
Watch the topics live from the browser: MQTT client.
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.