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-23 09:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add periods

Browse Source
This commit is contained in:
Fabian Affolter 2017-01-14 18:46:29 +01:00
parent d90c4a4baf
commit 7f0c26f72f
No known key found for this signature in database
GPG Key ID: E23CD2DD36A4397F
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
source/_topics/packages.markdown
View File

@ -23,7 +23,7 @@ homeassistant:
The package configuration can include: `switch`, `light`, `automation`, `groups` or the majority of the Home Assistant components. The package configuration can include: `switch`, `light`, `automation`, `groups` or the majority of the Home Assistant components.
It can be specified inline, or in a seperate YAML file using `!include` It can be specified inline or in a seperate YAML file using `!include`.
Inline example, main `configuration.yaml`: Inline example, main `configuration.yaml`:
@ -62,8 +62,8 @@ light:
There are some rules for packages that will be merged: There are some rules for packages that will be merged:
1. Component names may only use the basic form (e.g. `switch` and `switch 1` or `switch aa` is not accepted) 1. Component names may only use the basic form (e.g. `switch` and `switch 1` or `switch aa` is not accepted).
2. Platform based components (`light`, `switch`, etc) can always be merged 2. Platform based components (`light`, `switch`, etc) can always be merged.
3. Components where entities are identified by a key that will represent the entity_id (`{key: config}`) need to have unique 'keys' between packages and the main configuration file. 3. Components where entities are identified by a key that will represent the entity_id (`{key: config}`) need to have unique 'keys' between packages and the main configuration file.
For example if we have the following in the main config. You are not allowed to re-use "my_input" again for `input_boolean` in a package: For example if we have the following in the main config. You are not allowed to re-use "my_input" again for `input_boolean` in a package:
@ -72,7 +72,7 @@ There are some rules for packages that will be merged:
input_boolean: input_boolean:
my_input: my_input:
``` ```
4. Any component that is not a platform [2], or dictionaries with Entity ID keys [3] cannot be merged and can only occur once between all packages and the main config 4. Any component that is not a platform [2], or dictionaries with Entity ID keys [3] cannot be merged and can only occur once between all packages and the main configuration.
<p class='note tip'> <p class='note tip'>
Components inside packages can only specify platform entries using configuration style 1, where all the platforms are grouped under the component name. Components inside packages can only specify platform entries using configuration style 1, where all the platforms are grouped under the component name.