HACS Moves to Marketplace in Home Assistant 2026.11: What to Check

4 min read

,
Home Assistant 2026.11 Marketplace Browse tab, the built-in replacement for HACS, listing community integrations and dashboard cards grouped by status

HACS is moving into Home Assistant as Marketplace in version 2026.11. Your installed community integrations, cards, themes, custom repositories and update entities are expected to migrate on the first start after upgrading. You should still make a full backup and check the few HACS items that Marketplace will no longer manage.

Home Assistant 2026.11 is still in beta on 2 November. The project schedules stable releases for the first Wednesday of each month, which falls on 4 November this time. If you use the stable channel, wait for the stable release and check its final release notes before updating. The steps below are preparation for that update.

What changes when HACS becomes Marketplace

Marketplace appears under Settings > Marketplace and uses the HACS catalog. It is built into Home Assistant, so there is no separate HACS integration to install. The community still builds and supports the projects inside it; the Marketplace itself does not make every listing an official Home Assistant integration.

Home Assistant 2026.11 Settings page showing the new Marketplace entry between Apps and Dashboards, which replaces HACS
In Home Assistant 2026.11, HACS becomes Marketplace under Settings. Screenshot: Home Assistant
  • Installed repositories and custom repositories carry over, along with their update entities.
  • AppDaemon apps and Python scripts remain on disk but Marketplace will not manage their updates.
  • A custom repository needs a hacs.json file for Marketplace to install or update it.
  • The old /hacs link redirects to Marketplace, and existing dashboard files on /hacsfiles/ remain reachable.

Marketplace projects remain community software. Check each project’s maintainer, required Home Assistant version and recent activity before installing a new integration.

Home Assistant Marketplace repository page for the Spook integration showing the installed version, a Set up button, required Home Assistant version, downloads and GitHub stars
Each Marketplace project page shows the required Home Assistant version, downloads and GitHub activity. Screenshot: Home Assistant

What to do before updating

  • Make a full Home Assistant backup from Settings > System > Backups. Download a copy off the Home Assistant machine and keep the backup encryption key or emergency kit with it.
  • Update the HACS projects you already use while still on 2026.10. Make a note of custom dashboard cards and any integrations that have been abandoned.
  • List any AppDaemon apps, Python scripts and custom repositories you added through HACS. For custom repositories, check whether their current release has hacs.json.
  • Read the final 2026.11 release notes when the stable build is published. Other changes in that release may affect your integrations or dashboards.

A backup stored only on the same device is a weak rollback plan. Keep a copy elsewhere before the first 2026.11 start, since that start removes the separate HACS integration and migrates its data.

After the stable update

Update Home Assistant through your normal method for Home Assistant OS, Container or Core. Once it restarts, open Settings > Marketplace as an administrator. Check that your installed projects and custom repositories appear. Then look under Settings > System > Repairs and Logs for issues the migration reports.

If a custom integration stops working, check the project’s own compatibility notes before reinstalling anything. For dashboard cards, reload your browser and check their resources. If AppDaemon or Python scripts were installed through HACS, you now need to manage updates for those files yourself.

What if something is missing?

First check whether the repository is still in the catalog and whether its latest version meets Marketplace’s requirements. A project without hacs.json cannot be installed or updated through Marketplace. Do not delete the files just because an update is missing; check the project’s release page and Home Assistant’s Repairs message for the specific problem.

If a dashboard resource was added manually in YAML and fails after upgrading, check its URL. Existing /hacsfiles/ files remain reachable according to Home Assistant’s migration documentation, so do not rewrite working paths pre-emptively. If you need to replace a resource later, use the path shown by the installed project in Marketplace.

Should you install the beta?

For a home you depend on every day, wait for the stable build. The beta exists so users and maintainers can find migration problems before the release. If you do test it, use a separate setup or make sure you have a full, restorable backup and time to troubleshoot.

This is mainly a change to where you manage community projects. For most HACS users, the first job is simple: back up, update the existing projects, and check Marketplace and Repairs after Home Assistant 2026.11 is stable.

Share this story

About the author