In the documentation about Splitting Up the Configuration, specifically this section here, we are invited to modularize the configurations for certain integrations by adding a space after the key and then some discriminating text, for example (in configuration.yaml):
light groups: !include light-groups.yaml
light switches: !include light-switches.yaml
…so that the extra text after “light” is there to keep the YAML parser happy, but the light integration is smart enough to pull in any dictionary element whose key starts with ‘light’.
The problem is that the aforementioned documentation page tells us that “Some integrations support multiple top-level !include statements”, and lists a few, but it doesn’t tell us how to tell whether any others support it.
Alas, it appears that the helper integrations still do not, because I tried:
# A few inclusions to make sure that '<key> <modifier>: !include ...' is working
input_number telltale: !include telltale_input_number.yaml
input_text telltale: !include telltale_input_text.yaml
input_datetime telltale: !include telltale_input_datetime.yaml
where the included files would look something like:
telltale:
name: "Telltale - Datetime"
has_date: true
has_time: true
and those just don’t work at all (even though Developer Tools says that the configuration looks fine). After a day of trying every variation I could think of, I finally gave up and went with Packages… which, arguably, is the better was to go about it, but it would have been nice to have known that it was the only viable route 12 hours ago.
So… is there some wiki page, somewhere, which details which integrations support this trick and which don’t?