Set climate timer

The Set climate timer action switches a Tado climate device, such as a radiator valve, to a target temperature for a set time. This is the equivalent of a manual boost: the device heats to the temperature you choose and then returns to its schedule.

You can either set a fixed time period or choose an overlay that decides when the change ends, such as keeping it until the next scheduled block.

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 climate timer from an automation or a script:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create automation > Create new automation.
  3. 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.
  4. In the Then do section, select Add action.
  5. From the search box, search for and select Tado: Set climate timer.
  6. Under Targets, choose the climate entities to control.
  7. Enter the Temperature, and optionally a Time period or an Overlay.
  8. 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

Temperature (Required)

The target temperature to set the climate entity to.

Time period (Optional)

The length of time the change should last, for example 01:30:00. Choose this or an overlay.

Overlay (Optional)

Choose this or a time period. Decides when the change ends: NEXT_TIME_BLOCK keeps it until the next scheduled block, MANUAL keeps it until you remove it, and TADO_DEFAULT uses the setting from the Tado app.

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_timer. A basic example looks like this:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: tado.set_climate_timer
target:
  entity_id: climate.heating
data:
  temperature: 20.5
  time_period: "01:30:00"

Options in YAML

temperature float Required

The target temperature to set the climate entity to.

time_period string

The length of time the change should last, for example 01:30:00. Choose this or an overlay.

requested_overlay string

Choose this or a time period. Decides when the change ends: NEXT_TIME_BLOCK keeps it until the next scheduled block, MANUAL keeps it until you remove it, and TADO_DEFAULT uses the setting from the Tado app.

Good to know

  • Set either a time period or an overlay, not both.

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.

Tip

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.

Script: boost heating and hot water together

Boost the radiator and the hot water at the same time with a single script. Handy as a dashboard button on a cold morning.

  • Action: Tado: Set climate timer
  • Target: Heating
  • Temperature: 25
  • Time period: 01:30:00
  • Action: Tado: Set water heater timer
  • Target: Hot water
  • Time period: 01:30:00
YAML example for boosting heating and hot water
ScriptScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more]
alias: "Boost heating and hot water"
sequence:
  - action: tado.set_climate_timer
    target:
      entity_id: climate.heating
    data:
      temperature: 25
      time_period: "01:30:00"
  - action: tado.set_water_heater_timer
    target:
      entity_id: water_heater.hot_water
    data:
      time_period: "01:30:00"

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.

Tip

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: