small edits (#19533)

This commit is contained in:
Marius 2021-09-30 16:26:18 +02:00 committed by GitHub
parent fe8cb5ed91
commit 79db5c461c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -10,7 +10,7 @@ ha_codeowners:
ha_domain: input_select
---
The `input_select` integration allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selects a new item, a state transition event is generated. This state event can be used in an `automation` trigger.
The `input_select` integration allows the user to define a list of values that can be selected via the frontend and can be used within conditions of an automation. When a user selects a new item, a state transition event is generated. This state event can be used in an `automation` trigger.
The preferred way to configure an input select is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the **Dropdown** option.
@ -69,7 +69,7 @@ Because YAML defines [booleans](https://yaml.org/type/bool.html) as equivalent,
### Restore State
If you set a valid value for `initial` this integration will start with state set to that value. Otherwise, it will restore the state it had prior to Home Assistant stopping.
If you set a valid value for `initial` this integration will start with the state set to that value. Otherwise, it will restore the state it had prior to Home Assistant stopping.
### Services
@ -146,7 +146,7 @@ automation:
option: Paulus
```
To dynamically set the `input_select` options you can call `input_select.set_options`. The following example can be used in an automation rule:
To dynamically set the `input_select` options you can call `input_select.set_options` in an automation:
```yaml
# Example configuration.yaml entry