Develco Norwegian HAN adapter Reading of data


I have av Develco norwegian HAN adapeter connectetd to my HomeAssistant v 0.103. I can se each cluster attribute in the config part for ZHA. So how do I get hold off these data and make an presentastion in Lovelace ?

I’m also interrested in getting the Develco Norwegian HAN to work correctly. I am currently running HomeAssistant v. 0.105.2 in Docker on my Ubuntu server, with a Conbee II USB adapter. I have successfully attached the Develco HAN adapter to HomeAssistant. Only 2 sensors show up in HA, EMIZB-132 and EMIZB-132-2:

Readings in the database look like this:

       event_id: 5233725
     event_type: state_changed
     event_data: {"entity_id": "sensor.emizb_132", "old_state": {"entity_id": "sensor.emizb_132", "state": "23527.8", "attributes": {"on": true, "power": 5293, "unit_of_measurement": "kWh", "friendly_name": "EMIZB-132"}, "last_changed": "2020-02-09T20:00:09.057974+00:00", "last_updated": "2020-02-09T20:08:02.489909+00:00", "context": {"id": "2d91935cef9a4902a42b5ac095445a36", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "sensor.emizb_132", "state": "23527.8", "attributes": {"on": true, "power": 5380, "unit_of_measurement": "kWh", "friendly_name": "EMIZB-132"}, "last_changed": "2020-02-09T20:00:09.057974+00:00", "last_updated": "2020-02-09T20:08:13.730082+00:00", "context": {"id": "3ed28632a3e84137a117211b91a38618", "parent_id": null, "user_id": null}}}
         origin: LOCAL
     time_fired: 2020-02-09 20:08:13
        created: 2020-02-09 20:08:13
     context_id: 3ed28632a3e84137a117211b91a38618
context_user_id: NULL
*************************** 100. row ***************************
       event_id: 5233726
     event_type: state_changed
     event_data: {"entity_id": "sensor.emizb_132_2", "old_state": {"entity_id": "sensor.emizb_132_2", "state": "0", "attributes": {"on": true, "current": 25280, "voltage": 237, "unit_of_measurement": "W", "friendly_name": "EMIZB-132"}, "last_changed": "2020-02-09T12:27:14.487901+00:00", "last_updated": "2020-02-09T20:08:02.697844+00:00", "context": {"id": "b958e29b838d420f8ecab3daf80ebf6e", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "sensor.emizb_132_2", "state": "0", "attributes": {"on": true, "current": 62280, "voltage": 237, "unit_of_measurement": "W", "friendly_name": "EMIZB-132"}, "last_changed": "2020-02-09T12:27:14.487901+00:00", "last_updated": "2020-02-09T20:08:13.938439+00:00", "context": {"id": "e2f614d3fea64e1e9de125d35e8b2021", "parent_id": null, "user_id": null}}}
         origin: LOCAL
     time_fired: 2020-02-09 20:08:13
        created: 2020-02-09 20:08:13
     context_id: e2f614d3fea64e1e9de125d35e8b2021
context_user_id: NULL

My first problem is that the EMIZB-132-2 sensor constantly shows 0 W in the graph.
Second problem is that hte momentanuous Power reading from EMIZB-132 and momentanuous Voltage and Current readings from EMIZB-132-2 are not possible to use for historial graphs.

How can this be done?

To continue my above post, looking at the deConz GUI, the Simple Metering Cluster looks like this:

And the Electrical Metering Cluster looks like this:

As you see, there are separate values for current and voltage in Phase A, B and C, as well as non-phase specific values.

Looking at the cluster data, I guess the 0 W shown for EMIZB-132-2 sensor originates from the “Current Summation Received” in the “Simple Metering Cluster”, while Voltage and Current originates from the “Electrical Metering Cluster”.

If more information needed, please let me know how to collect it.

Thanks in advance for your help.

How is this going? iam considering buying this device and i hope it is working now?


I managed to get this device showing some data on my dashboard after some tinkering:

I also got two entities in HASS, but only the “total power consumption” entity showed data when adding to the dashboard. I eventually found that the device has more state attributes that contain the additional data I want.

In addition to the sensor.emi.state attribute that shows the total consumption I wanted the sensor.emi.power attribute on the dashboard since that is the current power draw:

'on': true
power: 743
unit_of_measurement: kWh
friendly_name: Total consumption
icon: 'hass:flash'

To get that state attribute to the dashboard I needed to:

  1. Install HACS
  2. Install Custom template UI sensor
  3. Add a custom sensor with the template: {{ state_attr('sensor.emi', 'power') }}
  4. Add the custom sensor to a Lovelace card

Repeat step 3 and 4 to access the data from the second sensor (the one that just reports zero):

'on': true
current: 290
voltage: 236
unit_of_measurement: W
friendly_name: Monitor
device_class: power



I bought this one from Elektroimportøren (over the counter - and now I can’t find the receipt - hm). It’s either broken, or the data from the HAN port is broken (but Elvia claims it must be a problem with the unit).

Device info
by Develco Products A/S
Zigbee Coordinator
Firmware: 0x00030507

It shows completely wrong measurements, and the power and metering comes without any units.

RMS Current: some of the readings may look correct, but sometimes it jumps to single-digit ampere numbers to triple-digit ampere numbers. I’m for sure not using that much electricity. It also stays constant i.e. when I’m boiling tea water.

RMS Voltage: It varies a bit, but it’s usually around 2370V. Should probably be around 237V. I’m quite sure things would regularly have been exploding around me if the RMS voltage was 2370V.

Power: comes up without units. If the unit is kW, then the reading looks more or less correct - but it is not. The consumption is jumping with 3.2 kW when I turn on the tea water boiler. While the fuse can theoretically deliver 3.2 kW, I’m quite sure the fuses would have gone on a daily basis if it did so (as it’s not the only thing connected to that fuse). According to the label it should take 2 kW +/- 0.2 kW.

Energy metered: Comes up without any unit, presumably kWh. The number started does not match the counter on the meter. It usually shows around 108k, but every now and then it jumps up to 880M. I compared the reading from the device with the reading from the Elvia web pages for a full day, the numbers reported by the unit is twice as high as the number reported from the web site.