Set control setpoint
The Set control setpoint action sets the central heating control setpoint override on your OpenTherm Gateway. Normally, the thermostat calculates and controls the central heating setpoint on the boiler. Setting this to any value other than 0 enables the override and lets the OpenTherm Gateway control this setting. While the override is active, the gateway also requests your boiler to activate the central heating circuit. For your boiler’s supported setpoint range, see the slave_ch_max_setp and slave_ch_min_setp sensors. Because of the potential consequences of leaving this setting enabled for a long time, the override is disabled when Home Assistant shuts down or restarts.
You only need this if you are writing your own software thermostat.
Improper use of this action may continuously keep your central heating system active, resulting in an overheated house and a significant increase in gas or electricity consumption.
Read this information from the designer of the OpenTherm Gateway before you consider writing your own software thermostat.
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 the control setpoint 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 OpenTherm Gateway: Set control setpoint.
- Enter the Gateway ID and the Temperature.
- Select Save.
This action does not support targets. In the UI, you are not prompted to choose an area, device, entity, or label.
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 opentherm_gw.set_control_setpoint. A basic example looks like this:
action: opentherm_gw.set_control_setpoint
data:
gateway_id: opentherm_gateway
temperature: 60
This sets the central heating control setpoint to 60 degrees on the selected gateway.
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.
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 central heating override: Sets the central heating override option on the gateway.
-
Set max modulation: Overrides the maximum relative modulation level on the gateway.