Yaml configuration - 'include' deprecated?

Hey,

while troubleshooting some other topic I found today that if I run
python3 -m homeassistant --script check_config -c /config
I receive warning about:

Testing configuration at /config
WARNING:homeassistant.helpers.config_validation: The 'include' option is deprecated, please remove it from your configuration

So what is the strategy forward?
Will we be unable to use packages and includes via yaml configuration?

include is not deprecated. Share your config so we can see what’s wrong.

how do I share my full config if it is using packages and includes massively?

I’m not sure. Include hasn’t been deprecated, so you need to search your config if you can’t share all the files.

search for include: in your files, start there.

sorry - I don’t get the idea behind this…
What should be the benefit of having now a list of all includes?


You didn’t do as I asked. You searched for include. I said search for include:.

Anyways, the benefit of searching for include: is that you can see where that key exists in your configuration and you can remove it or handle it.

Again include is not deprecated. So !include will continue to work. The error message / config error is about the key include: which is linked to an integration. Once you figure out which integration that is, you can alter the yaml to the include: replacement.

Thanks for the explanation - where do you know from this is coming from an integration and why do you know that it needs to be include: (since the initial error message shows ‘include’ not 'include: ?

most of the ‘include:’ results are from ‘logbook’, ‘history’ or ‘recorder’ since I only include there what is really needed. But I could not find any deprecation notice of this

Because, config validation does not know about !include. That’s a function that merges configuration. Config validation validates keys in your config, i.e. include:.

Right, that means you need to grep your config for all include: and find the one where the deprecation exists.