🔥 🌡️Tado Offset adjustment (Zigbee thermometers, Start/End times, Switch for only when HEAT)

[Jesperh (Jesper Hegeman)]

Hi DLLFPP, thanks for this blueprint. I will check it out. Did you just update this blueprint? Do you use this blueprint in combination with better thermostat or the advanced heating control blueprint?

[dllfpp]

Hi!
I’ve been using this blueprint since last cold season but only now I had the idea of sharing it because I thought it was worth it.
I personally use Tado app for scheduling so that’s why I needed an external offset.

[wimpie007]

Thanks!
Got it to work!

[BertCa]

Great blueprint. Saves me a lot of templating/testing.
But there is one remark I want to make. The switch was not working in my setup (Tado). After some investigation I found out that the blueprint is checking the state to be ‘heat’. But as I use the tado app to set up the time schedules, the state of my climate entity stays on ‘auto’. So the switch in the template does never get triggered.
Therefor I changed the blueprint to check the attribute ‘hvac_action’ to be ‘heating’.

- condition: template
  value_template: '{{ enable_switch == false }}'
- condition: and
  conditions:
  - condition: template
    value_template: '{{ enable_switch == true }}'
  - condition: state
    entity_id: !input entity_to_update
    attribute: hvac_action
    state: heating

[dllfpp]

Thanks, awesome example of how the community helps and supports each other members.
I’ve updated my GitHub code (see details), you can just re-add the blueprint and overwrite it.
I suggest the same to all of those who downloaded the bp to proceed and update it again.
Thanks!

[David.buck]

This automation blueprint is exactly what I’ve been looking for / trying to create. So thank you for sharing.

I do have an issue I can’t solve though, if anyone can help.

I have set the automation for my Tado system, when ever I run the trace, I get True/True and a offset figure… but then the offset of the tado never updates and the temps in the tado app don’t match my Zigbee 2’s

I being trying to solve this for a while now, but I’m not getting anywhere. Can anyone help me please.

Thanks.

[dllfpp]

Have you ever tried to run the offset update action manually with a static value, just to see if your Tado integration works correctly? I’m not having this issue honestly.

I’ve recently updated the BP so, just in case, try and add it again so if you have an older version you get the latest code.
Let me know!

[rondol1 (Ron Dol)]

I’m running into the same problem as David.buck.
I tried the action in de developers tools as you suggested, that works fine. It looks like the BP doesn’t execute the set offset action somehow.

I copied the last part of your code on your Github en replaced it for the code in the BP I downloaded, now it is working as expected.

Code Github:
action:

• if:
  • condition: numeric_state
    entity_id:
    • !input sensor_to_monitor
    • !input entity_to_update
      value_template: “{{ (states(sensor_to_monitor)|float - state_attr(entity_to_update, ‘current_temperature’)|float)|abs }}”
      above: !input threshold
      then:
  • service: tado.set_climate_temperature_offset
    data:
    offset: “{{( state_attr(entity_to_update, ‘offset_celsius’)|float if state_attr(entity_to_update, ‘offset_celsius’) is not none else 0 ) + ((states(sensor_to_monitor)|float - state_attr(entity_to_update, ‘current_temperature’)|float) if states(sensor_to_monitor) is not none and state_attr(entity_to_update, ‘current_temperature’) is not none else 0 ) | round(1)}}”
    target:
    entity_id: !input entity_to_update

trace:
stored_traces: 96

Code BP:
action:

• if:
  • condition: numeric_state
    entity_id:
    • !input sensor_to_monitor
    • !input entity_to_update
      value_template: “{{ (states(sensor_to_monitor)|float - state_attr(entity_to_update, ‘current_temperature’)|float)|abs }}”
      above: !input threshold
      then:
  • service: tado.set_climate_temperature_offset
    data:
    offset: “{{( state_attr(entity_to_update, ‘offset_celsius’)|float if state_attr(entity_to_update, ‘offset_celsius’) is not none else 0 ) + ((states(sensor_to_monitor)|float - state_attr(entity_to_update, ‘current_temperature’)|float) if states(sensor_to_monitor) is not none and state_attr(entity_to_update, ‘current_temperature’) is not none else 0 ) | round(1)}}”
    target:
    entity_id: !input entity_to_update

trace:
stored_traces: 96

[dllfpp]

That’s crazy because it’s the very same code…

[David.buck]

Thanks both of you. I’m glad it’s not just me doing something wrong.

I would like to try this and copy the code as suggested. Where would I do this, I’m not a coder and do everything via the GUI.

Should I update the BP code or the automation code? Also would you mind telling me how.

Thanks again.

[David.buck]

I’ve actually just got it to work, I had added the radiator thermostat entity to the automation, and after some trial and error in the Dev tool area, I found I needed to add the room climate entity. All
5 rooms now work perfectly and have updated offsets. First time they’ve ever read the right temp on the Tado app.

Thanks for your help and a great Blueprint.

[TDCroPower]

Thanks for the blueprint, that’s exactly what I was looking for to avoid using Better Thermostat.
I’ll see how well the blueprint works as it is, but for now I’ve converted it to customise it myself.
What would be desirable is to be able to customise the 15min trigger in the blueprint.
I myself want it to trigger every 60 minutes.

One question:
What are the checks enable_switch == false and enable_switch == true for?

[dllfpp]

The switch makes the automation run based on the condition:

attribute:hvac_action
state: heating

If turned on, the automation will run only when the heating is active (this to save unnecessary offset calibration when radiator is off). When off, automation will run even when hvac is on off/auto, always still within time ranges defined in the blueprint.

Fot what concerns timing, I tried to let users specify but couldn’t get through it. Since it was done a long time ago, I’ll have a look soon.

[dllfpp]

UPDATE: 3.0

Bug fixes:
None

New features:
- Added the possibility to change the frequency of the offset to be calibrated for each automation (before 15 minutes was hardcoded).

Thanks @TDCroPower for the suggestion (here):

Don’t forget to re-download this blueprint to update your local file!

[rondol1 (Ron Dol)]

My bad, I copied the same code twice…
But anyway, I don’t know why my imported blueprint had a different code for action, but I doesn’t matter. I re-downloaded your newest version and it works perfect! Thanks so much!!

[mehul93 (Mehul)]

Thanks for the blueprint! I’m playing around with it now but can’t seem to get the offset to update (Presume I should be able to see the offset change within the tado app?)

Seems like everything is being fired so not sure where I’m gone wrong, any ideas?

P.s I’m on the new Tado X system.

if
Executed: 21 December 2024 at 15:26:20
Result:
result: true
if/condition/0
[If Outdoor temperature and Loft Smart Radiator Thermostat X are above 1]
Executed: 21 December 2024 at 15:26:20
Result:
result: true
if/condition/0/entity_id/0
[Unknown condition]
Executed: 21 December 2024 at 15:26:20
Result:
result: true
state: 4.210000000000001
if/condition/0/entity_id/1
[Unknown condition]
Executed: 21 December 2024 at 15:26:20
Result:
result: true
state: 4.210000000000001

[dllfpp]

@mehul93

P.s I’m on the new Tado X system.

Huh…I suppose that’s the problem here.
Most likely the system is speaking a different language than mine, but unfortunately I don’t have therefore I cannot test/fix anything on this, I’m sorry…

[dllfpp]

Take a look here Using tado° Smart Thermostat X through Matter - #122 by TDCroPower

It looks like this user has accomplished your need with this blueprint, on TadoX evironment.

[TDCroPower]

it works with the tado X devices, but you should note that it takes some time until the value is actually set in the tado system.

[jasmith (James)]

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.