This object is in archive! 
Climat "Until next period" doesn"t respect the Next period when changing manually temperature via HORSTMANN HRT4
Known
Everything works fine with the program.
The program starts to heat at 9 am (SET_TEMPERATURE=22°)
Before 9am, SET_TEMPERATURE is set to 18.5°
When I manually change the temperature with the HORSTMANN HRT4 at 7am to 22°, it's working. BUT, after a while, the SET_TEMPERATURE is back to 18.5 (see events screen capture)
So, why the zipabox changes the temperature BEFORE "Next period" ?
The "Until Next period" doesn't work with the web widget too. I always have to use "Hold for"!
Thanks
Files:
events.PNG
No connection
Real-time notifications may not work
Zipato firmware up o date: 0.9.999.8k
Horstmann SRT321 + Boiler Actuator
SRT321 Wakeup intervall: 10 mn
Program in climate: 00h00-17h00: t°= 16.3
17h00-19h00: t°= 17.2
19h00-24h00: t°= 18.8
I add the following problems:
1- when program is running, it switch to "until next period" at SRT321's wakeup time.And setpoint_heating t° increase to the next entire value.
For exp: 18.6°program => 19.0°when switching to next period.But t° in SRT321 chart shown 19.3°; then 19.5°.
2- when I change setpoint_heating t° on SRT321, setpoint_heating t° changes in "climate".
when I change setpoint_heating t° in "climate", setpoint_heating t° doesn't change on SRT 321.
Zipato firmware up o date: 0.9.999.8k
Horstmann SRT321 + Boiler Actuator
SRT321 Wakeup intervall: 10 mn
Program in climate: 00h00-17h00: t°= 16.3
17h00-19h00: t°= 17.2
19h00-24h00: t°= 18.8
I add the following problems:
1- when program is running, it switch to "until next period" at SRT321's wakeup time.And setpoint_heating t° increase to the next entire value.
For exp: 18.6°program => 19.0°when switching to next period.But t° in SRT321 chart shown 19.3°; then 19.5°.
2- when I change setpoint_heating t° on SRT321, setpoint_heating t° changes in "climate".
when I change setpoint_heating t° in "climate", setpoint_heating t° doesn't change on SRT 321.
All these problmes remain under firmware 1.0.11.
All these problmes remain under firmware 1.0.11.
Replies have been locked on this page!