jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-05-06 11:08:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Entity Component to no longer generate automatic groups (#11662)

Browse Source 
* Entity Component to no longer generate automatic groups

* Entity Component to no longer generate automatic groups
This commit is contained in:
Franck Nijhof 2020-01-07 18:00:45 +01:00 committed by Paulus Schoutsen
parent 7357868203
commit ada7cc55a4
9 changed files with 24 additions and 79 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_cookbook/automation_for_rainy_days.markdown
View File

@ -17,7 +17,7 @@ automation:
to: 'rain'
condition:
- condition: state
entity_id: group.all_devices
entity_id: all
state: 'home'
- condition: time
after: '14:00'

2
source/_cookbook/automation_sun.markdown
View File

@ -14,7 +14,7 @@ automation:
offset: "-00:45:00"
condition:
condition: state
entity_id: group.all_devices
entity_id: all
state: home
action:
service: light.turn_on

14
source/_cookbook/ifttt.manything.markdown
View File

@ -21,7 +21,7 @@ automation:
# if we leave the house during the day.
trigger:
- platform: state
entity_id: group.all_devices
entity_id: all
to: 'not_home'
condition:
- platform: state
@ -36,7 +36,7 @@ automation:
# when we get home unless it's nighttime.
trigger:
- platform: state
entity_id: group.all_devices
entity_id: all
to: 'home'
condition:
- condition: state
@ -59,9 +59,9 @@ For ManyThing support, you need to set up an `on` and `off` event.
You can use the developer tools to test your [Maker Service](https://ifttt.com/maker_webhooks) trigger. To do this, open the Home Assistant UI, open the sidebar, click on the first icon in the developer tools. This should get you to the 'Call Service' screen. Fill in the following values:
Field | Value
----- | -----
domain | `ifttt`
service | `trigger`
Service Data | `{"event": "manything_on"}`
| Field | Value |
| ------------ | --------------------------- |
| domain | `ifttt` |
| service | `trigger` |
| Service Data | `{"event": "manything_on"}` |

6
source/_docs/automation/examples.markdown
View File

@ -20,13 +20,13 @@ automation:
event: sunset
offset: '-01:00:00'
- platform: state
entity_id: group.all_devices
entity_id: all
to: 'home'
condition:
# Prefix the first line of each condition configuration
# with a '-'' to enter multiple
- condition: state
entity_id: group.all_devices
entity_id: all
state: 'home'
- condition: time
after: '16:00:00'
@ -40,7 +40,7 @@ automation:
- alias: 'Rule 2 - Away Mode'
trigger:
platform: state
entity_id: group.all_devices
entity_id: all
to: 'not_home'
action:
service: light.turn_off

6
source/_docs/ecosystem/appdaemon/api.markdown
View File

@ -1650,7 +1650,7 @@ for tracker in trackers:
### everyone_home()
A convenience function to determine if everyone is home. Use this in preference to getting the state of `group.all_devices()` as it avoids a race condition when using state change callbacks for device trackers.
A convenience function to determine if everyone is home.
#### Synopsis
@ -1669,7 +1669,7 @@ if self.everyone_home():
```
### anyone_home()
A convenience function to determine if one or more person is home. Use this in preference to getting the state of `group.all_devices()` as it avoids a race condition when using state change callbacks for device trackers.
A convenience function to determine if one or more person is home.
#### Synopsis
@ -1689,7 +1689,7 @@ if self.anyone_home():
```
### noone_home()
A convenience function to determine if no people are at home. Use this in preference to getting the state of group.all_devices() as it avoids a race condition when using state change callbacks for device trackers.
A convenience function to determine if no people are at home.
#### Synopsis

14
source/_integrations/blink.markdown
View File

@ -117,17 +117,17 @@ Force a refresh of the Blink system.
Trigger a camera to take a new still image.
| Service Data Attribute | Optional | Description |
|------------------------|----------|----------------------------------------|
| `name` | no | Name of camera to take new image with. |
| ---------------------- | -------- | -------------------------------------- |
| `name` | no | Name of camera to take new image with. |
### `blink.save_video`
Save the last recorded video of a camera to a local file. Note that in most cases, Home Assistant will need to know that the directory is writable via the `whitelist_external_dirs` in your `configuration.yaml` file (see example below).
| Service Data Attribute | Optional | Description |
|------------------------|----------|------------------------------------------|
| `name` | no | Name of camera containing video to save. |
| `filename` | no | Location of save file. |
| ---------------------- | -------- | ---------------------------------------- |
| `name` | no | Name of camera containing video to save. |
| `filename` | no | Location of save file. |
```yaml
@ -176,7 +176,7 @@ Here, this example assumes your blink module is named `My Sync Module` and that
alias: Arm Blink When Away
trigger:
platform: state
entity_id: group.all_devices
entity_id: all
to: 'not_home'
action:
service: alarm_control_panel.alarm_arm_away
@ -192,7 +192,7 @@ Similar to the previous example, this automation will disarm blink when arriving
alias: Disarm Blink When Home
trigger:
platform: state
entity_id: group.all_devices
entity_id: all
to: 'home'
action:
service: alarm_control_panel.alarm_disarm

6
source/_integrations/google_assistant.markdown
View File

@ -102,8 +102,6 @@ google_assistant:
light.living_room:
expose: false
room: LIVING_ROOM
group.all_automations:
expose: false
```
{% configuration %}
@ -196,10 +194,6 @@ Currently, the following domains are available to be used with Google Assistant,
- sensor (temperature setting for temperature sensors and humidity setting for humidity sensors)
- Alarm Control Panel (arm/disarm)
<div class='note warning'>
The domain `groups` contains groups containing all items, such as `group.all_automations`. When telling Google Assistant to shut down everything, this will lead in this example to disabling all automations.
</div>
### Secure Devices
Certain devices are considered secure, including anything in the `lock` domain, `alarm_control_panel` domain and `covers` with device types `garage` and `door`.

49
source/_integrations/group.markdown
View File

@ -60,18 +60,6 @@ control:
type: string
{% endconfiguration %}
## Default groups
Some integrations automatically create special groups containing integration entities. These groups are named like `group.all_...`, for example:
- `group.all_switches`
- `group.all_lights`
- `group.all_devices`
- `group.all_scripts`
- `group.all_automations`
You can see list of these groups in **States** <img src='/images/screenshots/developer-tool-states-icon.png' class='no-shadow' height='38' /> page of the **Developer Tools**.
## Group behavior
By default when any member of a group is `on` then the group will also be `on`. Similarly with a device tracker, when any member of the group is `home` then the group is `home`. If you set the `all` option to `true` though, this behavior is inverted and all members of the group have to be `on` for the group to turn on as well.
@ -148,40 +136,3 @@ Notice in the example below that in order to refer to the group "Living Room", y
- group.living_room
- group.bedroom
```
Default groups appear in the HOME tab, if not overridden by user views and groups. Default groups are hidden by default, so you must [customize](/docs/configuration/customizing-devices/) them to be visible in your custom groups and views.
```yaml
# Example configuration.yaml to include default groups in custom view
customize:
group.all_automations:
hidden: false
group.all_scripts:
hidden: false
group:
automation_view:
name: Automation
view: true
entities:
- group.all_automations
- group.all_scripts
```
## Customize group order
You can also order your groups using [customize](/docs/configuration/customizing-devices/) with `order: ` if they don't show up in the order you want them in.
```yaml
# Example configuration.yaml to order groups with order:
customize:
group.all_automations:
order: 1
group.all_scripts:
order: 2
group:
automation_view:
name: Automation
view: true
entities:
- group.all_automations
- group.all_scripts
```

4
source/_posts/2015-09-19-alarm-sonos-and-itunes-support.markdown
View File

@ -43,11 +43,11 @@ automation:
event: sunset
offset: "-01:00:00"
- platform: state
entity_id: group.all_devices
entity_id: all
state: home
condition:
- platform: state
entity_id: group.all_devices
entity_id: all
state: home
- platform: time
after: "16:00:00"