DEV Community

Cover image for How to Install HACS in Home Assistant, and the Marketplace from 2026.11
Michael Bernhart
Michael Bernhart

Posted on Edited on Originally published at cloudapp.dev

How to Install HACS in Home Assistant, and the Marketplace from 2026.11

From Home Assistant 2026.11 there is nothing left to install. HACS, the Home Assistant Community Store, ships inside Home Assistant as the Marketplace, under Settings → Marketplace. On 2026.10 or older you still install HACS yourself, and those steps are further down. (For what HACS actually is, see What is HACS?.)

I run Home Assistant in Docker and am on 2026.9 while writing this. I'm waiting for the first bugfix release of 2026.11, so the Marketplace sections come from the release notes and the Home Assistant documentation, and I haven't used it myself yet. I installed HACS myself following the steps for older versions.

Home Assistant 2026.11 or newer: use the Marketplace

Go to Settings → Marketplace. It sits between Apps and Dashboards, needs no setup and is available to administrators only. The catalog holds integrations, dashboard cards, themes and templates, and you can search it, filter it and sort it, for example by GitHub stars.

You don't need a GitHub account to browse, install or update catalog projects. The first visit shows a warning that nothing in the catalog is tested, audited or supported by the Home Assistant project. You can browse before accepting it, but installing and updating only work afterwards.

To install, open a repository's page and select Install. What follows depends on the type. An integration opens its setup page straight away when Home Assistant can load it without a restart. A dashboard card needs a browser reload. Themes and templates are reloaded automatically. Updates appear under Settings → Updates.

A project missing from the catalog can be added with Add from link and its repository URL. It has to be a public GitHub repository with a hacs.json file. This is where GitHub is still needed: the Marketplace asks you to connect an account, without access to private repositories and without permission to change anything on GitHub.

Already using HACS? What the upgrade changes

Home Assistant migrates HACS automatically on the first start after the update and removes the HACS integration and its files. Integrations, cards, themes and templates you installed stay and keep getting updates. Custom repositories and update entities carry over with their names, areas, labels and entity IDs, and bookmarks to /hacs open the Marketplace. The release notes and the documentation don't ask for a backup. I'll take one anyway, as before any version jump.

A few things do change:

  • It moves out of the sidebar. The Marketplace is under Settings, and the HACS options for sidebar title and icon are gone.
  • AppDaemon apps and Python scripts are no longer managed. The files stay and keep working, but they get no more updates. A repair tells you which ones this concerns.
  • Dashboard resources move to /local/community/. The old /hacsfiles/ paths keep working. If you define resources in YAML, a repair asks you to update them.
  • Templates need the new name. integration_entities('hacs') finds nothing anymore. Use integration_entities('marketplace').

To prepare, I have already searched my own configuration: no /hacsfiles/ path and no such template, so I expect neither of the last two to apply to me. You also can't stay on HACS by reinstalling it: Home Assistant 2026.11 blocks the custom integration.

Older than 2026.11: prerequisites

A running Home Assistant installation. You need to know which type you run (HAOS/Supervised vs. Container/Core) – the install method differs.

Container / Core: terminal access to the config directory. HAOS / Supervised: no terminal needed.

A free GitHub account – HACS loads its integrations through GitHub.

Older than 2026.11: install HACS step by step

1. Download HACS

HAOS / Supervised (the most common setup): go to Settings → Apps (called Add-ons until early 2026) → App store → ⋮ (top right) → Repositories, and add https://github.com/hacs/addons. Then install the Get HACS app, start it, and follow the instructions in the app logs.

Container / Core: run the official installer inside your Home Assistant config directory:

That one-liner has to run inside the Home Assistant configuration directory — the folder holding your configuration.yaml. In a Docker setup that folder lives on the host and is mounted into the container, so you have a choice: run the installer on the host in the mounted directory, or exec into the container and run it there. Either works, because both end up writing to the same place — the custom_components folder next to your configuration.

This command shows the mounted directories. Replace homeassistant with the name of your container:

docker inspect -f '{{range .Mounts}}{{.Source}} -> {{.Destination}}{{"\n"}}{{end}}' homeassistant

The line whose destination is /config is the directory you want. The installer looks for the file .HA_VERSION in several locations and stops with an error if it finds none.

wget -O - https://get.hacs.xyz | bash -

The official documentation runs the same command from inside the container; the result is identical:

docker exec -it homeassistant bash -c 'wget -O - https://get.hacs.xyz | bash -'

2. Restart Home Assistant

Go to Settings → System → Restart. Home Assistant only detects the new integration after a restart.

This was the only step that briefly stopped me. HACS installs files into custom_components, and Home Assistant only scans that folder at startup — so until you restart, HACS genuinely does not exist as far as Home Assistant is concerned. A configuration reload is not enough here; it has to be a full restart.

3. Add the HACS integration

Go to Settings → Devices & Services → Add Integration and search for HACS. If HACS doesn't appear: do a hard refresh or clear your browser cache. Then acknowledge the statements and submit.

