jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 17:27:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Explain limitation of multiple !include on top level (#22939)

Browse Source
This commit is contained in:
Erik Montnemery 2022-06-01 11:50:11 +02:00 committed by GitHub
parent 56b6bf624b
commit 600c3bc53c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_docs/configuration/splitting_configuration.markdown
View File

@ -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. 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 ```yaml
light: light: