From dc7b3458b36501e80eeaf177d57509d68ce27a2f Mon Sep 17 00:00:00 2001 From: Josh Nichols Date: Thu, 28 Dec 2017 04:00:06 -0500 Subject: [PATCH] Try to clarify acceptable component names in a package (#4284) I read this a few times, and thought the original language was confusing, or at least a little ambiguous. Hopefully this helps a little? --- source/_docs/configuration/packages.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index 09feb26aabd..584014521f4 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -63,7 +63,7 @@ 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). +1. Component names may only use the basic form (e.g. `switch`, but not `switch 1` or `switch aa`). 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.