Hallo
I have a problem with the jump in setpoint temperature (from 18.0 to 21.5). Note that the cueing value before this temp change is high, so my guess is that the controller was holding the setpoint at 21.0, just for some reason it didn't show up in the HS app.
The temperature controller that supports this is MDT SCN-RT6REG.01. The temperature is set by a bidirectional 2 byte "setpoint value offset" object, in HS this is type 16-bit EIS5 with a range of -5 to 5 and a step of 0.5, HS queries it on startup. The setpoint temperature status is a simple 2-byte "actual setpoint" object. In QuadConfig I use the option "setpoint value displacement specification".
I will add that the temp of 18.0 is the value for standby (assuming 21.0 in comfort)
Have you had this problem and where could the error be ?
Video link: https://1drv.ms/u/s!Ah9askw8qlBnqDge...j7HHv?e=gw95aj
Best regards
zybi
I have a problem with the jump in setpoint temperature (from 18.0 to 21.5). Note that the cueing value before this temp change is high, so my guess is that the controller was holding the setpoint at 21.0, just for some reason it didn't show up in the HS app.
The temperature controller that supports this is MDT SCN-RT6REG.01. The temperature is set by a bidirectional 2 byte "setpoint value offset" object, in HS this is type 16-bit EIS5 with a range of -5 to 5 and a step of 0.5, HS queries it on startup. The setpoint temperature status is a simple 2-byte "actual setpoint" object. In QuadConfig I use the option "setpoint value displacement specification".
I will add that the temp of 18.0 is the value for standby (assuming 21.0 in comfort)
Have you had this problem and where could the error be ?
Video link: https://1drv.ms/u/s!Ah9askw8qlBnqDge...j7HHv?e=gw95aj
Best regards
zybi