Get the mode capabilities of a Sensibo device

Use this action to find out which settings a Sensibo climate device supports for a specific HVAC mode. The Set full state and Enable Climate React actions both expect their values to match what the Sensibo API allows exactly, and those values are case-sensitive. Run this action first to get the list of valid options, then copy the ones you need into the other actions, your automations, or your scripts.

This action returns its result as response data and does not change anything on the device.

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 get the device capabilities 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. Select what you want to control. Under By target (see Targets), select the Sensibo climate device.
  6. From the actions shown for that target, select Sensibo: Get device mode capabilities.
  7. Select the HVAC mode you want the capabilities for.
  8. Select Save.

Options in the UI

HVAC mode

The HVAC mode to get the capabilities for. Choose from cool, heat, dry, fan, or auto.

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 sensibo.get_device_capabilities. 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: sensibo.get_device_capabilities
target:
  entity_id: climate.living_room
data:
  hvac_mode: cool
response_variable: capabilities

This stores the supported settings for cool mode in a variable named capabilities.

Options in YAML

hvac_mode string Required

The HVAC mode to get the capabilities for. Choose from cool, heat, dry, fan, or auto.

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.

Response data

The action returns a mapping of the settings the device supports in the chosen HVAC mode, with the allowed values for each. Depending on the device, this can include settings such as fan levels, swing modes, horizontal swing modes, target temperatures, and light options. The values are case-sensitive, so copy them exactly as returned.

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.

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: