After using the OH1-binding quite a while ago to successfully read my Landis+Gyr E230, I managed to get the latest version of the iec6205621meter to work under OH2.4.0.
Unfortunately there is an issue: I’m not getting the first few data sets of my meter, i.e. F.F.0, 0.0.0, 1.8.0 and most of the time not even the 4th one (2.8.0) - see below for a proper readout.
Same HW-setup using a python script (sticking to 300 baud) is stable and gives me all OBIS codes configured for readout.
Sometimes I get an error “STX (0x02) character is expected but not received as first byte of data message” with a truncated answer of my meter (usually starting between 2nd and 3rd data set).
This is similar to Iec6205621meter Problem…
There is a ~5 sec gap between “Read meter” and the 1st “DataSet” coming in. Tried messing with the .baudRateChangeDelay and .refresh parameters, but it’s not getting any better.
2019-01-02 15:38:41.611 [DEBUG] [eter.internal.Iec6205621MeterBinding] - Read meter: meter1; /dev/ttyUSB0
2019-01-02 15:38:46.618 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 0AC.K76;;
2019-01-02 15:38:46.619 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: B;C#Wh)
2.8.0;000965.799;kWh
2019-01-02 15:38:46.620 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 0.2.0;K76-0-9;
2019-01-02 15:38:46.620 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: C.5.0;0000E0F0;
2019-01-02 15:38:46.620 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: C.7.0;0005;
2019-01-02 15:38:46.621 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: C.7.1;0020;
2019-01-02 15:38:46.621 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: C.7.2;0019;
2019-01-02 15:38:46.622 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: C.7.3;0023;
2019-01-02 15:38:46.622 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 32.7.0;226;V
2019-01-02 15:38:46.623 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 52.7.0;228;V
2019-01-02 15:38:46.623 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 72.7.0;228;V
2019-01-02 15:38:46.623 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 31.7.0;000.43;A
2019-01-02 15:38:46.624 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 51.7.0;000.48;A
2019-01-02 15:38:46.624 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 71.7.0;001.19;A
2019-01-02 15:38:46.625 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 16.7.0;000.37;kW
2019-01-02 15:38:46.652 [DEBUG] [eter.internal.Iec6205621MeterBinding] - Updating item Leistung with OBIS code 16.7.0 and value 000.37
2019-01-02 15:38:47.654 [DEBUG] [eter.internal.Iec6205621MeterBinding] - Read meter: meter1; /dev/ttyUSB0
2019-01-02 15:38:52.674 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 0AC.K76;;
2019-01-02 15:38:52.677 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: KRsB;:C#Wh)
2.8.0;000965.799;kWh
2019-01-02 15:38:52.678 [DEBUG] [nding.iec6205621meter.internal.Meter] - DataSet: 0.2.0;K76-0-9;
AND
2019-01-02 15:42:31.452 [DEBUG] [eter.internal.Iec6205621MeterBinding] - Read meter: meter1; /dev/ttyUSB0
2019-01-02 15:42:36.528 [ERROR] [nding.iec6205621meter.internal.Meter] - IOException while trying to read: STX (0x02) character is expected but not received as first byte of data message. (hex: 4200000000001730283030373732322e3833382a6b5768290d0a322e382e30283030303936352e3739392a6b5768290d0a302e322e30284b37362d302d39290d0a432e352e30283030303045304630290d0a432e372e302830303035290d0a432e372e312830303230290d0a432e372e322830303139290d0a432e372e332830303233290d0a33322e372e30283232382a56290d0a35322e372e30283232382a56290d0a37322e372e30283232372a56290d0a33312e372e30283030312e32372a41290d0a35312e372e30283030302e34372a41290d0a37312e372e30283030382e37322a41290d0a31362e372e30283030322e32342a6b57290d0a210d0a032f0000…
/LGZ5ZMR120AC.K76
F.F.0(00000000)
0.0.0(3038xxxx)
1.8.0(007722.662kWh)
2.8.0(000965.799kWh)
0.2.0(K76-0-9)
…and so on…