diff --git a/source/_integrations/input_boolean.markdown b/source/_integrations/input_boolean.markdown index 15080625f28..05797132150 100644 --- a/source/_integrations/input_boolean.markdown +++ b/source/_integrations/input_boolean.markdown @@ -12,7 +12,7 @@ ha_domain: input_boolean The Input Boolean helper integration allows you to define boolean values that can be controlled via the user interface and can be used within conditions of -automation. This can for example be used to disable or enable certain +an automation. This can for example be used to disable or enable certain automations by using them in their conditions. ## Configuration @@ -74,14 +74,14 @@ Home Assistant itself. ### Restore State -If you set a valid value for `initial` this integration will start with state +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. ## Automation Examples Here's an example of an automation using the above `input_boolean`. This action -will only occur if the switch is on. +will only occur if the `input_boolean` is on. ```yaml automation: diff --git a/source/_integrations/input_datetime.markdown b/source/_integrations/input_datetime.markdown index 9accf3fb106..dccd62c13cd 100644 --- a/source/_integrations/input_datetime.markdown +++ b/source/_integrations/input_datetime.markdown @@ -85,7 +85,7 @@ automations and templates. ### 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 diff --git a/source/_integrations/input_select.markdown b/source/_integrations/input_select.markdown index b8530200828..c7999bc9656 100644 --- a/source/_integrations/input_select.markdown +++ b/source/_integrations/input_select.markdown @@ -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 diff --git a/source/_integrations/roku.markdown b/source/_integrations/roku.markdown index 5840e24d75e..789a297c2aa 100644 --- a/source/_integrations/roku.markdown +++ b/source/_integrations/roku.markdown @@ -128,10 +128,6 @@ action: media_content_type: channel ``` -## Remote - -The `remote` platform allows you to send keypress commands to your device. Remote entities are automatically registered during the integration setup. - ## Services ### Service `roku.search`