DSMR Belgian e-MUCS-1 meter, not all channels are updated

I’ve followed the advise in the documentation to run a scan and look at the ouput. It reports those 6 objects that I mentioned above:

14:49:08.474 [INFO ] [l.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object ‘EMETER_INSTANT_POWER_PRODUCTION_L3’ found in the data: Cosem Object(type:EMETER_INSTANT_POWER_PRODUCTION_L3, cosemValues:{=0.268 kW})
14:49:08.482 [INFO ] [l.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object ‘EMETER_INSTANT_POWER_DELIVERY_L3’ found in the data: Cosem Object(type:EMETER_INSTANT_POWER_DELIVERY_L3, cosemValues:{=0.000 kW})
14:49:08.480 [INFO ] [openhab.event.ItemStateEvent ] - Item ‘MainElectricityMeter_InstantVoltageL3’ updated to 235.1
14:49:08.491 [INFO ] [l.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object ‘EMETER_INSTANT_POWER_DELIVERY_L1’ found in the data: Cosem Object(type:EMETER_INSTANT_POWER_DELIVERY_L1, cosemValues:{=0.013 kW})
14:49:08.499 [INFO ] [l.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object ‘EMETER_INSTANT_POWER_DELIVERY_L2’ found in the data: Cosem Object(type:EMETER_INSTANT_POWER_DELIVERY_L2, cosemValues:{=0.109 kW})
14:49:08.498 [INFO ] [openhab.event.ItemStateEvent ] - Item ‘MainElectricityMeter_InstantCurrentL1’ updated to 0.19
14:49:08.507 [INFO ] [l.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object ‘EMETER_INSTANT_POWER_PRODUCTION_L1’ found in the data: Cosem Object(type:EMETER_INSTANT_POWER_PRODUCTION_L1, cosemValues:{=0.000 kW})
14:49:08.516 [INFO ] [l.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object ‘EMETER_INSTANT_POWER_PRODUCTION_L2’ found in the data: Cosem Object(type:EMETER_INSTANT_POWER_PRODUCTION_L2, cosemValues:{=0.000 kW})

It also asked to provide the full information dump:

/FLU5\xxxxxxxxx_A

0-0:96.1.4(50215)
0-0:96.1.1(xxxxxxxx)
0-0:1.0.0(210227144933W)
1-0:1.8.1(001247.747kWh)
1-0:1.8.2(002330.879
kWh)
1-0:2.8.1(002159.427kWh)
1-0:2.8.2(000812.563
kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.000kW)
1-0:2.7.0(00.149
kW)
1-0:21.7.0(00.013kW)
1-0:41.7.0(00.108
kW)
1-0:61.7.0(00.000kW)
1-0:22.7.0(00.000
kW)
1-0:42.7.0(00.000kW)
1-0:62.7.0(00.271
kW)
1-0:32.7.0(234.5V)
1-0:52.7.0(234.0
V)
1-0:72.7.0(235.1V)
1-0:31.7.0(000.19
A)
1-0:51.7.0(000.80A)
1-0:71.7.0(001.39
A)
0-0:96.3.10(1)
0-0:17.0.0(999.9kW)
1-0:31.4.0(999
A)
0-0:96.13.0()
0-1:24.1.0(003)
0-1:96.1.1(xxxxxxxx)
0-1:24.4.0(1)
0-1:24.2.3(210227144600W)(00996.617*m3)
!9C1E
/FLU5\xxxxxxxx_A

I did cost some effort though, the dump in the trace does not coincide with the actual start and end of the raw data.

I’ve also removed and added the Things again and now I get an extra field emeter_equipment_identifier…

The inactive channels still do not update and the ignored fields are absent.

I’ve found the problem, although I had to dig deep :slight_smile:
The Thing is detected with channel ID 1 but it is actually channel ID 0. I do not know why all the other data channels work with the Channel ID set to 1 but after setting it to 0, it works fine.

Only the emeter_treshold_kw still does not work.

I would really like access to those missing fields, though. They would make a nice graph about how much power I am using on each of my phases.

Hi Johan,

Thanks for the complete data. I can use that to test. I found it misses some channels as you already mentioned. And it also doesn’t set the channel id correctly when there is both a electric and gas meter. Which explains why you needed to set the channel to 0. So I’m going to fix those things.

1 Like

Hi Hilbrand,

thank you for the update and your work on this binding!

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.