Innogy room thermostat at 400°C

[lagom (Jörn)]

Hello everyone,

I’m using the official innogy binding on OH 2.5.8-1. One of my WRT (room thermostat) is placed in the fridge and usually provides the correct temperatures.
I observed that the thermostat seems to deliver wrong values from time to time:

Line 69: 2020-08-25 23:55:29.903 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 409.2 to 409.5
Line 343: 2020-08-25 23:57:52.770 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 409.5 to 0.1
Line 536: 2020-08-26 00:00:00.396 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.1 to 0.3
Line 880: 2020-08-26 00:02:58.680 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.3 to 0.5
Line 1271: 2020-08-26 00:05:41.609 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.5 to 0.7
Line 1543: 2020-08-26 00:08:10.374 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.7 to 0.9
Line 1765: 2020-08-26 00:10:24.864 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.9 to 1.1
Line 1993: 2020-08-26 00:12:24.812 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.1 to 1.3
Line 2287: 2020-08-26 00:15:14.332 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.3 to 1.5
Line 2555: 2020-08-26 00:17:49.542 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.5 to 1.7
Line 2790: 2020-08-26 00:20:10.421 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.7 to 1.9
Line 2971: 2020-08-26 00:22:16.626 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.9 to 2.1
Line 3276: 2020-08-26 00:25:12.738 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.1 to 2.3
Line 3820: 2020-08-26 00:30:21.184 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.3 to 2.0
Line 4022: 2020-08-26 00:32:33.929 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.0 to 1.7
Line 4298: 2020-08-26 00:35:36.022 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.7 to 1.2
Line 4650: 2020-08-26 00:38:23.776 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.2 to 0.7
Line 4923: 2020-08-26 00:40:57.043 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.7 to 0.1
Line 5356: 2020-08-26 00:43:16.193 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.1 to 409.0
Line 5544: 2020-08-26 00:45:20.592 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 409.0 to 408.3
Line 5930: 2020-08-26 00:48:14.600 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 408.3 to 407.8
Line 6166: 2020-08-26 00:50:54.353 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 407.8 to 407.5
Line 6626: 2020-08-26 00:55:30.253 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 407.5 to 407.7
Line 7068: 2020-08-26 00:58:30.883 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 407.7 to 408.1
Line 7337: 2020-08-26 01:01:16.927 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 408.1 to 408.5
Line 7551: 2020-08-26 01:03:48.483 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 408.5 to 408.9
Line 7813: 2020-08-26 01:06:05.920 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 408.9 to 409.3
Line 8055: 2020-08-26 01:08:08.549 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 409.3 to 0.0
Line 8365: 2020-08-26 01:11:00.509 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.0 to 0.2
Line 8624: 2020-08-26 01:13:38.595 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.2 to 0.4
Line 8864: 2020-08-26 01:16:01.826 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.4 to 0.5
Line 9188: 2020-08-26 01:18:10.827 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.5 to 0.7
Line 9430: 2020-08-26 01:21:09.359 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.7 to 0.9
Line 9721: 2020-08-26 01:23:53.590 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.9 to 1.1
Line 10035: 2020-08-26 01:26:23.258 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.1 to 1.3
Line 10362: 2020-08-26 01:28:38.551 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.3 to 1.5
Line 10551: 2020-08-26 01:30:39.558 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.5 to 1.8
Line 10856: 2020-08-26 01:33:30.019 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.8 to 2.0
Line 11103: 2020-08-26 01:36:06.019 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.0 to 2.1
Line 11426: 2020-08-26 01:38:27.863 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.1 to 2.3
Line 11641: 2020-08-26 01:40:35.078 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.3 to 2.4
Line 11959: 2020-08-26 01:43:31.875 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.4 to 2.2
Line 12234: 2020-08-26 01:46:14.443 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 2.2 to 1.8
Line 12560: 2020-08-26 01:48:42.124 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.8 to 1.4
Line 12763: 2020-08-26 01:50:55.628 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 1.4 to 0.8
Line 13047: 2020-08-26 01:53:58.575 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.8 to 0.3
Line 13354: 2020-08-26 01:56:47.328 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 0.3 to 409.3
Line 13669: 2020-08-26 01:59:21.648 [vent.ItemStateChangedEvent] - ClimateFridgeTemperature changed from 409.3 to 408.5

Is this a bug in the binding or is there a way to filter-out these very wrong values before they are send to the item (and remain persistent)?
Could it be that the temperatures above 400 have to be interpreted as negative temperatures by the binding?

[rossko57]

@lagom

is there a way to filter-out these very wrong values

More than one way, depending on your aims. Search for this, example -

Control a heater with multiple sensors

This is a hard problem. As with all hard problems, you need to break it into multiple parts. As rossko57 indicates, you need to figure out how to know that a sensor is not working. Then write code/configuration to reliably detect this in your Rules. You will probably need to use a Proxy Item and a Rule. And of course how you do this depends greatly on the behavior the sensor exhibits when it is not working correctly. Does it stop reporting? Does it momentarily report an unreasonable value? Wh…

@lagom

Could it be that the temperatures above 400 have to be interpreted as negative temperatures

Looking at your logged data, that does seem likely - the “mess up” occurs where you could expect a 0.0 reading from the trend.
Could be the sensor design deficient though, if it was only intended for room temperatures.

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

I would suggest still raising an issue on github for the binding as well

[hafniumzinc (T)]

Separately - are those real temperature values for your fridge? You run it very cold!!

[oliver_kuhl (Ollie)]

At least the RST manual states an ambient temp range of 0 to 55 celsius. What does the innogy app itself show?

[lagom (Jörn)]

Thanks for your explanation. I will try to validate this with another thermostat

[lagom (Jörn)]

Yes, they are real - this is the coldest point within the fridge… currently its quite empty

[lagom (Jörn)]

Currently its 407.4°C

[oliver_kuhl (Ollie)]

So its an innogy bug. OpenHAB shows the same.

[lagom (Jörn)]

I by-passed the issue by using a proxy item with the following rule and it seems to work fine:

rule "Appliances - fridge"
when
	Item ClimateFridgeTemperature changed
then
	if(ClimateFridgeTemperature.state > 300) {
		var orgTemp = (ClimateFridgeTemperature.state as Number).doubleValue
		var newTemp = orgTemp - 409.6
		
		logInfo("[HDMX] Appliances - fridge", "Fixing temperature from "+orgTemp+" to "+newTemp+"")
		
		ClimateFridgeTemperatureReal.sendCommand(newTemp)
	}
	else 
		ClimateFridgeTemperatureReal.sendCommand(ClimateFridgeTemperature.state)
end

@hilbrand it would be good to fix this on binding level, what do you think? Maybe it can be done via optional parameter in the Thing configuration analog to RST?

Thing WRT 	Climate_Fridge	"Kühlschrank" @ "Home" 	[ id="ce...1d8e7" ]		{ Type ??? : ??? [negativeValues=true] }

[oliver_kuhl (Ollie)]

I think the innogy backend should provide correct values.

[lagom (Jörn)]

I totally agree @oliver_kuhl… But we know that this may take some time
To be honest: I would do it if I knew what to do but as I am the only user that has this issue (and found a way to bypass it) we can leave the binding as it is.