Hi,
I’m using the binding to read a Landis & Gyr 2WR5 district heating meter.
I get all data in and displayed in openhab except where the meter returns multiple values separated by a semicolon. I only get data until the semicolon
Example:
DataSet: 6.8;0497.202;GJ - I just get 0497.202 { iec6205621meter=“district_heating:6.8” }
DataSet: 9.4;100;C&085*C - I just get 100. { iec6205621meter=“district_heating:9.4” }
In many cases the last item (like the GJ in my first example) is simply an indication of the unit for the value. But in my second example it is tuneable parameter for the heating of the house and I’d like to have the value reported.
Any recommendation on to go about getting this value in an item??
It looks like an identical issue where the ‘:’ is now replaced by a ‘;’.
Item config:
Number flowtempmaxreturn “Flow temperatuur in/uit [%.s]” { iec6205621meter=“district_heating:9.4” }
Binding log:
2016-04-13 12:16:44 - DataSet: 9.401;100;C&085C
2016-04-13 12:16:44 - Updateing item flowtempmaxreturn with OBIS code 9.4 and value 100
I guess the issue is that the binding only assigns a single value to an item (up until the next semicolon).
If you look at the structure of the data:
DataSet:id;val1;val2
only val1 is assigned to an item, val2 is discarded.
the 3 “;” separated items are
DataSet: 9.401;100;C&085C
OBIS;Value;unit
So my guess is that C&085*C is representing °C
So currently the dataset provides this values including the unit, but the item binding configuration does not allow access to the unit.
I am not sure if the item configuration could be adapted to also represent the unit.
Currently it is manually done in the formatting.
Hi,
In this case “C&085*C” is not the unit.
As you can see from the log below, most of the data is properly formatted, with the unit behind the last ;
Dataset: 9.4 is supposed to return two numbers: flow temperature IN and flow temperature OUT. In this case 100 and 85 degrees Celsius.
The data for this entry is oddly formatted, but it’s not the unit.
ok , got the point.
seems to be a bit strange as for most dataset it looks like following unit for 3rd entry.
I have looked into the code from openmuc to get an understanding how units are decoded from the bytes receive and I could not see any specific rule to deal with 2 values.
If you could share more details about the device we may contact the openmuc team to get some feedback from them.
Also looking into the IEC standard does not show that dataset my contain 2 values.
Address (Value*Unit)
While I connected the meter I was exited to get this tunable parameter data from it, now it gets warmer, the values do not change at all.
It turns out 9.4 is just a static value. So the interest in getting this resolved is gone (at least for me).
