Home Assistant · Guides & Tutorials

HACS becomes Marketplace in Home Assistant 2026.11: what to do

Home Assistant 2026.11 replaces HACS with the built-in Marketplace. What carries over, what stops updating, and the templates and YAML resources to check.

By the TechnoGecko Team· 22 October 2026 · Updated 22 October 2026· 6 min read

You don’t need to do anything. When Home Assistant 2026.11 starts for the first time, the new built-in Marketplace takes over from HACS. Everything you installed with HACS stays installed and keeps getting updates, your update entities keep their IDs, and HACS itself is removed. Three things need a look afterward: AppDaemon apps and Python scripts stop getting updates, dashboard resources move to a new path, and templates or tools that refer to HACS by name need changing.

What’s changing

HACS (the Home Assistant Community Store) has been a custom integration you installed yourself to get community integrations, cards and themes. Starting with Home Assistant 2026.11, the HACS documentation says, “HACS ships with Home Assistant itself, as the Marketplace integration.” You’ll find it under Settings > Marketplace. The catalog is the same, the repositories are the same, and publishers keep using the same hacs.json file.

Home Assistant’s release calendar lists 2026.11 for November 4, with the beta from October 28.

Before you update

1. Make a backup. It’s a big change to how your community integrations and cards are managed, so take a full backup first.
2. Note anything installed as AppDaemon or Python scripts. These are the only HACS types the Marketplace doesn’t manage (see below).
3. Note whether you manage dashboard resources in YAML. If you do, you’ll have a small edit to make afterward.
4. Search your templates for hacs. If anything uses integration_entities('hacs'), it’ll need a one-word change.

What carries over automatically

Per the HACS and Home Assistant docs, on the first start after the update:

• Everything you downloaded stays installed and keeps getting updates. Integrations, dashboard cards, themes and templates all move across.
• Custom repositories carry over. These are the repositories you added by URL that aren’t in the default catalog.
• Update entities carry over with their names, areas and labels, and keep their entity IDs. Automations and dashboards that use them keep working.
• Old links still work. Bookmarks to /hacs open the Marketplace, and buttons made for HACS open the repository in the Marketplace.
• HACS itself is removed, together with its files. You can’t install HACS on 2026.11 or newer: Home Assistant blocks it, because the Marketplace replaces it.

One exception: a custom repository with no hacs.json file stays installed, but the Marketplace can’t update it.

What works differently

The Marketplace lives under Settings

It’s at Settings > Marketplace, not in the sidebar, and it’s available to administrators only. The HACS options for the sidebar title and icon are gone. The first time you open it, the Marketplace shows a warning that community content isn’t reviewed or supported by the Home Assistant project. Until you accept that warning, Home Assistant can’t install or update Marketplace content, including from an automation.

AppDaemon apps and Python scripts stop getting updates

The Marketplace installs four types: integrations, dashboards (cards and other frontend items), themes and templates. It doesn’t manage AppDaemon apps or Python scripts. If you installed any through HACS, their files stay where they are and keep working, but they won’t get updates from the Marketplace. A repair under Settings > System > Repairs tells you which ones are affected. To keep them current, update them by hand from each project’s repository.

Dashboard resources move to /local/community/

The Marketplace serves dashboard files from /local/community/. The old /hacsfiles/ paths keep working. If you manage dashboard resources in the UI, there’s nothing to do. If you configured resources in YAML, a repair reminds you to change them to the new path. For example:

# Before (HACS)
resources:
  - url: /hacsfiles/lovelace-mushroom/mushroom.js
    type: module

# After (Marketplace)
resources:
  - url: /local/community/lovelace-mushroom/mushroom.js
    type: module

The folder name above is an example. Use the path the repair or the install dialog shows for your card. If you manage resources in YAML, the Marketplace can’t add new resources for you either: its install dialog shows the line to add.

Templates, automations and tools that mention HACS

Update entities keep their IDs, so most automations are fine. What changes is anything that refers to HACS itself. From the “Coming from HACS” section of Home Assistant’s Marketplace docs:

A common example is a template sensor that counts pending HACS updates. Here’s a Marketplace version. It uses the integration name from the Marketplace docs, and counts update entities in the on state, which Home Assistant’s update docs define as an update being available:

template:
  - sensor:
      - name: "Marketplace updates pending"
        state: >
          {{ integration_entities('marketplace')
             | select('match', 'update\.')
             | select('is_state', 'on')
             | list | count }}

GitHub: when you need to connect it

You can browse, install and update catalog content without connecting a GitHub account. You need a GitHub connection to add custom repositories, to keep them updated, and to get a higher request limit. The Marketplace uses GitHub’s device sign-in: it shows a code, you enter it on GitHub, and you approve the connection there. Home Assistant’s docs say the connection doesn’t request access to private repositories or permission to make changes. You can revoke it any time in GitHub under Settings > Applications > Authorized OAuth Apps.

Home Assistant’s docs don’t say whether a GitHub connection you made in HACS carries over. If your custom repositories stop updating after the switch, connect GitHub again: go to Settings > Devices & services > Marketplace, open the three-dot menu of the Marketplace entry and select Reconfigure.

Troubleshooting

“Why are my cards missing?” First, reload the browser, since the Marketplace adds resources and the browser can cache the old ones. If you manage resources in YAML, check them against the new /local/community/ path (the old /hacsfiles/ path should still work). Then check Settings > System > Repairs.

“The Marketplace is not available.” It doesn’t load in recovery mode. If you’re not in recovery mode, check the Home Assistant logs.

“GitHub limit reached.” Without a GitHub connection, the Marketplace shares GitHub’s hourly request limit with other devices on your internet connection. Wait for it to reset, or connect GitHub.

A repository was removed. If the catalog removes a repository, for example because it’s abandoned, installed copies keep working without updates and a repair explains why. If it’s marked critical (harmful), the Marketplace uninstalls it immediately and restarts Home Assistant.

Something you installed doesn’t work. That’s for the project’s own issue tracker, linked from its Marketplace page. Bugs in the Marketplace itself go to the Home Assistant core repository’s Marketplace issues.

A reminder about community content

Nothing changes about who makes community integrations and cards. Home Assistant’s docs are blunt that Marketplace content is “made and published by the community, not by the Home Assistant project”, isn’t reviewed, audited or supported by it, and can access your home, your data and your network. Before you install something, check its author, recent activity and community feedback.

Once you’re updated, our dashboards guide covers using community cards in Home Assistant’s Sections view.

How pages like this are made: How we work.