What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Power phase b | power_phase_b | W | read only |
| Power reactive | power_reactive | VAR | read only |
| Power reactive phase b | power_reactive_phase_b | VAR | read only |
| Power apparent | power_apparent | VA | read only |
| Power apparent phase b | power_apparent_phase_b | VA | read only |
| Current phase B | current_phase_b | A | read only |
| Voltage phase B | voltage_phase_b | V | read only |
| Power factor phase b | power_factor_phase_b | — | read only |
| Energy phase a | energy_phase_a | kWh | read only |
| Produced energy phase a | produced_energy_phase_a | kWh | read only |
| Energy phase b | energy_phase_b | kWh | read only |
| Produced energy phase b | produced_energy_phase_b | kWh | read only |
| Total power | total_power | W | read only |
| Total power reactive | total_power_reactive | VAR | read only |
| Total power apparent | total_power_apparent | VA | read only |
| On / off | state | — | settable |
| Power | power | W | read only |
| Voltage | voltage | V | read only |
| AC frequency | ac_frequency | Hz | read only |
| Power factor | power_factor | — | read only |
| Current | current | A | read only |
| Energy | energy | kWh | read only |
| Produced energy | produced_energy | kWh | 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_phase_b": 0,
"power_reactive": 0,
"power_reactive_phase_b": 0,
"power_apparent": 0,
"power_apparent_phase_b": 0,
"current_phase_b": 0,
"voltage_phase_b": 0,
"power_factor_phase_b": 0,
"energy_phase_a": 0,
"produced_energy_phase_a": 0,
"energy_phase_b": 0,
"produced_energy_phase_b": 0,
"total_power": 0,
"total_power_reactive": 0,
"state": "ON",
"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.