So i have a question maybe some of you can help how do you convert in openhab a 16 bit unsigned to something humanly readable ?
maybe for more inspiration i am looking at a knx group adress with dpd 7.000 from a device and basically that is a temperature sensor reading right now i am getting a value of 0016 in ets monitor wich is 16 degree i believe but if i use lets say 7.001 i get 22 pulses
At least these:
What’s your KNX device connecting the KNX bus to openHAB? How is your KNX bridge configured?
Do other KNX devices work as they should?
What’s running on your openHAB server in parallel to openHAB?
Its a simple question how to read a 7.yyy Wich is a 2 x 8-bit unsigned value from knx in openhab I don’t have problems with communication errors or anything wrong with network VM network cards anything environment java etc
It’s simple. You configure KNX as is and you get the correct values out of it.
If it doesn’t- it has to do something with your environment and/or configuration. But you’re not sharing it, so there’s nothing I can help you with.
I will explain one more time in ets I have a group address with dpd 7.000 that reads in the monitor 0016 as value now the knx device is not certified.
This is what the manual is saying
DATA TYPE VALUES
All of the data type values are simple unsigned whole numbers. Specific
KNX data types are not used. For example, if a 16-bit unsigned value of
20 is written in the group address for the temperature settings,
the temperature will be set at 20 °C. Specific KNX data types for
temperature are not used.
now we’re talking. It has something to do with your environment. Your device just delivers uint16 values to the KNX bus no matter what. That I did not read out of your answers.
Hint: “0016” in hex is not 16 but 22 in integer.
And your question has nothing to do with KNX in the first place. The best way is to use a JS-transformation within your item-definition:
create a .js file in your transform folder containing the transformation from uint16 to decimal
i was looking at this but Calimero mentions it can handle that type of dpd so thinking maybe there is a trick in knx binding to do that directly without profile transformation.
Thank you for the explanation i appreciate it also for the ambiguous questions.