Option is selected
The Option is selected condition passes when a dropdown 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] is currently set to a specific option. It works with both Select entities provided by integrations and the Dropdown helper (“input_select”) you create yourself. Use it to gate automations on the current choice of a dropdown, such as only running a routine when House mode is set to “Home” or “Guest”.
When you target more than one dropdown, the Condition passes if option controls how the check combines results. You can require any targeted dropdown to be on the selected option, or demand that all of them are.
Requires the Purpose-specific triggers and conditions Labs preview feature. Enable it at Settings > System > Labs.
Using this condition from the user interface
If you prefer building automations visually, Home Assistant walks you through this condition step by step. You pick what to check, tweak a few options, and save. No YAML knowledge required.
To use Option is selected in an automation:
- Go to Settings > Automations & scenes.
- Open an existing automation, or select Create automation > Create new automation.
- In the And if section, select Add condition.
- Select what you want to check. Under By target (see Targets), pick the dropdown entity you want to check. You can also select an area, a device, or a label.
- From the conditions shown for that target, select Option is selected.
- Under Option, select one or more options to check for. Only options available on the targeted dropdown are shown.
- Under Condition passes if (see Behavior), pick Any or All to control how the check behaves when multiple dropdowns are targeted.
- Under For at least, set how long the dropdown must have been on the selected option before the condition passes. Leave it at zero to pass immediately.
- Select Save.
Options in the UI
The option or options to check for. Only the options available on the targeted dropdown are shown. The condition passes when the dropdown is set to any of the selected options.
When multiple dropdowns are targeted, controls how results combine. Pick Any to pass if at least one targeted dropdown is on the selected option, or All to pass only when every targeted dropdown is on the selected option. Default is Any.
Using this condition 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 condition as select.is_option_selected. A basic example looks like this:
condition: select.is_option_selected
target:
entity_id: select.living_room_soundbar_sound_mode
options:
option: "Movie"
This passes when the soundbar sound mode is set to “Movie”.
To check for any one of several options:
condition: select.is_option_selected
target:
entity_id: select.living_room_soundbar_sound_mode
options:
option:
- "Movie"
- "Night"
Options in YAML
The option or options to check for. Accepts a single option string or a list of option strings. The condition passes when the dropdown is set to any of the listed options.
When multiple dropdowns are targeted, controls how results combine. Accepts all or any.
Targets of the condition
This condition requires a target. The target is the object that Home Assistant will check. You can point the condition 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 evaluate every matching select entity behind that target.
-
Entity: one specific select entity, such as
select.living_room. - Device: every select entity that belongs to a device.
- Area: every select entity in a room or area.
- Floor: every select entity on a floor.
- Label: every select entity that shares a label.
You can also select different target types in one condition. For example, you can add a specific entity and an area as targets in the same condition to check both of them at once.
Behavior with multiple targets
When you target more than one entity (or select an area, floor, or label that contains several), the Condition passes if option controls how the results combine:
- Any (default): the condition passes if at least one of the targeted entities matches. For example, if you check three smoke sensors and only one of them detects smoke, the condition still passes. This is useful for questions like “is there smoke anywhere in the house?”
- All: the condition passes only when every targeted entity matches. For example, if you check the same three smoke sensors, the condition passes only once all three report cleared. This is useful for “is the entire house safe now?” checks, so your automation does not send an all-clear while one room still has a reading.
Good to know
- This condition works with both Select entities provided by integrations (domain
select) and Dropdown helpers you create yourself (domaininput_select). - The option string must match the dropdown’s option exactly, including capitalization. The UI lets you pick from the available options to avoid typos.
- A dropdown in the
unknownorunavailablestate never matches.
Try it yourself
Ready to test this? Go to Settings > Automations & scenes, open an automation, and add this condition. Trigger the automation with and without the condition met, and watch whether it continues or stops.
More examples
Real scenarios where this condition gates an automation. 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: dim the lights when the soundbar switches to Movie mode
Some media players expose their sound mode as a select entity, for example select.living_room_soundbar_sound_mode with options like Music, Movie, and Night. When someone starts a movie, dim the lights for a cinema feel.
-
Trigger: Selection changed
- Target: Living room soundbar sound mode
-
Condition: Option is selected
- Target: Living room soundbar sound mode
- Option: Movie
- Action: Turn on light
YAML example for dimming the lights in Movie mode
alias: "Dim lights for Movie mode"
triggers:
- trigger: select.selection_changed
target:
entity_id: select.living_room_soundbar_sound_mode
conditions:
- condition: select.is_option_selected
target:
entity_id: select.living_room_soundbar_sound_mode
options:
option: "Movie"
actions:
- action: light.turn_on
target:
entity_id: light.living_room
data:
brightness_pct: 20
Still stuck?
The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the condition you’re using and what you expected to happen, or share on our subreddit /r/homeassistant.
AI assistants like ChatGPT or Claude can also explain conditions or suggest the right one when you describe what you want in plain language.