Home Assistant 2026.11.0: custom integrations not loaded

Call: Known issue. Home Assistant 2026.11.0 (Nov 4) moves HACS custom integrations over to the new built-in Marketplace. On some installs, every custom integration then shows “Not loaded” after the next restart. This is reported, not confirmed: one GitHub issue holds five independent reports, and the Home Assistant team hasn’t responded in it yet. A user found a likely cause and a fix that a second user confirmed. Check for it before you update.

What breaks: The first boot on 2026.11.0 looks fine. Then the migration deletes custom_components/hacs, and on the next restart the custom integrations disappear: “Not loaded,” can’t be reloaded, and redownloading them from the Marketplace doesn’t help. Reporters lost anything from 6 of 20 integrations to all of them.

Why, at least sometimes: On the installs that were traced, a stray copy of HACS’s own source files sat directly in custom_components/ (a top-level __init__.py, manifest.json, websocket/ and friends) next to the real hacs/ folder. Those files import from custom_components.hacs. Once the migration removes that folder, the import fails, the loader catches the error, and Home Assistant concludes you have no custom integrations at all. Without logging anything, naturally. Not every report has been traced to this, so if your custom_components/ is clean and you’re still hit, you have a different problem.

Who’s hit: Home Assistant installs that used HACS and move to 2026.11.0. The stray-file case looks like leftovers from a botched HACS install at some point in the past, which is the sort of thing a homelab collects over the years.

What to do:

Before updating, from the HAOS host shell, run ls -p /mnt/data/supervisor/homeassistant/custom_components | grep -v /. It should print nothing. If it lists files, that’s the problem.
Fix: take a backup, then move those top-level files (not the integration folders) out of custom_components/ and restart. One reporter quarantined them instead of deleting, which is the polite way.
Already broken: clean up as above, or restore your 2026.10.4 backup. Two reporters rolled back and got everything back without reinstalling.
Separately, a few integrations (alexa_media, tapo_control) have their own 2026.11 issues. Check your integrations’ trackers too.

Sources: home-assistant/core #190450 (opens in a new tab), home-assistant/core #190741 (opens in a new tab).

Home Assistant 2026.11.0: custom integrations not loaded

Sources

More from October 2026 patch cycle