From fac43222aab78bda713fce570342d72995b4bc15 Mon Sep 17 00:00:00 2001 From: Gary Barclay Date: Sun, 13 Jan 2019 10:47:30 +0000 Subject: [PATCH] Small changes to help fill a couple of small gaps. (#8111) * Small changes to help fill a couple of small gaps. Stopped short of offering a full example such as Harmony Remote config. * Fix comments --- source/_docs/configuration/packages.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index 00a3636b4f4..c899808e8a7 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -22,7 +22,7 @@ homeassistant: ...package configuration here... ``` -The package configuration can include: `switch`, `light`, `automation`, `groups`, or most other Home Assistant components. +The package configuration can include: `switch`, `light`, `automation`, `groups`, or most other Home Assistant components including hardware platforms. It can be specified inline or in a separate YAML file using `!include`. @@ -88,7 +88,7 @@ homeassistant: ``` This uses the concept splitting the configuration and will include all files in a directory with the keys representing the filenames. -See the documentation about [splitting the configuration](/docs/configuration/splitting_configuration/) for more information about `!include_dir_named` and other include statements that might be helpful. +See the documentation about [splitting the configuration](/docs/configuration/splitting_configuration/) for more information about `!include_dir_named` and other include statements that might be helpful. The benefit of this approach is to pull all configurations required to integrate a system, into one file, rather than accross several. ### {% linkable_title Customizing entities with packages %}