4. Authorize with GitHub and finish

HACS uses a GitHub device OAuth flow: copy the device code it shows, open github.com/login/device, sign in, enter the code, and authorize HACS. Back in Home Assistant, assign HACS to an area and select Finish.

5. Install your first integration

HACS now appears in your sidebar. Open it, download an integration and restart Home Assistant, then add it under Settings → Devices & Services.

The HACS panel on my own instance: repositories grouped by status, with downloads, stars and last activity for each one.

How to check the HACS install actually worked

Three quick checks tell you whether HACS is properly set up:

  • HACS is in the sidebar. If it isn't, check that you restarted, finished the integration setup and that the files are under custom_components/hacs.
  • Settings → Devices & Services shows HACS as a configured integration — not just as something you can add. If it's still only in the "add" list, the setup flow didn't complete.
  • Opening HACS lists repositories rather than an empty page. If it stays empty, first check that the GitHub authorization finished.

If all three look right, HACS is set up.

What a finished install looks like under Settings → Devices & Services: HACS listed as a configured integration, not just an available one.

A word on trust before you install anything

Integrations from HACS or the Marketplace are third-party code running inside your Home Assistant process, with the same access to your instance that the built-in integrations have. They are not sandboxed. Cards, themes and templates come from third parties too, and nobody at Home Assistant reviews any of it. The Marketplace documentation says outright that its content can compromise your security and privacy.

I run several HACS integrations. Before installing something I don't recognise, I look at whether the repository has recent commits, whether issues get answered, and roughly how many people use it. If a project hasn't changed in two years, I check whether people report problems with current Home Assistant versions.

Common problems with HACS before 2026.11

HACS doesn't appear in the integration list: clear your browser cache or hard-refresh and double-check you restarted Home Assistant.

HACS stays empty: first check that the GitHub authorization in step 4 finished.

GitHub rate limit: wait until GitHub accepts requests again. Authorizing again doesn't reset the limit.

HACS installed but the integration you added still doesn't appear: installing through HACS only downloads the code. Almost every integration needs another Home Assistant restart afterwards, and then to be added under Settings → Devices & Services like any other integration.

Everything worked, then broke after a Home Assistant update: a custom integration that hasn't kept up with a breaking change will fail to load and show up in the logs at startup. Check the repository for an update before assuming your configuration is at fault.

Frequently asked questions

Is HACS free?

Yes. HACS is open source and free, and the release notes say everything in the Marketplace is free and will stay that way.

Do I need a GitHub account?

Not from 2026.11, unless you add custom repositories. On 2026.10 or older, yes: HACS loads its integrations through GitHub, so a free account is required.

Does it work with Home Assistant Container or Core?

The one-line installer for HACS works on all installation types. The Marketplace is an integration inside Home Assistant Core, and its manifest depends on nothing outside Core, so I expect it to work the same in Docker. I'll confirm that after my own upgrade.

How do I update integrations?

From 2026.11 they appear under Settings → Updates. In HACS, updates show up in its panel. In both cases an integration usually needs a restart afterwards.

Does HACS slow Home Assistant down?

HACS itself is negligible — it checks for updates in the background. The load comes from what you install through it, for example how often an integration polls its devices or services. When I look at the load, I start with the installed integrations and how often they poll.

Can I remove HACS again?

From 2026.11 the upgrade removes it for you, and the Marketplace comes with Home Assistant. On older versions, delete the integration under Settings → Devices & Services, then remove the hacs folder from custom_components and restart. Integrations you installed through HACS are separate folders and stay behind, so remove those too if you want a clean state.

Is HACS official?

It started as a community project. From 2026.11 it is part of Home Assistant as the Marketplace, while the projects in the catalog are still made by the community and aren't tested or supported by Home Assistant. HACS remains the name of the project and of the version for 2026.10 and older.

Where do I download HACS?

From 2026.11 there is nothing to download. On older versions the script from get.hacs.xyz fetches the current release from GitHub and places it under custom_components/hacs, and on HAOS the Get HACS app does the same. The release files live in the hacs/integration repository on GitHub, and you never need them by hand.

How long does the installation take?

On 2026.11 there is no installation. On older versions about ten minutes including the restart. The download itself takes seconds, and most of the time goes into the restart and the GitHub authorisation.

Can I install HACS without a terminal?

From 2026.11 no terminal is involved. On older HAOS and Supervised installs, yes, through the Get HACS app. On older Container and Core installs there is no way around the terminal, because the files have to land in the configuration directory. A single command is enough.

Can I still install HACS on 2026.11?

No. The HACS installer stops at 2026.11, and Home Assistant blocks the custom integration from that version on.

Next step

For what HACS is and why I use it, see What is HACS?.

Once the Marketplace or HACS is running, the harder question is what's worth adding. I keep a directory of HACS integrations here, ranked by GitHub stars and grouped into collections like energy, lighting and security, and a list of what is gaining stars this week.


Originally published at cloudapp.dev, where it is kept up to date.

Top comments (0)