New DSMR-binding for OpenHAB 2

[menzosteinhorst]

I keep getting the following error:

2017-08-22 16:15:19.341 [WARN ] [ab.binding.dsmr.internal.DSMRBinding] - Invalid value 1.0 for dsmr:gas.channel. Ignore mapping!
java.lang.NumberFormatException: For input string: "1.0"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)[:1.8.0_121]
at java.lang.Integer.parseInt(Integer.java:580)[:1.8.0_121]
at java.lang.Integer.parseInt(Integer.java:615)[:1.8.0_121]
at org.openhab.binding.dsmr.internal.DSMRBinding.updated(DSMRBinding.java:220)[188:org.openhab.binding.dsmr:1.10.0]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1461)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1417)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)[3:org.apache.felix.configadmin:1.8.12]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]

How to get rid of this? I didn’t change anything in the settings.

[menzosteinhorst]

Hi Bauke,

As soon as you save the config in expert mode it replaces the values for double values. Eg 1.0 instead of 1.
If you do a change, retype everything, and it will be fine… As a workaround at least…

[rvdbreemen (Robert van den Breemen)]

Hi Marcel,
Sorry to bother you as a beginner of openhab2. I have read this thread. What do I need to do to just try the latest DSMR binding with my openhab2.1 install. I have tried installing the binding using the PaperUI. It gets dsmr1.10 which I suspect is the old binding.

Hope you can help me to get it going, thanks so much.
My troubleshooting thread:
https://community.openhab.org/t/trouble-configuring-dsmr-binding-with-oh2

Regards,
Robert

[diederikd (Diederik)]

@rvdbreemen Currently I am using openhab2 with dsmr binding version 2.1.0. I just send you a message on twitter to send me your email address. Then I will send you the jar file that I use.

[rvdbreemen (Robert van den Breemen)]

Thanks Diederik. It helped talking to you! Next step persistense and a graph.

[QNimbus (Bas)]

@mvolaart Thanks for creating an OpenHAB 2 binding for the DSMR, I really appreciate it.

I’m running into an issue with the binding however; hope you know how to resolve this :

My DSMR for electricity is a

Landis+Gyr SMR 5.0 ZMF110CCtFs2 CDMA (SMR 5.0)

My DSMR for gas is a

Flonidan SMR 5.0 G4 G6 (SMR 5.0)

• My openhab.log file is spammed with the following log entries (every second or so) :

2017-11-10 12:59:57.182 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters
2017-11-10 12:59:58.189 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters
2017-11-10 12:59:58.238 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: []
2017-11-10 12:59:58.240 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: []

• I think the above might be related to my second question; I have two DSMR’s in my metering cabinet. One for electricity and one for gas. The gas meter sends its measurements wirelessly to the electricity meter. But the gas meter doesn’t show up as a ‘Thing’ in OpenHAB. I only have my electricity meter as a Thing and as such am only able to get readings from the electricity meter.

So basically two unresolved issues for me: not being able to get measurements from my gas meter and getting my log file spammed with messages about ‘unhandled CosemObjects’. Just to clarify, I have no issues with reading from the electricity meter.

Additional info (Output from cu -l /dev/ttyUSB0 -s 115200 --parity=none -E q) :

1-3:0.2.8(50)
0-0:1.0.0(000101010000W)
0-0:96.1.1(4530303436303033383634383834373137)
1-0:1.8.1(000184.333kWh)
1-0:1.8.2(000000.000kWh)
1-0:2.8.1(000000.000kWh)
1-0:2.8.2(000000.000kWh)
0-0:96.14.0(0001)
1-0:1.7.0(00.522kW)
1-0:2.7.0(00.000kW)
0-0:96.7.21(00011)
0-0:96.7.9(00000)
1-0:99.97.0(0)(0-0:96.7.19)
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00000)
1-0:52.36.0(00000)
1-0:72.36.0(00000)
0-0:96.13.0()
1-0:32.7.0(0237.0V)
1-0:52.7.0(0237.0V)
1-0:72.7.0(0236.0V)
1-0:31.7.0(1.30A)
1-0:51.7.0(0.97A)
1-0:71.7.0(1.41A)
1-0:21.7.0(00.114kW)
1-0:41.7.0(00.154kW)
1-0:61.7.0(00.253kW)
1-0:22.7.0(00.000kW)
1-0:42.7.0(00.000kW)
1-0:62.7.0(00.000kW)
0-1:24.1.0(003)
0-1:96.1.0(0000000000000000000000000000000000)
!BA95
/XMX5LGBBLA4412138089

Note: My gas meter is now at approx. 66M^3, which I cannot find in the serial port communication above - so maybe the gas meter isn’t properly connected to the electricity meter?

Update: I just had a phone call with the network supplier and they informed me that it’s possible that it takes about 14 working days (meter has been installed 10 days ago) for the meter to get a proper connection via CDMA. Not sure if this also fixes the gas meter not reporting to the electricity meter (which is located 40cm above it)…

Hope you help resolve this issue for me!

Kind regards,

Bas

[casperleenheer]

Hi,
**** This is a none issue. I had to remove the old dsmr things and there it start working again. So if your meter is replaced, remove the old dsmr things except the port… ****

I just got a new Smart Meter (Sagemcom XS210 ESMR5), because my old one was broken. It’s dsmr v 5.0. Now I’m getting

14:38:52.613 [INFO ] [binding.dsmr.internal.device.DSMRPort] - DSMR Port opened successful
14:38:52.625 [INFO ] [binding.dsmr.internal.device.DSMRPort] - DSMR Port opened successful
14:38:52.634 [INFO ] [binding.dsmr.internal.device.DSMRPort] - DSMR Port opened successful
14:38:54.368 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received unknown Cosem Object(OBIS id: 22.7.0)
14:38:54.398 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received unknown Cosem Object(OBIS id: 1-0:99.97.0)
14:38:54.405 [WARN ] [binding.dsmr.internal.device.DSMRPort] - Dropping 21 CosemObjects due Received P1 telegram is corrupted
14:38:54.414 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'dsmr:dsmrBridge:22e5393d' changed from ONLINE (DUTY_CYCLE): P1 telegram received OK to OFFLINE (COMMUNICATION_ERROR): Read error
14:38:54.416 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'dsmr:device_v4:default' changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
14:38:54.422 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'dsmr:m3_v5_0:1' changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
14:38:54.426 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'dsmr:electricity_v4_2:0' changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
14:38:55.394 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier: 0-0:96.7.20:96.7.9
14:38:56.358 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:56.363 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:56.367 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:56.371 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:56.375 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier: )
1-0:1.8.2
14:38:56.382 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received unknown Cosem Object(OBIS id: 0-1:24.1.0)
14:38:56.388 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:56.392 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier: )
0-0:96.13.0
14:38:56.409 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received unknown Cosem Object(OBIS id: 1-0:32.36.0)
14:38:56.416 [INFO ] [binding.dsmr.internal.device.DSMRPort] - Closing DSMR port
14:38:57.367 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received unknown Cosem Object(OBIS id: 0-1:24.2.1)
14:38:57.373 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:57.377 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:57.382 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:57.387 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:57.392 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:57.398 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:57.402 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier:
14:38:57.408 [WARN ] [ernal.device.cosem.CosemObjectFactory] - Received invalid OBIS identifier: R 5.0

1-3:0.2.8
14:38:57.422 [WARN ] [binding.dsmr.internal.device.DSMRPort] - Dropping 38 CosemObjects due Received P1 telegram is corrupted


I found this on the web (dutch): it uses "UART signal inversion option". Could this be the cause?

https://gathering.tweakers.net/forum/list_messages/1792159

Best regards,

Casper

[casperleenheer]

Hi there,

In one of the first artikels of this thread it says:

Another change I made was to make the serial port reactive instead of polling.

I had a question about this. With my new dsmr 5 device I’m getting, when using a lot of electricity, up to two events per second. My wish would be that I could temper this by polling every x seconds. Is there something I can do to stop the flood of events?

Thanks,

Casper

[pdiender (patrick)]

@mvolaart a big thanks for creating an OpenHAB 2 binding for the DSMR

I’m running into an issue with the binding, that is mentioned above

2017-11-24 23:49:31.497 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V4, channel: -1]
2017-11-24 23:49:41.466 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters
2017-11-24 23:49:41.472 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V4, channel: -1]
2017-11-24 23:49:51.461 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters
2017-11-24 23:49:51.467 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V4, channel: -1]
2017-11-24 23:50:01.432 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters
2017-11-24 23:50:01.438 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V4, channel: -1]
2017-11-24 23:50:11.470 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters
2017-11-24 23:50:11.473 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V4, channel: -1]
2017-11-24 23:50:21.485 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters

My DSMR for electricity is a

KFM5KAIFA-METER

output from

cu -l /dev/ttyUSB0 -s 115200 --parity none

/KFM5KAIFA-METER

1-3:0.2.8(42)
0-0:1.0.0(171119202357W)
0-0:96.1.1(4530303236303030303130363837393134)
1-0:1.8.1(003095.599*kWh)
1-0:1.8.2(003283.520*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0001)
1-0:1.7.0(00.526*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00012)
0-0:96.7.9(00005)
1-0:99.97.0(5)(0-0:96.7.19)(170615124004S)(0000015270*s)(160504100552S)(0000000186*s)(160422115631S)(0000001201*s)(160420145748S)(0000000611*s)(000101000001W)(2147483647*s)
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00000)
1-0:52.36.0(00000)
1-0:72.36.0(00000)
0-0:96.13.1()
0-0:96.13.0()
1-0:31.7.0(001*A)
1-0:51.7.0(000*A)
1-0:71.7.0(000*A)
1-0:21.7.0(00.401*kW)
1-0:22.7.0(00.000*kW)
1-0:41.7.0(00.123*kW)
1-0:42.7.0(00.000*kW)
1-0:61.7.0(00.001*kW)
1-0:62.7.0(00.000*kW)
!AD4B

loglevel TRACE for org.openhab.binding.dsmr

2017-11-25 20:17:18.527 [DEBUG] [ding.dsmr.internal.device.DSMRDevice] - Processed cosemObjects [Cosem Object(type:EMETER_EQUIPMENT_IDENTIFIER, cosemValues:{default=E0026000010687914}), Cosem Object(type:EMETER_DELIVERY_TARIFF1, cosemValues:{default=3122.049}), Cosem Object(type:EMETER_DELIVERY_TARIFF2, cosemValues:{default=3332.392}), Cosem Object(type:EMETER_PRODUCTION_TARIFF1, cosemValues:{default=0.0}), Cosem Object(type:EMETER_PRODUCTION_TARIFF2, cosemValues:{default=0.0}), Cosem Object(type:EMETER_TARIFF_INDICATOR, cosemValues:{default=0001}), Cosem Object(type:EMETER_ACTUAL_DELIVERY, cosemValues:{default=0.41}), Cosem Object(type:EMETER_ACTUAL_PRODUCTION, cosemValues:{default=0.0}), Cosem Object(type:EMETER_POWER_FAILURES, cosemValues:{default=12.0}), Cosem Object(type:EMETER_LONG_POWER_FAILURES, cosemValues:{default=5.0}), Cosem Object(type:EMETER_POWER_FAILURE_LOG, cosemValues:{duration_2=1201, duration_1=186, entries=5, duration_0=15270, timestamp_0=Thu Jun 15 12:40:04 UTC 2017, obisId=0-0:96.7.19, timestamp_4=Sat Jan 01 00:00:01 UTC 2000, timestamp_3=Wed Apr 20 14:57:48 UTC 2016, timestamp_2=Fri Apr 22 11:56:31 UTC 2016, timestamp_1=Wed May 04 10:05:52 UTC 2016, duration_4=2147483647, duration_3=611}), Cosem Object(type:EMETER_VOLTAGE_SAGS_L1, cosemValues:{default=0.0}), Cosem Object(type:EMETER_VOLTAGE_SAGS_L2, cosemValues:{default=0.0}), Cosem Object(type:EMETER_VOLTAGE_SAGS_L3, cosemValues:{default=0.0}), Cosem Object(type:EMETER_VOLTAGE_SWELLS_L1, cosemValues:{default=0.0}), Cosem Object(type:EMETER_VOLTAGE_SWELLS_L2, cosemValues:{default=0.0}), Cosem Object(type:EMETER_VOLTAGE_SWELLS_L3, cosemValues:{default=0.0}), Cosem Object(type:EMETER_INSTANT_CURRENT_L1, cosemValues:{default=1.0}), Cosem Object(type:EMETER_INSTANT_CURRENT_L2, cosemValues:{default=0.0}), Cosem Object(type:EMETER_INSTANT_CURRENT_L3, cosemValues:{default=0.0}), Cosem Object(type:EMETER_INSTANT_POWER_DELIVERY_L1, cosemValues:{default=0.322}), Cosem Object(type:EMETER_INSTANT_POWER_PRODUCTION_L1, cosemValues:{default=0.0}), Cosem Object(type:EMETER_INSTANT_POWER_DELIVERY_L2, cosemValues:{default=0.09}), Cosem Object(type:EMETER_INSTANT_POWER_PRODUCTION_L2, cosemValues:{default=0.0}), Cosem Object(type:EMETER_INSTANT_POWER_DELIVERY_L3, cosemValues:{default=0.001}), Cosem Object(type:EMETER_INSTANT_POWER_PRODUCTION_L3, cosemValues:{default=0.0})]
2017-11-25 20:17:18.529 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - There are unhandled CosemObjects, start autodetecting meters
2017-11-25 20:17:18.530 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type DEVICE_V2_V3 is compatible
2017-11-25 20:17:18.531 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - Meter type DEVICE_V2_V3 has no identification
2017-11-25 20:17:18.532 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - Meter type is compatible and has the following descriptor Meter type: DEVICE_V2_V3, channel: -1
2017-11-25 20:17:18.533 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type DEVICE_V2_V3 is compatible
2017-11-25 20:17:18.534 [DEBUG] [internal.discovery.DSMRMeterDetector] - New compatible meter descriptor Meter type: DEVICE_V2_V3, channel: -1
2017-11-25 20:17:18.535 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type DEVICE_V4 is compatible
2017-11-25 20:17:18.537 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - Meter type DEVICE_V4 has no identification
2017-11-25 20:17:18.538 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - Meter type is compatible and has the following descriptor Meter type: DEVICE_V4, channel: -1
2017-11-25 20:17:18.540 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type DEVICE_V4 is compatible
2017-11-25 20:17:18.541 [DEBUG] [internal.discovery.DSMRMeterDetector] - New compatible meter descriptor Meter type: DEVICE_V4, channel: -1
2017-11-25 20:17:18.542 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type DEVICE_V5 is compatible
2017-11-25 20:17:18.543 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - Meter type DEVICE_V5 has no identification
2017-11-25 20:17:18.544 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - Meter type is compatible and has the following descriptor Meter type: DEVICE_V5, channel: -1
2017-11-25 20:17:18.545 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type DEVICE_V5 is compatible
2017-11-25 20:17:18.546 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_ACE4000 is compatible
2017-11-25 20:17:18.547 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.548 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_ACE4000 is not compatible
2017-11-25 20:17:18.549 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GAS_ACE4000 is compatible
2017-11-25 20:17:18.550 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.551 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GAS_ACE4000 is not compatible
2017-11-25 20:17:18.552 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type HEATING_ACE4000 is compatible
2017-11-25 20:17:18.553 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.554 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type HEATING_ACE4000 is not compatible
2017-11-25 20:17:18.555 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type COOLING_ACE4000 is compatible
2017-11-25 20:17:18.556 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType CMETER_VALUE_V2 not found
2017-11-25 20:17:18.557 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type COOLING_ACE4000 is not compatible
2017-11-25 20:17:18.559 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type WATER_ACE4000 is compatible
2017-11-25 20:17:18.560 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.562 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type WATER_ACE4000 is not compatible
2017-11-25 20:17:18.563 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type SLAVE_ELECTRICITY1_ACE4000 is compatible
2017-11-25 20:17:18.564 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_DELIVERY_TARIFF0 not found
2017-11-25 20:17:18.565 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type SLAVE_ELECTRICITY1_ACE4000 is not compatible
2017-11-25 20:17:18.566 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type SLAVE_ELECTRICITY2_ACE4000 is compatible
2017-11-25 20:17:18.567 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_DELIVERY_TARIFF0 not found
2017-11-25 20:17:18.568 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type SLAVE_ELECTRICITY2_ACE4000 is not compatible
2017-11-25 20:17:18.570 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_V2_1 is compatible
2017-11-25 20:17:18.571 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_EQUIPMENT_IDENTIFIER_V2_X not found
2017-11-25 20:17:18.572 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_V2_1 is not compatible
2017-11-25 20:17:18.573 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GAS_V2_1 is compatible
2017-11-25 20:17:18.576 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType GMETER_EQUIPMENT_IDENTIFIER_V2 not found
2017-11-25 20:17:18.577 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GAS_V2_1 is not compatible
2017-11-25 20:17:18.578 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_V2_2 is compatible
2017-11-25 20:17:18.580 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_EQUIPMENT_IDENTIFIER_V2_X not found
2017-11-25 20:17:18.581 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_V2_2 is not compatible
2017-11-25 20:17:18.582 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GAS_V2_2 is compatible
2017-11-25 20:17:18.584 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType GMETER_EQUIPMENT_IDENTIFIER_V2 not found
2017-11-25 20:17:18.585 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GAS_V2_2 is not compatible
2017-11-25 20:17:18.586 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type HEATING_V2_2 is compatible
2017-11-25 20:17:18.588 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType HMETER_EQUIPMENT_IDENTIFIER_V2_2 not found
2017-11-25 20:17:18.589 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type HEATING_V2_2 is not compatible
2017-11-25 20:17:18.590 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type COOLING_V2_2 is compatible
2017-11-25 20:17:18.591 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType CMETER_EQUIPMENT_IDENTIFIER_V2_2 not found
2017-11-25 20:17:18.592 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type COOLING_V2_2 is not compatible
2017-11-25 20:17:18.594 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type WATER_V2_2 is compatible
2017-11-25 20:17:18.595 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType WMETER_EQUIPMENT_IDENTIFIER_V2_2 not found
2017-11-25 20:17:18.596 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type WATER_V2_2 is not compatible
2017-11-25 20:17:18.597 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_V3_0 is compatible
2017-11-25 20:17:18.599 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.600 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_V3_0 is not compatible
2017-11-25 20:17:18.602 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GAS_V3_0 is compatible
2017-11-25 20:17:18.603 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.604 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GAS_V3_0 is not compatible
2017-11-25 20:17:18.605 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type WATER_V3_0 is compatible
2017-11-25 20:17:18.606 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.608 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type WATER_V3_0 is not compatible
2017-11-25 20:17:18.609 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GJ_V3_0 is compatible
2017-11-25 20:17:18.610 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.612 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GJ_V3_0 is not compatible
2017-11-25 20:17:18.613 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GENERIC_V3_0 is compatible
2017-11-25 20:17:18.614 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.616 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GENERIC_V3_0 is not compatible
2017-11-25 20:17:18.617 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_V4_0 is compatible
2017-11-25 20:17:18.618 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.619 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_V4_0 is not compatible
2017-11-25 20:17:18.621 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type M3_V4 is compatible
2017-11-25 20:17:18.622 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.623 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type M3_V4 is not compatible
2017-11-25 20:17:18.625 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GJ_V4 is compatible
2017-11-25 20:17:18.626 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.627 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GJ_V4 is not compatible
2017-11-25 20:17:18.629 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type SLAVE_ELECTRICITY_V4 is compatible
2017-11-25 20:17:18.630 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.631 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type SLAVE_ELECTRICITY_V4 is not compatible
2017-11-25 20:17:18.632 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_V4_0_4 is compatible
2017-11-25 20:17:18.632 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.633 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_V4_0_4 is not compatible
2017-11-25 20:17:18.634 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_V4_2 is compatible
2017-11-25 20:17:18.635 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.636 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_V4_2 is not compatible
2017-11-25 20:17:18.637 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type ELECTRICITY_V5_0 is compatible
2017-11-25 20:17:18.638 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType EMETER_EQUIPMENT_IDENTIFIER not found
2017-11-25 20:17:18.639 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type ELECTRICITY_V5_0 is not compatible
2017-11-25 20:17:18.640 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type M3_V5_0 is compatible
2017-11-25 20:17:18.641 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.642 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type M3_V5_0 is not compatible
2017-11-25 20:17:18.643 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type GJ_V5_0 is compatible
2017-11-25 20:17:18.644 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.644 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type GJ_V5_0 is not compatible
2017-11-25 20:17:18.645 [DEBUG] [internal.discovery.DSMRMeterDetector] - Trying if meter type SLAVE_ELECTRICITY_V5_0 is compatible
2017-11-25 20:17:18.646 [DEBUG] [ng.dsmr.internal.meter.DSMRMeterType] - required objectType METER_DEVICE_TYPE not found
2017-11-25 20:17:18.647 [DEBUG] [internal.discovery.DSMRMeterDetector] - Meter type SLAVE_ELECTRICITY_V5_0 is not compatible
2017-11-25 20:17:18.648 [INFO ] [ding.dsmr.internal.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V4, channel: -1]
2017-11-25 20:17:18.651 [DEBUG] [.discovery.DSMRMeterDiscoveryService] - DiscoveryResult [thingUID=dsmr:device_v4:default, properties={channel=-1, meterType=DEVICE_V4}, flag=NEW, label=Generic DSMR device, bridgeUID=dsmr:dsmrBridge:22e5393c, ttl=-1, timestamp=1511641038650] for meterDescriptor Meter type: DEVICE_V4, channel: -1

hope this is enough information for you, if not let me know!

Kind regards,

Patrick

[ricadelic (Rick Jongbloed)]

@mvolaart i noticed that you made a lot of enhancements to the OH2 DSMR binding. Your effort in this binding is very much appreciated Would you mind posting a new (alpha) .jar binding file so we can try it out? Thanks a lot!

[mvolaart]

Some very busy months, so excuse me not reply in the mean time.
Likely i have now some time to update the binding.

@QNimbus
In your dump i don’t see any gas data in the raw output. I expect the communication between the gas meter and the DSMR device is not working correctly. This is no binding issue however.

@pdiender
In my development version i see no more problems.

@ricadelic
I will make an new alpha version soon.

[pdiender (patrick)]

Thanks for taking the time to reply, looking forward to try out your new alpha version!

[QNimbus (Bas)]

@mvolaart Thanks for your response; it turned out to be a problem with my DSMR meter (no network connection via CDMA, so I had it replaced for a GPRS model and it’s now working correctly)

[snowbird (Maarten Dekker)]

@mvolaart, looks like the binding, org.openhab.binding.dsmr-2.0.0-SNAPSHOT.zip, does not handle the ISKRA AM550 smart meter correctly.

The meter sends its data every second and a complete telegram is posted below:

/ISK5\2M550T-1012

1-3:0.2.8(50)
0-0:1.0.0(180104231941W)
0-0:96.1.1(4530303434303036393033333132393137)
1-0:1.8.1(000156.167*kWh)
1-0:1.8.2(000071.546*kWh)
1-0:2.8.1(000000.000*kWh)
1-0:2.8.2(000000.000*kWh)
0-0:96.14.0(0001)
1-0:1.7.0(00.519*kW)
1-0:2.7.0(00.000*kW)
0-0:96.7.21(00009)
0-0:96.7.9(00005)
1-0:99.97.0(2)(0-0:96.7.19)(170609063239S)(0000000267*s)(170611001706S)(0000149657*s)
1-0:32.32.0(00000)
1-0:52.32.0(00000)
1-0:72.32.0(00000)
1-0:32.36.0(00002)
1-0:52.36.0(00002)
1-0:72.36.0(00002)
0-0:96.13.0()
1-0:32.7.0(234.8*V)
1-0:52.7.0(232.1*V)
1-0:72.7.0(235.3*V)
1-0:31.7.0(000*A)
1-0:51.7.0(001*A)
1-0:71.7.0(001*A)
1-0:21.7.0(00.122*kW)
1-0:41.7.0(00.237*kW)
1-0:61.7.0(00.158*kW)
1-0:22.7.0(00.000*kW)
1-0:42.7.0(00.000*kW)
1-0:62.7.0(00.000*kW)
0-1:24.1.0(003)
0-1:96.1.0(4730303339303031373633333738373137)
0-1:24.2.1(180104231507W)(00212.529*m3)
!D82C

I am using opehab2 and added the jar into the addons folder, next step was goto Inbox -> DSMR Binding enter the serial port /dev/ttyUSB1
I left the location field empty, not sure if that is correct??

I found four new things:
Dutch Smart Meter (Status: ONLINE)
Generic DSMR device (Status: OFFLINE)
Main electricity meter (Status: OFFLINE)
M3 meter

The first three I could add but the Generic DSMR device and the Main electricity meter are offline.

The M3 meter while adding it gives an error in paperUI (ERROR: 409 - Conflict)

The openhab.log gives every second the following message:

2018-01-04 23:58:38.178 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - There are unhandled messages, start autodetecting meters
2018-01-04 23:58:38.179 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V5, channel: -1, identification: unknown_id, Meter type: M3_V5_0, channel: 1, identification: 4730303339303031373633333738373137, Meter type: ELECTRICITY_V5_0, channel: 0, identification: 4530303434303036393033333132393137]
2018-01-04 23:58:39.174 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - There are unhandled messages, start autodetecting meters
2018-01-04 23:58:39.175 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V5, channel: -1, identification: unknown_id, Meter type: M3_V5_0, channel: 1, identification: 4730303339303031373633333738373137, Meter type: ELECTRICITY_V5_0, channel: 0, identification: 4530303434303036393033333132393137]
2018-01-04 23:58:40.205 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - There are unhandled messages, start autodetecting meters
2018-01-04 23:58:40.207 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V5, channel: -1, identification: unknown_id, Meter type: M3_V5_0, channel: 1, identification: 4730303339303031373633333738373137, Meter type: ELECTRICITY_V5_0, channel: 0, identification: 4530303434303036393033333132393137]
2018-01-04 23:58:41.179 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - There are unhandled messages, start autodetecting meters
2018-01-04 23:58:41.180 [INFO ] [enhab.binding.dsmr.device.DSMRDevice] - Detected the following new meters: [Meter type: DEVICE_V5, channel: -1, identification: unknown_id, Meter type: M3_V5_0, channel: 1, identification: 4730303339303031373633333738373137, Meter type: ELECTRICITY_V5_0, channel: 0, identification: 4530303434303036393033333132393137]

The three added Things in PaperUI:

The remaining Thing in Inbox which cant be added:

Does something needs to be changed into the binding? Or did I made some mistakes from my end?

Thanks,

Maarten

[rtvb (Robert)]

Would it be bood idea to put the binding in the marketplace until it is included in the official repo?

Distributing bindings through the IoT Marketplace

All, As the queue for binding PRs is still too long at thus it has become a common practice to share JARs of unmerged bindings with other users on Github, there was the strong wish to have some easy mechanism to share such bindings. Well, I am happy to announce that we now have an (early) version of such a mechanism in place: The Eclipse IoT Marketplace integration! Here are the details: Eclipse IoT Marketplace The Eclipse IoT Marketplace is a website, which allows people to exchange extensio…

[Jaap (Jaap Schuurman)]

Exactly the same problem :-/

[snowbird (Maarten Dekker)]

Hi Jaap,

I worked around it by simply writing a few lines in GO reading from the serial port and post messages on the local MQTT bus updating the OpenHAB items.

It works for me just fine.

Maarten

[Jaap (Jaap Schuurman)]

Hi Maarten,

Can you elaborate what you wrote in Go (I presume the programming language)… where you stored it, how you let it call the serial bus and how you made the OH2 binding listen to the output from you program instead of a serial bus?

Lots of thanks for the help
Kindest regards,
Jaap.

[snowbird (Maarten Dekker)]

Hi Jaap,

Yeah, its nothing fancy, but it simple does the trick for me to get what I want.

I simply run the executable in the background (for a nice init.d script I was way to lazy).

See the attached go code.

Maarten

[Jaap (Jaap Schuurman)]

Hi Maarten,

I am probably blind… but I do not see any “attached go code” … Can you past it inline in the message?
Me being a ‘snowbird’ means I am still working out how this site works ;-p

Regards,
Jaap.