I’m about to update my OH env from 2.5.x to 3.x. Under OH 2.5.x i used the binding “IEC 620562-21 Meter” and a USB IR-Reader from volkszaehler connected to a Landis+Gyr E350 series2 with the following config:
and it worked ok so far. Sure, there were some issues with “IOException while trying to read: CR (0x0D) character is expected but not received after data block of data message” from time to time, but nothing critical.
After updating to OH 3.x i realised at first, that there’s no “IEC 620562-21 Meter” binding anymore, instead i found the “Smartmeter” one. I suppose it’s the same just with another name. So i took that one. To my surprise, the config has changed as well. Now it expects a “protocol mode”. From the example on the documentation i think i need mode “C”. But with that and other modes i was not able to connect to the meter. I always get the following error:
An error occurred while calling method 'ThingHandler.initialize()' on 'org.openhab.binding.smartmeter.internal.SmartMeterHandler@4ed6c74a': No enum constant org.openhab.binding.smartmeter.internal.helper.ProtocolMode.C
Does anybody know, what the default config was under the old “IEC 620562-21 Meter” binding? Or is there anything wrong on the new one? Did i miss something?
thank you, i know. But the question is, which mode do i need respectively what’s wrong with my config. Smartmeter asks for that mode but i don’t know which one i have to use. As i wrote, i tested all of them but without success …
yes that is the config unter OH 2.5.x. Now i use OH 3.x with the Smartmeter binding. The question is, which mode i need to use that my meter is working again under OH 3.x and the Smartmeter binding. I already tested all the modes SML, A, B, C and D but i wasn’t successful with either of them. What i’m doing wrong?
same here Landis&Gyr E550
Also using ABC with 9600 baud (or with 300) same (non) results.
Following commands on the linux console gets the data from the meter:
stty -F /dev/ttyUSB4 300 -parodd cs7 -cstopb parenb -ixoff -crtscts -hupcl -ixon -opost -onlcr -isig -icanon -iexten -echo -echoe -echoctl -echoke
echo -n -e ‘\x2F\x3F\x21\x0D\x0A’ > /dev/ttyUSB4
echo -n -e ‘\x06\x30\x30\x30\x0D\x0A’ > /dev/ttyUSB4
I have tried ABC, D and SML modes with no success in reading the meter using the binding.
The logs shows this and then nothing.
2021-01-05 11:20:45.280 [DEBUG] [martmeter.internal.SmartMeterHandler] - Initializing Smartmeter handler.
2021-01-05 11:20:45.281 [DEBUG] [martmeter.internal.SmartMeterHandler] - config port = /dev/ttyUSB5
@robd: How did you get it to work exactly? Which parameters did you use?
I have a similar problem: I want to migrate from the old IEC 620562-21 Meter Binding to the new Smartmeter Binding in preparation to update to OH3 (still on 2.5.10).
The old IEC Binding reads my meter (Logarex) flawlessly, but I cannot get it to work with the new Smartmeter Binding, I have tried all settings.
This is how my log looks:
2021-03-22 23:59:42.481 [INFO ] [ding.smartmeter.internal.MeterDevice] - Opening connection to smartmeter:meter:hauptzaehler
2021-03-22 23:59:53.777 [WARN ] [.iec62056.Iec62056_21SerialConnector] - 1. reading attempt failed: Expected carriage return character not received. Retrying /dev/ttyUSB1...
2021-03-22 23:59:53.778 [WARN ] [.iec62056.Iec62056_21SerialConnector] - Delaying retry by PT10S
2021-03-23 00:00:15.016 [WARN ] [.iec62056.Iec62056_21SerialConnector] - 2. reading attempt failed: Expected carriage return character not received. Retrying /dev/ttyUSB1...
2021-03-23 00:00:15.017 [WARN ] [.iec62056.Iec62056_21SerialConnector] - Delaying retry by PT10S
2021-03-23 00:00:22.491 [WARN ] [ding.smartmeter.internal.MeterDevice] - Timeout occured for smartmeter:meter:hauptzaehler; The source did not signal an event for 40000 milliseconds and has been terminated.
However, I still get the exactly same openHAB log entries as listed before, the smartmeter binding does not want to talk with my meter.
As the reply I got with cat seems valid to me, I don’t know what else to try.