Set demand control
Use this action to limit the unit’s maximum power to a percentage of its nominal power, for example, to reduce power consumption during peak electricity price periods. Not all Daikin units support demand control. On units that don’t, the action returns an error. It is only available on units that support demand control.
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 demand control 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.
- Under By type, select the Set demand control actionAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more] under the Daikin AC integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more].
- Select the Device, set Enable, and configure Maximum power and Mode as needed.
- Select Save.
Options in the UI
The Daikin deviceA device is a model representing a physical or logical unit that contains entities. to limit
Maximum power as a percentage of the unit’s nominal power, from 40 to 100. Defaults to 100. Only used when Enable is on and Mode is Manual.
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. For how an automation or a script is built in YAML, refer to Automations in YAML and Scripts.
In YAML, refer to this action as daikin.set_demand_control. A basic example looks like this:
action: daikin.set_demand_control
data:
device_id: 17159993ce512ff1794b6c1abc6f3df3
en_demand: true
max_pow: 40
This sets the deviceA device is a model representing a physical or logical unit that contains entities. 17159993ce512ff1794b6c1abc6f3df3 demand control to 40% of the nominal power. The easiest way to get the device ID is to create the action in the UI first. Then, on the action, select Menu
Options in YAML
The Daikin deviceA device is a model representing a physical or logical unit that contains entities. to limit
Maximum power as a percentage of the unit’s nominal power, from 40 to 100. Only used when en_demand is true and mode is manual.
Good to know
- This action works with Daikin climate devices.
- If multiple indoor units are connected to an outdoor unit, the outdoor unit automatically selects the least restrictive demand setting. For example, if one indoor unit is set to an 80% capacity limit and the other to a 50% capacity limit, the outdoor unit will operate at a maximum capacity of 80%.
Try it yourself
Ready to test this? Open Settings > 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. In the visual editor, select the UI options listed in the example or paste the YAML code.
You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the visual 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: Limit the maximum power of the unit during high-rate electricity periods
This example assumes that binary_sensor.electricity_high_rate already exists and turns on during high-rate periods. Replace it with the entity provided by your electricity-rate integration or one you created separately.
-
Trigger: State
-
Entity: High-rate signal (
binary_sensor.electricity_high_rate) - To: On or Off
-
Entity: High-rate signal (
-
Action: If-then
- If: High-rate signal is on
-
Then: Set demand control
- Device: Daikin unit
- Enable: On
- Maximum power: 40%
-
Else: Set demand control
- Device: Daikin unit
- Enable: Off
Show example YAML
- alias: "Limit maximum AC power during high-rate periods"
triggers:
- trigger: state
entity_id: binary_sensor.electricity_high_rate
to:
- "on"
- "off"
actions:
- if:
- condition: state
entity_id: binary_sensor.electricity_high_rate
state: "on"
then:
- action: daikin.set_demand_control
data:
device_id: "17159993ce512ff1794b6c1abc6f3df3"
en_demand: true
max_pow: 40
else:
- action: daikin.set_demand_control
data:
device_id: "17159993ce512ff1794b6c1abc6f3df3"
en_demand: false
Automation: Limit the maximum power of the unit during the night
-
Trigger: State
-
Entity: Sun (
sun.sun) - To: Below horizon or Above horizon
-
Entity: Sun (
-
Action: If-then
- If: Sun is below the horizon
-
Then: Set demand control
- Device: Daikin unit
- Enable: On
- Maximum power: 60%
-
Else: Set demand control
- Device: Daikin unit
- Enable: Off
Show example YAML
- alias: "Limit the maximum power of the unit during the night"
triggers:
- trigger: state
entity_id: sun.sun
to:
- "below_horizon"
- "above_horizon"
actions:
- if:
- condition: state
entity_id: sun.sun
state: "below_horizon"
then:
- action: daikin.set_demand_control
data:
device_id: "17159993ce512ff1794b6c1abc6f3df3"
en_demand: true
max_pow: 60
else:
- action: daikin.set_demand_control
data:
device_id: "17159993ce512ff1794b6c1abc6f3df3"
en_demand: false
Still stuck?
To test the action on its own, run it in the automation editor with Run action, and check the message that it shows. To see what the action did when the automation ran, open the trace of that run. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.
If that doesn’t help, 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.