tado v2 behaviour
I have a tado wired (relay) stat and the v2 bridge (the soap bar style one without the homekit integration). Relay rather than digital setup.
Now its heating season, all the 'strange' things tado does are back and annoying me like before so I just wanted to see if anyone else is seeing the same behaviour or if I need some sort of reset on mine.
I understand that sometimes it will keep heating the house after the set temp is reached to avoid cycling so thats fine and there is a +/- variance of 0.xC around the set temp but the other things it does I dont understand.
For example…
The overnight set temperature is 18.5 and I have the temp scheduled for 20c at 0630 so the house is warm for 0700. At 0630, the temp is around 18.5, the 0630 temp change to 20c schedule kicks in and tado does nothing at all…
After 5 minutes of waiting for the wiggles to appear I hit the boost button to get it going. This is annoying as 'on' doesnt seem to be on.
Why does it have a think rather than start at 0630 as the commanded temp is higher than current temp? Is 1.5c not enough variance to make it call for heat?
When boost mode is activated, the boiler still runs after the boost time is up and the displayed temp is higher than the boosted temp. I would expect it to click off after the timer runs down and the boiler turn off otherwise why have a timer on the boost function?
Also, it doesnt seem to matter if the boost is 5 minutes or 30 minutes, it will still run for 30 or so minutes regardless…
The off button seemingly does nothing at all. The heating could be on and the house is getting too warm whilst tado is being 'clever' and heating it above the set temp so you hit the off button and nothing at all happens. The boiler is still on and the house is still heating up.
Despite it being in relay mode tado still acts like there is weather comp activated at it will display 1 wiggle (nothing happens), 2 wiggles (still nothing happens) then finally 3 wiggles which starts the boiler up. I suspect 1 or 2 wiggles is it thinking its sending round low flow then but as there is no temp increase it up the wiggles until reaching 3 which is on.
I have had tado for many years and each year the same irritations appear. I just wondered if this was pretty much standard or if its unique to me…
Being able to control it via the app is very handy but I do sometimes wonder if a conventional programmable stat would do a better job.
Comments
-
I'll try to address some of your remarks, to increase understanding:
1 wiggle (nothing happens), 2 wiggles (still nothing happens) then finally 3 wiggles which starts the boiler up.
We use a PWM controller for our relay. It will modulate your heating. With 1 wiggle, it is off most of the time but will come on occasionally. The wiggles, by the way, are a graphical simplification of a heat request percentage.
At 0630, the temp is around 18.5, the 0630 temp change to 20c schedule kicks in and tado does nothing at all…
After 5 minutes of waiting for the wiggles to appear I hit the boost button to get it going. This is annoying as 'on' doesnt seem to be on.
As long as the device is online, it is controlled via the cloud. This means there can be little delays. But more importantly, given the PWM I linked to above, if the heat request is low it might take a while for the relay to switch after a change in schedule. In theory this would be fine, because when the heat request is low it means the desired temperature is already close to the measured temperature.
0
