From 7d99847e2367ff2a2c10cc22b614ab4bc9767db9 Mon Sep 17 00:00:00 2001 From: akasma74 Date: Tue, 4 Feb 2020 20:59:15 +0000 Subject: [PATCH 1/2] one more example of configuring packages folder I thought it's useful to have a real example of what's possible to achieve. --- source/_docs/configuration/packages.markdown | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index d3ba7e9dba09..31f1f0110653 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -82,8 +82,21 @@ 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. The benefit of this approach is to pull all configurations required to integrate a system, into one file, rather than across several. - +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 across several. +The following example allows to have subfolders in the `packages` folder, which could make managing multiple packages easier by grouping: +```yaml +homeassistant: + packages: !include_dir_merge_named packages/ +``` +and in `packages/subsystem1/functionality1.yaml`: +```yaml +subsystem1_functionality1: + input_boolean: + ... + binary_sensor: + ... + automation: +``` ### Customizing entities with packages It is possible to [customize entities](/docs/configuration/customizing-devices/) within packages. Just create your customization entries under: From 39d9f4d92e4eab37e354b810ab976df91ce658ca Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 5 Feb 2020 10:01:53 +0100 Subject: [PATCH 2/2] :pencil2: Tweaks --- source/_docs/configuration/packages.markdown | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index 31f1f0110653..b7fffed55f6f 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -82,13 +82,17 @@ 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. The benefit of this approach is to pull all configurations required to integrate a system, into one file, rather than across several. +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 across several. + The following example allows to have subfolders in the `packages` folder, which could make managing multiple packages easier by grouping: + ```yaml homeassistant: packages: !include_dir_merge_named packages/ ``` + and in `packages/subsystem1/functionality1.yaml`: + ```yaml subsystem1_functionality1: input_boolean: @@ -97,6 +101,7 @@ subsystem1_functionality1: ... automation: ``` + ### Customizing entities with packages It is possible to [customize entities](/docs/configuration/customizing-devices/) within packages. Just create your customization entries under: