Merge pull request #313 from lindsaymarkward/master
Clarified and added detail for devices, customizations and groups
This commit is contained in:
commit
d83ae837bf
3 changed files with 46 additions and 32 deletions
|
@ -15,10 +15,11 @@ Groups allow the user to combine multiple entities into one. A group can be prom
|
|||
|
||||
Check the **Set State** page from the **Developer Tools** and browse the **Current entities:** listing for all available entities.
|
||||
|
||||
By default, every group appears in the HOME tab. If you name a group `default_view` it will REPLACE the contents of the HOME tab so you can customize it as you wish.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
group:
|
||||
# If you name an entry default_view it will REPLACE the contents of the "Home" tab
|
||||
default_view:
|
||||
view: yes
|
||||
entities:
|
||||
|
@ -42,24 +43,32 @@ group:
|
|||
|
||||
Configuration variables:
|
||||
|
||||
- **view** (*Optional*): If yes then the entry will be shown as a view (tab).
|
||||
- **name** (*Optional*): Name of the group.
|
||||
- **icon** (*Optional*): An optional icon to show in the Frontend.
|
||||
- **view** (*Optional*): If yes then the entry will be shown as a view.
|
||||
- **entities** array or comma delimited string (*Required*): List of entites to group.
|
||||
- **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.
|
||||
- **entities** (*Required*): array or comma delimited string, list of entities to group.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2016-01-release-12/views.png'>
|
||||
Example of groups shown as views in the frontend.
|
||||
</p>
|
||||
|
||||
If all entities are switches or lights they can be controlled as one with a switch at the top of the card. Grouped states should share the same type of states (ON/OFF or HOME/NOT_HOME).
|
||||
If all entities in a group are switches or lights then Home Assistant adds a switch at the top of the card that turns them all on/off at once.
|
||||
|
||||
You can create views (tabs) that contain other groups.
|
||||
Notice in the example below that in order to refer to the group "Living Room", you use `group.living_room` (lowercase and spaces replaced with underscores).
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
group:
|
||||
living_room:
|
||||
- light.bowl
|
||||
- light.ceiling
|
||||
- light.tv_back_light
|
||||
children: device_tracker.child_1, device_tracker.child_2
|
||||
```
|
||||
# Example configuration.yaml entry that shows two groups, referred to in a view group (tab)
|
||||
Living Room:
|
||||
entities:
|
||||
- light.light_family_1
|
||||
- binary_sensor.motion_living
|
||||
Bedroom: light.light_bedroom, switch.sleeping
|
||||
Rooms:
|
||||
view: yes
|
||||
name: Rooms
|
||||
entities:
|
||||
- group.living_room
|
||||
- group.bedroom
|
||||
```
|
|
@ -72,4 +72,4 @@ Configuration variables:
|
|||
- **hour** (*Optional*): Specify the hour(s) of the day to schedule the speedtest. Use a list for multiple entries. Default is None.
|
||||
- **day** (*Optional*): Specify the day(s) of the month to schedule the speedtest. Use a list for multiple entries. Default is None.
|
||||
|
||||
This component uses [speetest-cli](https://github.com/sivel/speedtest-cli) to gather network performance data from Speedtest.net. Please be aware of the potential [inconsistencies](https://github.com/sivel/speedtest-cli#inconsistency) that this component may display.
|
||||
This component uses [speedtest-cli](https://github.com/sivel/speedtest-cli) to gather network performance data from Speedtest.net. Please be aware of the potential [inconsistencies](https://github.com/sivel/speedtest-cli#inconsistency) that this component may display.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue