It's in the 'fake' roadmap since more than two years....never implemented...they gave priority to vocal assistant support implementation...
Agreed; a child lock is a very important safety feature too; not just for cost savings and comfort. It is all too easy for a child to turn the radiator valve to maximum, and potentially hurt themselves on a very hot radiator.
I would have thought this should be a top priority improvement for ALL users; V3 and V3+. Lately there have not been any changes that I have noticed to the V3 app.....
In October my second child will born...how many child I must do before Tado implement child lock?
It is ridiculous only because we are speaking about a very easy and stupid function that could require no more than 2 weeks of developing...but it seems that for Tado's deveolopers it is too difficult...
I chose tado knowing this was in their roadmap. Almost 3 years ago!
A TRV child lock is a long requested feature, which was on Tado's roadmap, so hopefully they are still working on it. You may wish to add your vote to this existing request: https://community.tado.com/en-gb/discussion/comment/2336
Another person here also been requesting for a long time. The only sort of solution I have found was to make manual adjustments only happen for 1 minute so when my children play with the TRV they only manually adjust it for 1 minute,
As said it only sort of fixes the issue, A child lock would be far superior, ideally with a schedule built in so I can set the living room TRV's with child locks from say 7am until 7pm when there's a chance of them playing with the TRV's but after 7pm this would allow myself and my wife the chance to manually turn the heating up via the TRV when required
+1 to this feature request.
Child lock on radiator valves would be much appreciated.
It's been long requested and promised - we need a child lock on each radiator, plus a 'geo-fence only' app account, so the heating can be smart even for household members who we don't want to be able to adjust the settings. Without that it's open to abuse and children can cost you more than any saving you might get to both your bills and the environment.
There is an easy work around for the child lock:
Id rather wish Tado's one and only part time developer, if or when he returns from his 24 month career break , spent his time creating a home/away button (or removing the lines in the code that hide the existing home/away button whenever geolocation doesnt detect a change).
Ahahahah Vertigo, I implemented that workaround years ago :D
Tado engineers (if there's someone in Tado...) would never be able to think to it.
I’m very new here, but think this would be a good idea.