DDF for Develco/frient electricity meter interface 2 EMIZB-141

[github-actions[bot]]

Hey @SwoopX, thanks for your pull request!

[!TIP] Modified bundles can be downloaded here.

DDB changes

Modified

• develco/emizb-141_electricity_meter_interface_2.json : Electricity meter interface 2 EMIZB-141 :heavy_check_mark:

• frient/emizb-141_electricity_meter_interface_2.json : Electricity meter interface 2 EMIZB-141 :heavy_check_mark:

Validation

[!TIP] Everything is fine !

_{:clock530: Updated for commit 6f9ece159c38b952e9e1031bb44e92614fdbe27a}

[aksdb]

Since I am an extreme DDF-noob, can you give me a quick hint what part of the definition is the magic so it works with the overlapping IDs in the Simple Meter cluster? Anytime I tried to get or set the config 0x300 (pulse config), 0x301 (current) or 0x302 (interface mode), it instead read (or tried to write) the other 0x300 (unit of measure), 0x301 (multiplier) or 0x302 (divisor).

Is there some other adressing mechanism that can be leveraged when manually writing/adjusting the DDF?

[SwoopX]

I'm afraid it doesn't work as expected. Within deconz GUI, you cannot work with those overlaping IDs since like forever. Unfortunately, there's a distinction between general and manufacturer specific clusters missing. The respective code is, if I recall correctly, part of the deconz library and not so long open source.

DDFs do not care since they just "do" what you tell them. You might want to check the wiki for the DDF cheat sheet to get some more insights

[github-actions[bot]]

This pull request is now merged. The new DDB files have been uploaded to the store.

DDB Files

Modified

• develco/emizb-141_electricity_meter_interface_2.json : Electricity meter interface 2 EMIZB-141 : with hash (6cc813993d)

• frient/emizb-141_electricity_meter_interface_2.json : Electricity meter interface 2 EMIZB-141 : with hash (af235b1921)

_{:clock5: Updated for commit 3a532053cbeb8df385461e83a4a680683837fdec}