Some integrations are always enabled

[sciurius]

The problem

To test components I start HA with an (almost) empty config:

frontend:

However, despite the empty config. I still get the following integrations:

• Google Translate text to speech
• Shopping list
• Radio Browser

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[mib1185]

Hi @sciurius

This sounds like a request for support? We use GitHub for tracking issues with Home Assistant Core itself, not for providing support. If you are in need of support, you should try our Community Forum or join our Discord chat server.

Thanks! 👍

[sciurius]

Thanks for your reply. With an empty config no integrations should be enabled by default. I'd consider this a bug.

[mib1185]

there are some core integrations which are always loaded (when not in emergency recovery mode) Further default_config will also load some additional integrations. Those even an empty configuration.yaml will load some core integrations/components

[sciurius]

Sure. But in my example default_config: is not included.

I don't think Google Translate text to speech, Shopping list and Radio Browser are extremely critical integrations that always must be included.

[mib1185]

please provide the full configuration.yaml and also check if there are any configuration entries existing, which needs shopping list and radio browser

btw these are all integrations which will be set up during onboarding process, so they get a configuration entry created during onboarding, but can be disabled afterwards

[sciurius]

This is the complete configuration:

frontend:

I create a test setup as follows:

rm -fr ${TESTDIR}
mkdir -p ${TESTDIR}/custom_components
echo 'frontend:' >  ${TESTDIR}/configuration.yaml
hass -c ${TESTDIR}

btw these are all integrations which will be set up during onboarding process, so they get a configuration entry created during onboarding, but can be disabled afterwards

Speech-to-text, maybe.

But shopping list and radio browser are required for onboarding? Radio browser fails to setup anyway.

[frenck]

default_config is a YAML configuration, while the others listed here as not.

Home Assistant allows (UI) integrations to set up during onboarding, and it does so for some; including the ones listed in the OP + ones that are detected using discovery (and do not require authentication, for example, WLED, Elgato, ZHA, and many many more).

This is working as intended, you can remove the others in the integration dashboard if you do not wish to use them. As they are not YAML-based, they will not return after deleting them.

../Frenck