[Request device support] Develco EMI Norwegian HAN

[Jopinder]

Develco Norwegian HAN External Meter Interface

Real-time measurement and reporting of household power.

Product page:
https://www.develcoproducts.com/products/meter-interfaces/emi-norwegian-han/

Technical manual with detailed cluster information:
https://www.develcoproducts.com/media/3747/emizb-132-technical-manual-emi-norwegian-han.pdf

Node:

Node Info:

Basic Node 0000:

Simple Metering 0702:

Electrical Measurement 0B04:

[ebaauw]

Did you read the attributes of the 0x0702 and 0x0b04 clusters? The 0x0b04 seems to show only default values. The 0x0702 suggests you’re currently consuming 8.3 kW. Can you relate this to what the meter is displaying? Life-time consumption is again the default value.

[Jopinder]

Yes, all values are after clicking "read" and the meter shows ~1-1.2kW atm. To open the HAN-port on Norwegian meters we have to ask the power company to do it, and it says on "My pages" that the port is open. So I'm not sure why it shows default values.

I will request a close and re-opening of the port to see if that helps with the values.

[gantonjo-tnm]

Thank you, @Jopinder, for requesting support for the Develco EMI Norwegian HAN. I have one myself, but have not been able to add it to my Conbee II USB adapter, hence I am not able to get any readings into my HomeAssistant server. I have asked my power provider (LOS) to open my HAN port, and they confirmed that they had enabled my HAN port. Even so, I am not able to see my Develco sensor in ConBee II. I tried using the PhosCon web interface as well as the VNC GUI.

Can you tell me (details) how you managed to bind your Develco HAN to your Deconz adapter?

Thanks in advance and Happy New Year.

[Jopinder]

My power company has confirmed the HAN port is opened after some mailing with their support. I'm going to contact the seller over new year (Wattle/Home Control AS) to ask if they have done anything to the firmware as they claim it only works with their gateway.

@gantonjo-tnm I tried to add it via the web-gui and Sensors -> Add new sensor and chose "Other", but it did not show up. I then reset the Develco and added it again via the web ui. It still didn't show up in the web ui, but this time in the VNC UI as connected (but unable to get any readings from the power meter). So nothing special I did I'm afraid.

Btw, I have Skagerak Energi and the Aidon meter, which meter does LOS use?

[gantonjo-tnm]

@Jopinder LOS uses Kamstrup meters.

[einarjh]

I have the same reader, but my Manufacturer Code comes up as 0x117c as opposed to 0x1015. Very strange, this seems to be the code for IKEA? The sensor is not talking directly to my hub, it's only within range of one of my IKEA bulbs.

My reader is bought from Elektroimportøren, and the web shop lists it as compatible with "Homely": https://www.elektroimportoren.no/emi-norsk-han/4514731/Product.html?Event=livesearch

My meter is also from Aidon. I've gotten a confirmation from my power company that my HAN port is enabled.

@gantonjo-tnm I had to upgrade to the latest deCONZ beta before I was able to get cluster information etc. from my HAN sensor. Got it from here: http://deconz.dresden-elektronik.de/raspbian/beta/

Here are my screenshots:

Node info:

0x000:

0x0702:

0x0b04:

[einarjh]

I just realized that the meter is already turning up in Home-Assistant, probably because I'm on the current deCONZ beta?

But alas, it's not showing anything useful yet (the second screenshot is particularly hilarious)

[gantonjo-tnm]

@einarjh: Very interesting. Thanks for the information, allthough I am not sure how to upgrade my Conbee II to the latest Beta version. I am running my Home Assistant in Docker on an old Apple Mac Mini 2.5 that is running Ubuntu 18.04.3 LTS. Deconz is running as Docker image "marthoc/deconz".

[einarjh]

Derp! I just started reading the documentation for EMIZB-132 a bit closer, and found this:

Seems there is an extra step needed to enable metering data from Aidon meters, which both @Jopinder and I have.

[ebaauw]

Best define these attributes in general.xml and set them thru the deCONZ GUI. You would need to know the type of each attribute.

[gantonjo-tnm]

@einarjh Ok, I managed to update my Docker image to latest "marthoc/deconz", but even so I am not able to find my Develco EMI Norwegian HAN adapter. I have tried to factory reset it and unplugging it after the reset. No luck binding it to my ConBee II :-(

(Since I used docker-compose, "docker-compose down && docker-compose pull && docker-compose up -d" gave me the latest version of the "marthoc/deconz" Docker image):

[einarjh]

I messed around with this some more tonight, but can't quite get it to work.

As far as I can tell from the manufacturer documentation, the manufacture specific attribute ID 0x0302 needs to be added within the 0x0702 cluster, with the manufacturer code set to 0x1015, so I tried adding it like this (with an educated guess for the type, since this is omitted from the documentation):

<attribute-set id="0x0300" description="Develco Specific" mfcode="0x1015">
  <attribute id="0x0302" name="Interface Mode" type="enum16" access="rw" default="0x0200" showas="hex" required="m" mfcode="0x1015">
    <value value="0x0200" name="Norwegian HAN"></value>
    <value value="0x0201" name="Norwegian HAN - Enable extra load. This is need to enable Adion meter communication"></value>
    <value value="0x0202" name="Norwegian HAN - Aidon Meter supporting Norwegian HAN HW interface"></value>
    <value value="0x0203" name="Norwegian HAN - Kaifa meter and Kamstrup meters running old firmware"></value>
  </attribute>
</attribute-set>

That didn't turn up at all, but when I used the IKEA mfcode, it showed up. Why is my Develco device cloning the manufacturer code for IKEA?

Next problem: the attribute id 0x0302 seems to be conflicting with the attribute id for divisor, when I double click on my new attribute, it brings up the widget for divisor, ref. screenshot:

If I give a fictional, unused attribute set ID, it shows the expected widget with a dropdown, but that won't let me read or write, of course. I get UNSUP_MANUF_GENERAL_COMMAND …

[einarjh]

@gantonjo-tnm Sorry, I can't help you with the connectivity issues. I have a feeling that the meter struggles with the range, though, so make sure your nearest node is close enough. I had to move some of my IKEA lights from the IKEA hub over to deCONZ in order to extend the range. Even now it drops out from time to time.

[Jopinder]

That didn't turn up at all, but when I used the IKEA mfcode, it showed up. Why is my Develco device cloning the manufacturer code for IKEA?

@einarjh That's very strange. My Develco is currently connected to ConBee via an IKEA Trådfri spot, and it keeps all the info, 0x1015 etc.

@gantonjo-tnm Yeah, the range on the Develco is kind of crappy, especially if it's mounted on the inside of the fuse box.

[ebaauw]

so I tried adding it like this

That looks good to me, but you might want to set required to o.

That didn't turn up at all, but when I used the IKEA mfcode, it showed up. Why is my Develco device cloning the manufacturer code for IKEA?

I’m afraid you’re running into a limitation of the GUI: it only shows manufacturer-specific clusters and attributes for the same manufacturer code as the device reports in the Node Descriptor. You see the attribute, but it won’t work, as the device expects a different manufacturer code in the read and write commands.

Why they use the IKEA code is beyond me, I’ve seen iCasa use the Philips code, so their lights are exposed natively to HomeKit by the Hue bridge.

the attribute id 0x0302 seems to be conflicting with the attribute id for divisor

That’s another limitation in the GUI: it doesn’t support manufacturer-specific attributes with the same ID as a standard attribute. Ran into this for the poweron colour settings of Hue lights. If you comment out the standard attribute, you should be able to interact with the manufacturer-specific attribute (if it weren’t for the previous issue).

You could try and access the attributes thru the deconz-cli-plugin, but that’s not for the faint-hearted.

[gantonjo-tnm]

Thanks @einarjh and @Jopinder fro your answers. The distance between my Develco and my ConBee II is not more than 20 cm, so I cannot believe distance is the reason for my problems. In addition I powered off all other Zigbee devices in my home to avoid interference.

[Jopinder]

@einarjh How are you able to edit general.xml? I'm using Hass.io/HassOS, and each time I copy the edited file back to the deCONZ container and restart it, the file goes back to default.

Is there some way of forcing a reload of general.xml without restarting the container?

I also tried creating a file with the values and adding it as a second source for the ZCLDB with no luck.

[einarjh]

@Jopinder I'm not using docker, I'm using the .deb file directly on a raspbian install.

[einarjh]

I tried resetting and re-adding the meter. It still came back with the wrong manu ID. Then I tried turning off every router and moving my raspberry pi within range of the reader. Same problem, it still came back with the IKEA ID.

Then I went for broke, reset everything, and started from scratch with a blank gateway and then adding it. I had to reset everything about ten times, because the device kept coming up with blank manu ID and no attributes. When I finally got it synced up and showing all the attributes again, the manufacture ID was set to 0x1135, which is the same as the raspBee hat has. It seems to clone the manufacturer ID of whatever router it talks to when it pairs up.

So I'm pretty much stuck. I can't get it to show up with the correct manufacturer ID, which means I can't get it to use the correct measuring mode for my power meter.

Is this a bug in deCONZ or do I have a faulty zigbee device?

[einarjh]

Why they use the IKEA code is beyond me, I’ve seen iCasa use the Philips code, so their lights are exposed natively to HomeKit by the Hue bridge.

Just to re-iterate. My testing indicates that DeConz is not seeing the correct manufacturer code, it's seeing the code from whatever router it is talking to. I have left it connected for a few days now, with no change.

[SwoopX]

@einarjh Ok, I managed to update my Docker image to latest "marthoc/deconz", but even so I am not able to find my Develco EMI Norwegian HAN adapter. I have tried to factory reset it and unplugging it after the reset. No luck binding it to my ConBee II :-(

@gantonjo-tnm not sure if I understand what you're missing. From the screenshot you posted, the EMI is visible (device 0x0CF2). EMI is supported since deconz version .72, so the update was necessary.

@einarjh The reason why you have previously seen a different manufacturer code is 99% a node descriptor issue I also had to fight with on the develco smoke sensors (#2154, #2052, #1653). Long story short: in deconz core, the node descriptor is NULL, although a valid node descriptor response was transmitted from the device. This is still not resolved however, my sensors work now with the changes comitted.

Regarding the metering cluster manufacturer specific attribute: I've seen that while amending general.xml for the EMI, but that one felt fishy. Like @ebaauw already mentioned, it might be hard to have it set. Maybe that's doable with ma-ca's deconz cli plugin. Anyhow, not haveing set this attribute appropriately might be the reason why the measurement values show defaults?

@einarjh happy to include your changes of general.xml in a pull request, if you want.

EDIT
@einarjh I might be able to help you with correcting node info data. Let me test that on my sensors first. If it works, it would also require some help from @Jopinder or @gantonjo-tnm.

[SwoopX]

@einarjh the trick works. You need to open daconz' database with sqlite3 and shut down deconz before. While open, issue the following query and make sure you amend the MAC address to yours:

UPDATE device_descriptors SET data = x'02408015105050000000500000' WHERE device_id = (SELECT id FROM devices WHERE mac = '00:15:bc:AA:BB:CC:DD:EE') AND endpoint = 0 AND type = 2;

I know that data set is not 100% accurate (as it should be DC powered instead of battery), but it will do.

[einarjh]

@SwoopX Perfect! I suspected that messing with some database or cache file would allow me to replace the manufacturer ID somehow, but I didn't know where to start. I am now able to read the value, but not able to write it. Hmmm.

[einarjh]

As to committing my suggested config change, that wouldn't make much sense since one needs to comment out/remove different parts of the file in order to get it to work. Assuming I can make it work.

[SwoopX]

Ah yeah, I see. Well, as @ebaauw suggested, you might wanna give the deconz cli plugin from ma-ca a go. If I recall correctly, it might be able to handle that. I may be able to assist.

[einarjh]

That thing looks daunting. I'll see if I'm able to set it up correctly first.

[einarjh]

OK, I have it set up now, seeing lots of traffic in the nc "shell". Awaiting further instructions :)

[havardthom]

My device probably also has old firmware as I'm getting default values on all interface modes.

{
    "current": 65535,
    "current_phase_b": 65535,
    "current_phase_c": 65535,
    "energy": 0,
    "interface_mode": "aidon_meter",
    "linkquality": 188,
    "power": -8388608,
    "voltage": 65535,
    "voltage_phase_b": 65535,
    "voltage_phase_c": 65535
}
{
    "current": 65535,
    "current_phase_b": 65535,
    "current_phase_c": 65535,
    "energy": 0,
    "interface_mode": "norwegian_han_extra_load",
    "linkquality": 188,
    "power": -8388608,
    "voltage": 65535,
    "voltage_phase_b": 65535,
    "voltage_phase_c": 65535
}

Contacted both Wattle and Develco on wednesday asking for the firmware update, no response yet. Would be awesome if someone with a Wattle/Heimgaard hub could investigate possibilities of fetching these firmware files somehow. Doesn't seem like returning the device is an option either because of covid rules..

[mikke49]

@havardthom I see the same values, having FW version 3.5.3. According to WTell we need to be on minimum version 3.5.6.

I've also contacted both Wattle/Heimgaard and Develco. Wattle has closed my issues, saying that they do not accept devices to do the upgrade, and they are not allowed to share the FW. My request to Develco is still unanswered. I'm glad you also contacted them, maybe more requests can make something happen.

I was tempted to order the Wattle hub at Elkjøp, just to do the FW upgrade and then return the hub with the "åpent kjøp" policy. However, due to covid they temporarily do not accept returns of opened packages.

[oivindoh]

Develco have previously told me Wattle should be able to supply updated firmware, so I think Wattle are engaging in a case of blaming others for their unwillingness to simply publish the FW here.

Obviously they want people to buy the hub instead, where they distribute the same firmware they allege they’re not allowed to distribute.

[havardthom]

Got a reply from Wattle today, pretty much the same as other people got.

Hei Håvard,
Jeg tar sjansen at skrive til deg på svorsk.
Først og fremst beklager at det tatt litt tid at komme tilbake til deg.

Så til saken, vi har undersøkt opp mot produsent av disse sensorene hvis vi har muligheten at dele firmware på annen måte enn via vår OTA firmware. Det viser seg dessverre vi har ikke lov til dette. Vi har skrivet på en NDA og andre villkor som forbyr oss dette. Vi har bestemt at firmware vi har mulighet at dele legges her, som med vår dørlås f eks der vi står som produsent. se her: https://www.heimgard.com/support/vare-produkter/firmware-oppgraderingsfiler/

Vi beklager dette men det lar oss med alternativen:
Hvis du har noen kamrat som har Heimgard som kan oppdatere for deg
Hvis Home Assistant treffer en avtale med produsenten Develco for at inkludere disse filene i HA:s OTA oppdatering
Jeg kunnet gi deg 40% rabatt på en Heimgard pro hub, men ser du sier du ikke har lyst at bli Heimgard bruker så vet ikke om det er et alternativ?

Hadde virkelig ønsket vi kunne gjort deg til viljes da vi hadde tenkt at publisere disse filene hvis vi hadde hatt muligheten.

Hører fra deg hvis du har flere spørsmål.
Ha en god dag

Med vennlig hilsen

@oivindoh Do you have a screenshot of Develco saying Wattle should provide updated firmware, which I could use to confront Wattle?

[havardthom]

I see there is a 45-day return policy for the Heimgard Hub, which could be a last option if they wont release the firmware. https://www.heimgard.com/produkt/heimgard-hub-pro/

[gantonjo-tnm]

Just to give you guys a little information on how I ended up configuring my HomeAssistant instance with the ConBee II stick and the Develco Norwegian HAN EMI. I found the deconz path to be too limiting for me, not only for the EMI unit, but also for my IKEA blinds, lights and corresponding remote controls. So, I deleted the deConz integration and installed ZigBee2MQTT instead. No more mocking around in Phoscon GUI or VNC connection to the deconz. All controlled by the ZigBee2MQTT control panel and the EMI shows up with all sensors as shown in this attached picture.

[gforschi]

I suppose this means a lot of reconfiguring of exiting entities? But no re-pairing needed?

[gantonjo-tnm]

I suppose this means a lot of reconfiguring of exiting entities? But no re-pairing needed?

Well, I had to re-pair the nodes, but that was anyway part of my plan since I upgraded my HA to HomeAssistant OS on a new Intel NUC. So, yes, for the 30 or so nodes this meant a little extra work. However, I am so far happy I did the switch, since it is so much easier to debug when all (raw) messages in the network actually goes through the MQTT server before hitting the HA instance.

[gforschi]

Ah okay, hmm, no, I don't want to go that route yet (138 devices, including 35 groups for lights)
I have the Develco HAN EMI, but it is currently useless :(

[mikke49]

I have engaged in a discussion with tech at Develco regarding access to firmware files for their devices. So far their representative appears to be interested in the problem with being unable to update the EMI HAN meter. Waiting for response now on a question regarding the NDA that Wattle claims is blocking them from publishing the firmware files.

Develco reports version 3.5.7 as the latest firmware for the EMI HAN meter:

As a side track; I also pretty quick changed from using deConz and went for MQTT + Zigbee2MQTT instead. Very happy with this switch as I find it much easier to configure and debug.

[mikke49]

And now a I got the final answer from Develco:

I have to point you in the direction where you have acquired your EMI Norwegian HAN.
We are dealing with B2B only.

So the story ended there. I have acquired my EMI HAN meter from Elkjøp, and they write on the product page that this device requires the Wattle portal. Given this statement I guess there is no use in trying to involve Elkjøp in this discussion about firmware upgrade. And Wattle we already know is unwilling to support this.

I'm sorry to say so, but for me the conclusion will be that all devices from Develco should be avoided, unless you decide to go all in on their HUB and software as well. I cannot recommend anyone to buy these devices since it will be impossible to upgrade the firmware when required.

[havardthom]

Latest zigbee2mqtt release adds OTA support for Develco EMIZB-132: https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.22.0

Firmware v4.0.1 is now available through OTA in zigbee2mqtt !!

I am currently updating my device from the outdated "2017-11-01 12:57" firmware, will report if the device starts working after.

Edit:
Can confirm that the device is now reporting correct values for power, energy, current, voltage attributes.

I've experienced flickering of some of my zigbee lights after updating the device, possibly due to high amount of traffic. Tried changing the Min rep change for InstantaneousDemand from 1 second to 60 seconds, but I still have some light flickering issues. Anyone else experienced this?

[ggjersund]

I'm running the firmware dated "20190711 12:18" last updated via OTA. However, can't seem to get the right data readings, I've tried all the interface_modes, and norwegian_han and norwegian_han_extra_load both seem to have equal data (as below) output while aidon_meter has all data wrong:

Anyone got any idea on how to resolve this? I'm trying to use it on an Aidon 6525 meter.

[SwoopX]

@ggjersund I assume you're in the wrong place here?

[ggjersund]

@SwoopX Yeah, I must have misread parts of the PR here. I'll take up this issue in the proper forums :)

[oivindoh]

Sorry for the noise for others here.

@havardthom - did you do something special to make the device accept the update? I'm struggling to get it to accept the update

Zigbee2MQTT:error 2022-04-05 00:59:13: Update of 'HAN' failed (Device didn't respond to OTA request)
Zigbee2MQTT:debug 2022-04-05 00:59:13: Error: Device didn't respond to OTA request
    at requestOTA (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:196:15)
    at Object.updateToLatest (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:283:21)
    at OTAUpdate.onMQTTMessage (/app/lib/extension/otaUpdate.ts:256:21)

[havardthom]

Sorry for the noise for others here.

@havardthom - did you do something special to make the device accept the update? I'm struggling to get it to accept the update

Zigbee2MQTT:error 2022-04-05 00:59:13: Update of 'HAN' failed (Device didn't respond to OTA request)
Zigbee2MQTT:debug 2022-04-05 00:59:13: Error: Device didn't respond to OTA request
    at requestOTA (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:196:15)
    at Object.updateToLatest (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:283:21)
    at OTAUpdate.onMQTTMessage (/app/lib/extension/otaUpdate.ts:256:21)

No, I do not recall doing anything special. Maybe try resetting the device?

[MrsinNo]

Hi
I got my new EMIZB-132 Develco
There was no problem with connection but mqtt is showing some weird measurements like in this log below
I have tried all Configuring interface mode from here https://www.zigbee2mqtt.io/devices/EMIZB-132.html
but still the same error
Hope You guys can help me

[mikke49]

Those values are the same as I (and others) have experienced with the older EMIZB firmware. After updating the firmware all values will be correct.

[MrsinNo]

Those values are the same as I (and others) have experienced with the older EMIZB firmware. After updating the firmware all values will be correct.

But I already update firmware to 4.0.1 but still the same problem.

[mikke49]

Then I'm at a loss, sorry. But just to make sure; you have requested your grid provider to enable the HAN port on your utility meter?

[MrsinNo]

Then I'm at a loss, sorry. But just to make sure; you have requested your grid provider to enable the HAN port on your utility meter?

You are right I spoke with them today and they enable port for me but i´m still geting not correct all data. I have tried all configurations and norwegian_han is the best (screenshot below) but not perfect.
How do You think, what can i do?

[mikke49]

Tree questions:

• did the readings come through after a while (may be some delay in opening the HAN port)?
• have you tried to disconnect / reconnect the HAN port?
• what brand/model do you have of utility meter?

[MrsinNo]

Tree questions:

• did the readings come through after a while (may be some delay in opening the HAN port)?
• have you tried to disconnect / reconnect the HAN port?
• what brand/model do you have of utility meter?

Yes readings come after a while
Yes I have tried
Brand of meter is Kamstrup

[mikke49]

Then I'm running out of ideas. Neither do I know the Kamstrup meter specifically (using Aidon myself).

One thing, if you haven't tried already, might be to reset the Develco device and connect and pair it from scratch.

[gforschi]

My solution was moving to Zigbee2MQTT

[MrsinNo]

Hi
I'm using Z2M but still having this weird measurements

[Jopinder]

For what it's worth, I gave up on this reader and left it behind when we moved.

I'm now using a Pow-U from https://amsleser.no/ and it works like a charm over MQTT :) They also ship internationally through https://lectronz.com/stores/amsleser