From 600c3bc53cf8853f2062044d36a7e1c37c0d44ca Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Wed, 1 Jun 2022 11:50:11 +0200 Subject: [PATCH] Explain limitation of multiple !include on top level (#22939) --- source/_docs/configuration/splitting_configuration.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_docs/configuration/splitting_configuration.markdown b/source/_docs/configuration/splitting_configuration.markdown index 8fb85cc92ee..baef0f92a42 100644 --- a/source/_docs/configuration/splitting_configuration.markdown +++ b/source/_docs/configuration/splitting_configuration.markdown @@ -76,7 +76,9 @@ device_tracker: !include device_tracker.yaml Nesting `!include`s (having an `!include` within a file that is itself `!include`d) will also work. -You can, as well, have multiple top-level `!include`s for a given integration, if you give a different label to each one: +Some integrations support multiple top-level `!include`s, this includes integrations defining an IoT domain, e.g. `light`, `switch`, `sensor` as well as the `automation`, `script` and `template` integrations, if you give a different label to each one. Configuration for other integrations can instead be split up by using packages. To learn more about packages, see the [Packages](/docs/configuration/packages) page. + +Example of multiple top-level keys for the `light` platform. ```yaml light: