I’m now using Openhab 1.7 with the DSMR binding.
It works well.
Now I should like to start with OH2, what can I expect according the DSMR binding for version OH2?
Thanks to all of you for the effort to develop all these bindings, I’m not skilled enough to do it by myself.
You don’t have to wait for a v2 version of it, simply help testing the 1.x binding and if it works, we can add it to the official distro. See here for details.
For the record, I have used the 1.9 DSMR binding for around a week, without any problems. Logging goes to influxdb and graphing using grafana seems to show the ‘normal’ behaviour.
Thats nice to hear @edejong! This topic was started before PR #4719 was merged. This PR made installing DSMR a one click install in openHAB 2.0. Before that, people had to do some juggling with JAR files. 
Is it included in the distro soon ? cant get 1.x DSMR to work
what’s the problem?
DSMR works fine in OH2.
I specified in a cfg the proper port.
If i add a DSMR thing i get an blank screen.
Im not sure how this must be configured
1.x bindings don’t use Things, configure instead the old fashioned way with item files.
i need to activate the use 1.x bindings ? this is correct ?
now i get constantly a warning in the log : “Did not receive messages from DSMR port, switching port speed.”
and these warnings :
looks like Gas is not recognized.
21:21:24.737 [WARN ] [smr.internal.messages.OBISMsgFactory] - Received OBIS unknown message: 0-1:96.1.0
21:21:24.738 [WARN ] [internal.p1telegram.P1TelegramParser] - Failed to parse: OBISDataLine [OBIS id:0-1:96.1.0, obis values:[3238303131303038323235323033363132]
21:21:24.739 [WARN ] [smr.internal.messages.OBISMsgFactory] - Received OBIS unknown message: 0-1:24.1.0
21:21:24.741 [WARN ] [internal.p1telegram.P1TelegramParser] - Failed to parse: OBISDataLine [OBIS id:0-1:24.1.0, obis values:[03]
21:21:24.742 [WARN ] [smr.internal.messages.OBISMsgFactory] - Received OBIS unknown message: 0-1:24.3.0
21:21:24.745 [WARN ] [internal.p1telegram.P1TelegramParser] - Failed to parse: OBISDataLine [OBIS id:0-1:24.3.0, obis values:[170216210000, 00, 60, 1, 0-1:24.2.0, m3, 05146.057]
21:21:34.305 [WARN ] [smr.internal.messages.OBISMsgFactory] - Received OBIS unknown message: 0-1:96.1.0
21:21:34.307 [WARN ] [internal.p1telegram.P1TelegramParser] - Failed to parse: OBISDataLine [OBIS id:0-1:96.1.0, obis values:[3238303131303038323235323033363132]
21:21:34.309 [WARN ] [smr.internal.messages.OBISMsgFactory] - Received OBIS unknown message: 0-1:24.1.0
21:21:34.312 [WARN ] [internal.p1telegram.P1TelegramParser] - Failed to parse: OBISDataLine [OBIS id:0-1:24.1.0, obis values:[03]
21:21:34.315 [WARN ] [smr.internal.messages.OBISMsgFactory] - Received OBIS unknown message: 0-1:24.3.0
21:21:34.317 [WARN ] [internal.p1telegram.P1TelegramParser] - Failed to parse: OBISDataLine [OBIS id:0-1:24.3.0, obis values:[170216210000, 00, 60, 1, 0-1:24.2.0, m3, 05146.057]
and than mysteriously… it works. No changs, it just works now.