Child thermostat setpoint set totally broken

[Neo Andersson 230]

When setting a setpoint on a child device of a thermostat type, the values are totally out of order.

Moving the slider for example to 19, it sets the value to 18.

Calling function 

Please login or register to see this code.

 

sets the setpoint to 19.5, and some similar inexplicable behaviours happen.

The child device was created using the example given by @m.roszak, i dont know if it is related to that particular way of creating a child, or it is a general problem.

 

 

[jgab 2,642]

I think it's for a main QA also. I believe that if you are in auto you get the average between the heating and cooling setpoints and vice versa... I don't have an thermostat myself so I'm not sure how it should work, but there are clearly some calculation going on before values are reported...

[m.roszak 763]

In general, with auto mode available its tricky (its an avarage of heating and cooling setpoints) - but I think it is not the case here.

There is a mandatory hysteresis between cooling and heating setpoints which also affects that.

Anyway, don't update the setpoint property directly because this skips a lot of things in the backend.
Use set{setpointType}ThermostatSetpoint action instead.