What it means
configuration.yaml or a config entry refers to an integration that Home Assistant cannot find.
Why it happens
- A custom integration (HACS and others) is not in custom_components/ or the folder name differs from the domain.
- The integration was removed from Home Assistant in a new version.
- A typo in the integration name in configuration.yaml.
How to fix it
- Check that config/custom_components/<name>/manifest.json exists and that "domain" matches.
- Reinstall it from HACS and restart Home Assistant.
- Read the release notes of your version for removed integrations and delete the leftover block.
Useful tools
Other Home Assistant errors
- A request from a reverse proxy was received from 172.30.33.0, but your HTTP integration is
- Received X-Forwarded-For header from an untrusted proxy 172.18.0.2
- Login attempt or request with invalid authentication from 192.168.1.50 (192.168.1.50). Req
- Invalid config for 'automation' at automations.yaml, line 3: required key 'triggers' not p
- Template variable warning: 'dict object' has no attribute 'to_state' when rendering '{{ tr