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

Blueprints Exchange
, , ,
1

Blueprint: Update Entity Offset with Switch Control

Tado/Zigbee/Working Hours/ON-OFF Switch

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

immagine
immagine1052×729 25.6 KB

This blueprint allows you to dynamically update the temperature offset of a Tado climate entity (or another climate device) based on a Zigbee sensor’s readings, while providing control to enable or disable the automation based on the climate entity’s operating mode (specifically, when in HEAT mode).

Use Case:

You may want to adjust the temperature offset on your climate entity based on a more accurate or strategically placed sensor. This blueprint enables you to automate that adjustment within a specified time range and only when the heating system is on.

How It Works:

  • Sensor Monitoring: You specify a Zigbee temperature sensor whose state will be monitored.
  • Entity Update: You choose a climate entity (like Tado) whose temperature offset will be adjusted.
  • Threshold Control: You can set a maximum allowed temperature difference between the monitored sensor and the climate entity before triggering an update.
  • Time Range: You can define start and stop times for when the automation should be active.
  • Heat Mode Control: There’s an optional toggle to enable or disable this automation based on whether the climate entity is in HEAT mode. If the toggle is off, the automation will run regardless of the heating mode.

Inputs:

  • Zigbee Sensor to Monitor: The temperature sensor whose readings will determine the temperature offset.
  • Tado Entity to Update: The climate entity (Tado or similar) whose offset will be updated.
  • Threshold: The temperature difference required to trigger an update.
  • Start Time: Time when the automation starts.
  • End Time: Time when the automation ends.
  • Enable Automation Only When Heating: Boolean to control whether the automation only runs when the climate entity is in HEAT mode.

Example:

You have a Zigbee sensor in your living room and want to adjust the offset on your Tado thermostat based on the difference between the Tado’s temperature reading and the more accurate one from the Zigbee sensor. This automation allows you to apply this adjustment automatically, but only during specific times (e.g., 6 AM to 10 PM) and only when the Tado is heating.

Trigger & Condition:

The automation triggers every 15 minutes and checks the time of day and the heating mode condition (if enabled). If the difference between the monitored sensor and the Tado’s temperature exceeds the threshold, the Tado’s offset is updated.

Action:

The action recalculates and updates the offset value based on the temperature difference between the selected Zigbee sensor and the climate entity.

2

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?

3

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.

4

Thanks!
Got it to work!

1 Like
5

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
1 Like
6

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!