From fc22f519f4cc65d093ff122872c520de2c73316e Mon Sep 17 00:00:00 2001 From: Rolf K Date: Wed, 16 Oct 2019 22:02:18 +0200 Subject: [PATCH] Update input_select.markdown (#10795) Adds documentation for improved scene support for input_select. --- source/_integrations/input_select.markdown | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/source/_integrations/input_select.markdown b/source/_integrations/input_select.markdown index cd28d03e547..c380d03e647 100644 --- a/source/_integrations/input_select.markdown +++ b/source/_integrations/input_select.markdown @@ -77,17 +77,32 @@ This integrations provide three services to modify the state of the `input_selec ### Scenes -To specify a target option in a [Scene](/integrations/scene/) you have to specify the target as `option` attribute: +Specifying a target option in a [Scene](/integrations/scene/) is simple: ```yaml # Example configuration.yaml entry scene: - name: Example1 entities: - input_select.who_cooks: - option: Paulus + input_select.who_cooks: Paulus ``` +The list of options can also be set in a [Scene](/integrations/scene). In that case, you also need to specify what the new state will be. + +```yaml +# Example configuration.yaml entry +scene: + - name: Example2 + entities: + input_select.who_cooks: + options: + - Alice + - Bob + - Paulus + state: Bob +``` + + ## Automation Examples The following example shows the usage of the `input_select.select_option` service in an automation: