Jonathan. That's pretty much what I'm seeing from my Wiser system. Using today as an example
05:30 , room temp = 18.5C ; target 21.0C ; boiler came on with 100% demand indicated
06:10 19.8C demand dropped to 61% and boiler started to cycle on/off as driven by Wiser with brief 5 or 10 minute burns as demand % reduces
07:10 20.7C demand hit 20% at which point boiler stopped cycling
the room temperture then remained between 20.7 & 20.9C with 20% demand but no boiler activity. I assume this meets the 21.0C target. The app only allow 0.5 granularity but Wiser internally uses 0.1C increments.
09:00 schedule dropped temp to 20C , demand now 0%
10:50 19.8C demand shown as 20% for 40 minutes, boiler ran for 5 minutes (10:50 to 10:55)
11:30 20.0C demand returns to 0%
12:10 19.9C, demand goes to 20% for 40 minutes or so. again boiler ran for around 5 minutes.
This has continued over the day with the boiler running for brief periods to maintain temp.
05:30 , room temp = 18.5C ; target 21.0C ; boiler came on with 100% demand indicated
06:10 19.8C demand dropped to 61% and boiler started to cycle on/off as driven by Wiser with brief 5 or 10 minute burns as demand % reduces
07:10 20.7C demand hit 20% at which point boiler stopped cycling
the room temperture then remained between 20.7 & 20.9C with 20% demand but no boiler activity. I assume this meets the 21.0C target. The app only allow 0.5 granularity but Wiser internally uses 0.1C increments.
09:00 schedule dropped temp to 20C , demand now 0%
10:50 19.8C demand shown as 20% for 40 minutes, boiler ran for 5 minutes (10:50 to 10:55)
11:30 20.0C demand returns to 0%
12:10 19.9C, demand goes to 20% for 40 minutes or so. again boiler ran for around 5 minutes.
This has continued over the day with the boiler running for brief periods to maintain temp.
Last edited: