Sensibo mode not displayed correctly

[Freddy Kilowatt]

It always return the measurements:temperature in centigrade so the conversion for that in the code to 'ST' is proper.

But for setting the acState:targetTemperature it needs to be centigrade or Fahrenheit based on temperatureUnit.

There is also acState:nativeTargetTemperature which I believe always takes centigrade.  Incrementing or decrementing that probably just works.

I didn't know if you could dynamically set the editor values.  If so setting the values based on what sensibo reports would be nice.  But yes, different AC units may have different values.  I suspect it would just be the extent of the range of centigrade values.  My units take 16c-30c for cool, dry and auto and add 10c (50f) to that range only for heat (they call that Min.Heat).

Another interesting note is Sensibo's Fahrenheit values are different (but more accurate) than my actual remote control.  Sensibo uses [61, 63, 64, 66, 68, 70, 72, 73, 75, 77, 79, 81, 82, 84, 86].  My remote control uses [60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88] which is f = c * 2 + 28

Sensibo API output - Fujitsu mini-split Heat Pump.txt

Edited yesterday at 03:22 AM by Freddy Kilowatt

[bpwwer]

2 hours ago, Freddy Kilowatt said:

Another interesting note is Sensibo's Fahrenheit values are different (but more accurate) than my actual remote control.  Sensibo uses [61, 63, 64, 66, 68, 70, 72, 73, 75, 77, 79, 81, 82, 84, 86].  My remote control uses [60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88] which is f = c * 2 + 28

That is interesting. I bet whatever micro-controller that is in the remote can't do floating point so they had to approximate the conversion formula.