From 7f0c26f72fafed8d06242f00617871828e829cf5 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 14 Jan 2017 18:46:29 +0100 Subject: [PATCH] Add periods --- source/_topics/packages.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_topics/packages.markdown b/source/_topics/packages.markdown index 30358b1ea1b..369ba6d3443 100644 --- a/source/_topics/packages.markdown +++ b/source/_topics/packages.markdown @@ -23,7 +23,7 @@ homeassistant: 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`: @@ -62,8 +62,8 @@ light: 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) -2. Platform based components (`light`, `switch`, etc) can always be merged +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. 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: @@ -72,7 +72,7 @@ There are some rules for packages that will be merged: input_boolean: 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.

Components inside packages can only specify platform entries using configuration style 1, where all the platforms are grouped under the component name.