Is anyone aware of any downsides to setting the interval really short (~2mins) ? I have a few rooms where the sensors drift very quickly at certain times of day.
Only real and painful downside is that each time you trigger an offset update, the valve closes and opens again and this kills battery lifetime.
I have valves in my house where I need to replace batteries each week approximately due to this. I cannot set a too wide timeframe otherwise I would have too much delta between real and valve temperature so…as long as Tado keeps this behavour, I guess we won’t be able to update our offset too often.
UPDATE: 4.0
Bug fixes:
- Offset calibration interval from min:1 to min:10 minutes
New features:
None
Don’t forget to re-download this blueprint to update your local file!
I just made the observation that the blueprint is not working if there are more than one tado assigned to a room. Is there a workaround to handle that?
Had a (old) situation where the wall mount thermostat and a radiator valve where in one room, also in the app. But the thermostat is actually lying next to the heating boiler, only to control it (new situation).
So I created an extra room in the app for the thermostat. Now every room has only one tado device and it is working again.
Sorry, of course not, or at least it doesn’t work in the same automation.
You should do two automations, one for each single TRV.
Otherwise, I have a zone controller in my tado app that basically acts as a single-point of control for one room that has more than one TRV.
Hi all, I’ve just tried using this blueprint (thank you @dllfpp), but I’ve run into an issue. Looking at a trace I can see that it has correctly determines a 4.35 degree celsius temperature difference between external sensor and Tado TRV, but then it calculates an offset of -12.4 degree celsius (which looks wrong to me), and I think this is outside the range Tado permits anyway, so the then condition fails to set the offset. I’ve included the relevant parts of the trace below. If anyone has any ideas, I’d be most grateful.
Conditionally execute an action
Executed: 17 September 2025 at 08:28:00
Result:
choice: then
if
Executed: 17 September 2025 at 08:28:00
Result:
result: true
if/condition/0
[If Temperature Sensor Office Temperature and Office are above 0.5]
Executed: 17 September 2025 at 08:28:00
Result:
result: true
if/condition/0/entity_id/0
[Unknown condition]
Executed: 17 September 2025 at 08:28:00
Result:
result: true state: 4.350000000000001
if/condition/0/entity_id/1
[Unknown condition]
Executed: 17 September 2025 at 08:28:00
Result:
result: true state: 4.350000000000001
Perform action ‘Tado: Set climate temperature offset’ on Office
Executed: 17 September 2025 at 08:28:00
Result:
params:
domain: tado
service: set_climate_temperature_offset
service_data:
offset: -12.4
entity_id:
- climate.office
target:
entity_id:
- climate.office
running_script: false
Thank you @dllfpp for this!
I’m having some issues setting everything up.
I’m using Sonoff SNZB-02P sensor to change Tado X offset.
Looks like the offset is not changing correctly, my external sensor measures 17.5 °C while my Tado is now showing 16.6 °C. 10 minutes ago the sensor was also 17.5 while Tado was 18.
Anyone knows how to fix this? Thanks!
Sorry for my very late reply. Did you see previous comments from other users?
I don’t own a TadoX environment, therefore it’s impossible to me to help here. Check for previously mentioned solutions or try to get in contact with other users directly, maybe you can share common situations.
Thanks!
UPDATE: 5.0
Bug fixes:
None
New features:
Added open window control. When your window/door has being left open for more than 2 minutes, Tado goes off until you close it.
Don’t forget to re-import this blueprint to update your local HA instance!
I tested this new version with the window control and it will turn off my heater when opening the window, but not turn it into auto again once i close the window.
As for the window entity i use tado’s built in window open entity as i do not have separat sensors on my windows.
Uhm…can’t help. I disabled the built-in window open entity from Tado app and disabled the intelligent automation from their environment because it wasn’t that much reliable to me.
The whole intent of this blueprint is to get rid of internal sensors that might interfere with the valve itself and use external sensors for window and ambient temperature.