What it exposes
| Feature | Property | Values | Control |
|---|---|---|---|
| Ev status | ev_status | — | read only |
| Alarms | alarms | — | read only |
| Ev connected | ev_connected | — | read only |
| Charging | charging | — | read only |
| Derated | derated | — | read only |
| Alarm active | alarm_active | — | read only |
| Charge limit with on off | charge_limit_with_on_off | A · 0…32 | settable |
| On / off | state | — | settable |
| Charge limit | charge_limit | A · 6…32 | settable |
| Hardware current limit | hardware_current_limit | A · 6…32 | read only |
| Total active power | total_active_power | kW | read only |
| Total active energy | total_active_energy | kWh | read only |
| Last session energy | last_session_energy | kWh | read only |
| Power | power | W | read only |
| Voltage | voltage | V | read only |
| Current | current | A | read only |
| AC frequency | ac_frequency | Hz | read only |
| Power phase b | power_phase_b | W | read only |
| Power phase c | power_phase_c | W | read only |
| Voltage phase B | voltage_phase_b | V | read only |
| Voltage phase C | voltage_phase_c | V | read only |
| Current phase B | current_phase_b | A | read only |
| Current phase C | current_phase_c | A | read only |
| Single phase | single_phase | — | settable |
| Enable offline | enable_offline | — | settable |
| Time to offline | time_to_offline | s · 0…60 | settable |
| Offline current | offline_current | A · 6…32 | settable |
| Offline single phase | offline_single_phase | — | 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:
{
"ev_connected": false,
"charging": false,
"derated": false,
"alarm_active": false,
"charge_limit_with_on_off": 16,
"state": "ON",
"charge_limit": 19,
"hardware_current_limit": 19,
"total_active_power": 0,
"total_active_energy": 0,
"last_session_energy": 0,
"power": 12.4,
"voltage": 230,
"current": 0.06,
"linkquality": 120
}
Send commands to zigbee2mqtt/my_device/set:
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"single_phase":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"enable_offline":true}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"offline_single_phase":true}'
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.