From 3e2886d1f70e16565a31d7361cfc6e2dcb44d262 Mon Sep 17 00:00:00 2001 From: akasma74 Date: Wed, 5 Feb 2020 09:16:11 +0000 Subject: [PATCH] one more example of configuring packages folder (#11971) * one more example of configuring packages folder I thought it's useful to have a real example of what's possible to achieve. * :pencil2: Tweaks Co-authored-by: Franck Nijhof --- source/_docs/configuration/packages.markdown | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown index d3ba7e9dba0..b7fffed55f6 100644 --- a/source/_docs/configuration/packages.markdown +++ b/source/_docs/configuration/packages.markdown @@ -84,6 +84,24 @@ 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. +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: