Nous D4Z in Home Assistant
Energy · Zigbee · Smart energy monitor for 3P+N system
Zigbee device – see the note above on what ZHA needs for it.
Facts about this device
- Brand
- Nous
- Model
- D4Z
- Device type
- Energy
- Radio
- Zigbee
- Power
- Mains powered
- Reports itself as
- _TZE204_loejka0i, _TZE284_loejka0i, _TZE200_loejka0i
- Zigbee2MQTT
- Device page on zigbee2mqtt.io
How the device gets into Home Assistant
- official ZHA – with a Zigbee coordinator and the ZHA integration; for all its functions it needs a custom quirk, see above.
- add-on Zigbee2MQTT – Zigbee2MQTT runs as an add-on and passes the device on to Home Assistant over MQTT.
Known problems and fixes
Requests for ZHA support
- support requested The Nous D4Z 3-phase power meter is not supported in ZHA, so its energy measurements cannot be read or displayed in Home Assistant. Adding support would allow monitoring of electricity usage for three-phase systems.
ZHA quirks for this device
Custom quirk shared in an issue Recommended quirk
Shared in the issue tracker as a custom quirk – not reviewed by the ZHA maintainers.
Adds: Total Consumed Energy Total Power Total Power Factor Grid Frequency Phase A Voltage Phase A Current Phase A Power Phase A Consumed Energy Phase A Produced Energy Phase A Power Factor +12
Source:
zha-device-handlers · issue #5461 · by @nocturneop15 · October 15, 2026
Signature: _TZE284_loejka0i / TS0601
Alternatives
The same job from other makers – devices of the same type and radio that work with Home Assistant too.
-
Legrand 412015 Energy · Zigbee · DIN power consumption module Zigbee2MQTT Review
-
Tuya SPM01 Energy · Zigbee · Smart energy monitor for 1P+N system Zigbee2MQTT Custom quirk needed Review
- BTicino F20T60A Energy · Zigbee · DIN power consumption module Zigbee2MQTT Review
- Datek HSE2905E Energy · Zigbee · Datek Eva AMS HAN power-meter sensor Zigbee2MQTT Review
Sources: Zigbee2MQTT, ZHA quirks, Z-Wave JS, the Matter certification database, Shelly, ESPHome, Tasmota, Tuya Local and the issue trackers on GitHub. Reports are assigned to a device by the identifiers they contain; the sentences come from the integration pages, where a language model writes them from the titles.
