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-07-24 17:57:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clean up device vs entity mixup in older documentation (#18555)

Browse Source
This commit is contained in:
Franck Nijhof 2021-07-26 11:13:55 +02:00 committed by GitHub
parent b4efa02eb0
commit a302a89482
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
source/_docs/configuration/devices.markdown
View File

@ -3,16 +3,16 @@ title: "Adding devices to Home Assistant"
description: "Steps to help you get your devices in Home Assistant."
---
Home Assistant will be able to automatically discover many devices and services available on your network if you have [the discovery component](/integrations/discovery/) enabled (the default setting).
Home Assistant will be able to automatically discover many devices and services
available on your network.
See the [integrations overview page](/integrations/) to find installation instructions for your devices and services. If you can't find support for your favorite device or service, [consider adding support](/developers/add_new_platform/).
See the [integrations overview page](/integrations/) to find installation
instructions for your devices and services. Most integration can be
fully configured via the user interface these days; however, some older or
more complex integrations may need to be configured manually using YAML.
Classification for the available integrations:
- [IoT class](/blog/2016/02/12/classifying-the-internet-of-things): Classifier for the device's behavior.
- [Quality scale](/docs/quality_scale/): Representation of the integration's quality.
Usually every entity needs its own entry in the `configuration.yaml` file. There are two styles for multiple entries:
For some of these integrations, every entity needs its own entry in the
`configuration.yaml` file. There are two styles for multiple entity entries:
## Style 1: Collect every entity under the "parent"
@ -32,9 +32,10 @@ switch:
- platform: vera
```
## Style 2: List each device separately
## Style 2: List each entity separately
You need to append numbers or strings to differentiate the entries, as in the example below. The appended number or string must be unique.
You need to append numbers or strings to differentiate the entries, as in the
example below. The appended number or string must be unique.
```yaml
sensor bedroom:
@ -59,10 +60,12 @@ switch 2:
platform: vera
```
## Grouping devices
## Grouping entities
Once you have several devices set up, it is time to organize them into groups.
Each group consists of a name and a list of entity IDs. Entity IDs can be retrieved from the web interface by using the {% my developer_states title="States page in the Developer Tools" %}.
Once you have several entities set up, it is time to organize them into groups.
Each group consists of a name and a list of entity IDs. Entity IDs can be
retrieved from the web interface by using the
{% my developer_states title="States page in the Developer Tools" %}.
```yaml
# Example configuration.yaml entry