You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/_components/group.markdown
+1-1
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ Configuration variables:
58
58
59
59
- **view** (*Optional*): If yes then the entry will be shown as a view (tab) at the top.
60
60
- **name** (*Optional*): Name of the group.
61
-
- **icon** (*Optional*): If the group is a view, this icon will show at the top in the frontend instead of the name. If it's not a view, then the icon shows when this group is used in another group.
61
+
- **icon** (*Optional*): If the group is a view, this icon will show at the top in the frontend instead of the name. If the group is a view and both name and icon have been specified, the icon will appear at the top of the fronted and the name will be displayed as the mouse-over text. If it's not a view, then the icon shows when this group is used in another group.
62
62
- **control** (*Optional*): Set value to `hidden`. If hidden then the group switch will be hidden.
63
63
- **entities** (*Required*): array or comma delimited string, list of entities to group.
Copy file name to clipboardExpand all lines: source/_components/input_boolean.markdown
+5-3
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,8 @@ ha_category: Automation
13
13
14
14
The `input_boolean` component allows the user to define boolean values that can be controlled via the frontend and can be used within conditions of automation. This can for example be used to disable or enable certain automations.
15
15
16
+
To enable input booleans in your installation, add the following lines to your `configuration.yaml`:
17
+
16
18
```yaml
17
19
# Example configuration.yaml entry
18
20
input_boolean:
@@ -25,9 +27,9 @@ input_boolean:
25
27
Configuration variables:
26
28
27
29
- **[alias]** (*Required*): Alias for the input.
28
-
- **name** (*Optional*): Friendly name of the input.
29
-
- **initial** (*Optional*): Initial value when Home Assistant starts.
30
-
- **icon** (*Optional*): Icon for entry.
30
+
- **name** (*Optional*): Friendly name of the input.
31
+
- **initial** (*Optional*): Initial value when Home Assistant starts. Defaults to `False`.
32
+
- **icon** (*Optional*): Icon for entry.
31
33
32
34
Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
Copy file name to clipboardExpand all lines: source/_components/input_select.markdown
+22-6
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ha_release: 0.13
14
14
15
15
The `input_select` component 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.
16
16
17
-
To enable this platform, add the following lines to your `configuration.yaml`:
17
+
To enable this platform in your installation, add the following lines to your `configuration.yaml`:
18
18
19
19
```yaml
20
20
# Example configuration.yaml entry
@@ -35,11 +35,11 @@ input_select:
35
35
36
36
Configuration variables:
37
37
38
-
- **[alias]** (*Required*): Alias for the input.
39
-
- **name** (*Optional*): Friendly name of the input.
40
-
- **options** array: List of options to choose from
41
-
- **initial** (*Optional*): Initial value when Home Assistant starts.
42
-
- **icon** (*Optional*): Icon for entry.
38
+
- **[alias]** array (*Required*): Alias for the input. Multiple entries are allowed..
39
+
- **name** (*Optional*): Friendly name of the input.
40
+
- **options** array (*Required*): List of options to choose from.
41
+
- **initial** (*Optional*): Initial value when Home Assistant starts.
42
+
- **icon** (*Optional*): Icon for entry.
43
43
44
44
Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
45
45
@@ -71,6 +71,22 @@ automation:
71
71
option: Paulus
72
72
```
73
73
74
+
To dynamically set the `input_select` options you can call `input_select.set_options`. The following example can be used in an automation rule:
75
+
76
+
```yaml
77
+
# Example configuration.yaml entry
78
+
automation:
79
+
- alias: example automation
80
+
trigger:
81
+
platform: event
82
+
event_type: MY_CUSTOM_EVENT
83
+
action:
84
+
- service: input_select.set_options
85
+
data:
86
+
entity_id: input_select.who_cooks
87
+
options: ["Item A", "Item B", "Item C"]
88
+
```
89
+
74
90
### {% linkable_title Scenes %}
75
91
76
92
To specify a target option in a [Scene](/components/scene/) you have to specify the target as `option` attribute:
Copy file name to clipboardExpand all lines: source/_components/input_slider.markdown
+8-6
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ ha_release: 0.16
14
14
15
15
The `input_slider` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the slider generate state events. These state events can be utilized as `automation` triggers as well.
16
16
17
+
To enable this input sliders in your installation, add the following lines to your `configuration.yaml`:
18
+
17
19
```yaml
18
20
# Example configuration.yaml entry
19
21
input_slider:
@@ -27,12 +29,12 @@ input_slider:
27
29
28
30
Configuration variables:
29
31
30
-
- **[alias]** (*Required*): Alias for the slider input.
31
-
- **min** (*Required*): Minimum value for the slider.
32
-
- **max** (*Required*): Maximum value for the slider.
33
-
- **name** (*Optional*): Friendly name of the slider input.
34
-
- **initial** (*Optional*): Initial value when Home Assistant starts.
35
-
- **step** (*Optional*): Step value for the slider.
32
+
- **[alias]** (*Required*): Alias for the slider input. Multiple entries are allowed.
33
+
- **min** (*Required*): Minimum value for the slider.
34
+
- **max** (*Required*): Maximum value for the slider.
35
+
- **name** (*Optional*): Friendly name of the slider input.
36
+
- **initial** (*Optional*): Initial value when Home Assistant starts. Defaults to 0.
37
+
- **step** (*Optional*): Step value for the slider. Defaults to 1.
Copy file name to clipboardExpand all lines: source/_components/isy994.markdown
+1-1
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ A device is created by creating a directory, with the name for the device, under
88
88
**HA.lock* will create a lock
89
89
**HA.switch* will create a switch
90
90
91
-
A program, named *status*, is required under the program device directory. A program, named *actions*, is required for all program devices except for binary_sensor. Any other programs in these device directories will be ignored.
91
+
A program, named *status*, is required under the program device directory. A program, named *actions*, is required for all program devices except for binary_sensor. Any other programs in these device directories will be ignored. The *status* program requires that you create a variable with the name of your choice. This variable will store the actual status of the new device and will be updated by the *action* program.
0 commit comments