Set climate temperature offset
The Set climate temperature offset action calibrates the temperature reading of a Tado climate device. If the device reports a temperature that is consistently higher or lower than the real room temperature, you can apply an offset to correct it.
This is useful when a radiator valve sits close to the radiator and reads warmer than the rest of the room. An automation can keep the offset in sync with a separate, better-placed temperature sensor.
Using this action from the user interface
If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.
To set a temperature offset from an automation or a script:
- Go to Settings > Automations & scenes.
- Open an existing automation or script, or select Create automation > Create new automation.
- If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
- In the Then do section, select Add action.
- From the search box, search for and select Tado: Set climate temperature offset.
- Under Targets, choose the climate entities to adjust.
- Enter the Offset.
- Select Save.
Targets of the action
This action requires a target. The target is the object of the action. You can point the action at a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label, and Home Assistant will run the action on every matching climate entity behind that target.
-
Entity: one specific climate entity, such as
climate.living_room. - Device: every climate entity that belongs to a device.
- Area: every climate entity in a room or area.
- Floor: every climate entity on a floor.
- Label: every climate entity that shares a label.
You can also select different target types in one action. For example, you can add a specific entity and an area as targets in the same action to run the action on both of them at once.
Options in the UI
Using this action in YAML
If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.
In YAML, refer to this action as tado.set_climate_temperature_offset. A basic example looks like this:
action: tado.set_climate_temperature_offset
target:
entity_id: climate.tado
data:
offset: -1.5
Options in YAML
Try it yourself
Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.
More examples
Real scenarios where this action shows up in automations and scripts. Copy any example and adapt it to your setup.
You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the automation editor in Home Assistant, and press Ctrl+V (or Cmd+V on Mac). Home Assistant automatically converts the pasted YAML into the visual editor format, whether it’s a full automation, a single trigger, a condition, or an action.
Automation: keep the offset in sync with another sensor
When a better-placed room sensor and the Tado reading drift apart, recalculate the offset so the Tado device reflects the real room temperature.
- Trigger: The room sensor or the Tado temperature changes
- Condition: The two readings differ by more than 0.5°
- Action: Tado: Set climate temperature offset
- Target: Tado
- Offset: Calculated from the difference between the two sensors
YAML example for syncing the offset
alias: "Sync Tado offset with room sensor"
triggers:
- trigger: state
entity_id:
- sensor.temp_sensor_room
- sensor.tado_temperature
conditions:
- condition: template
value_template: >
{% set tado_temp = states('sensor.tado_temperature') | float(20) %}
{% set room_temp = states('sensor.temp_sensor_room') | float(20) %}
{{ (tado_temp - room_temp) | abs > 0.5 }}
actions:
- action: tado.set_climate_temperature_offset
target:
entity_id: climate.tado
data:
offset: >
{% set tado_temp = states('sensor.tado_temperature') | float(20) %}
{% set room_temp = states('sensor.temp_sensor_room') | float(20) %}
{% set current_offset = state_attr('climate.tado', 'offset_celsius') %}
{{ (-(tado_temp - room_temp) + current_offset) | round(1) }}
Still stuck?
The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.
AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.
Related actions
These actions work well alongside this one:
-
Set climate timer: Turns on a Tado climate entity for a set time.
-
Set water heater timer: Turns on a Tado water heater for a set time.
-
Add meter reading: Adds a meter reading to Tado Energy IQ.