LSH-Assistance
commented
2 years ago The temperatures are stored as binary and there seems to be an issue with negative numbers. Let me quote from another discussion on the openhab community: "_Here’s a clue - 4096 happens to be a magic number in binary = 0001000000000000 I’ll make an assumption that temp 0.5 is actually sent as 05 and the binding has to divide by ten. binary = 0000000000000101 So when you log 409.5 the binary would be 4095 = 0000111111111111 which can also be interpreted as a 12-bit negative binary number with value -1 (-0.1 when scaled)
I’d be fairly confident that you can make your own correction here with something as simple as if myvalue > 300 then myvalue = myvalue - 409.6_" (see https://community.openhab.org/t/innogy-room-thermostat-at-400-c/104156/2)
Apollon77
smash-666
If the temperature of the HKT goes into the minus range, then no negative values are displayed, but temperatures above 400 degrees. I believe that it is not a BUG in the adapter, but the innogy API really delivers these values. I had already seen this on a smartphone app (mySmarthome) and wrote it to the developer. It converts these values so that correct temperature values in the nagative range result from the incorrect values of the API. Is it possible to program this for this adapter too, so that the values are correctly displayed in the ioBroker?