Vulpo 1.4Updated
HACS becomes the Home Assistant Marketplace in 2026.11: what changes
Starting with Home Assistant 2026.11, due in early November 2026, HACS is built in as the Marketplace under Settings > Marketplace. There is nothing to install: on the first start after the update, the integrations, cards and themes HACS installed move over and keep getting updates. Until you update, keep using HACS.
What the Marketplace is
Home Assistant 2026.11, due in early November 2026, ships the Marketplace as part of Home Assistant itself, under Settings > Marketplace. This guide follows the Marketplace documentation published ahead of the release and is checked against the release notes once they are out. It grew out of HACS and reads the same catalog, the hacs/default list on GitHub, so the integrations, dashboard cards, themes and template macros known from HACS are all there. Only administrators can open it, and there is nothing to download first. The first time it opens, Home Assistant asks you to accept a warning: the Marketplace's contents come from community authors, and the Home Assistant project neither checks nor supports them. Until you accept, nothing can be installed or updated from it, not even by an automation. Inside, you can search, filter by type or by what is installed, and sort by GitHub stars or recent activity.
What happens when you update
The move runs by itself: when Home Assistant first starts on the new version, the Marketplace replaces HACS and migrates its content. One step is left for you: open Settings > Marketplace once, and if it shows the warning about community content, accept it. Until then, nothing installs or updates from the Marketplace, not even from an automation.
Your downloads
Integrations, dashboard cards, themes and templates downloaded with HACS remain in place and continue to receive new versions. AppDaemon apps and Python scripts stay but stop updating, see the table below.
Custom repositories
Repositories you added by hand come along, as long as they have a hacs.json file. One without it stays installed but can no longer be updated.
Update entities
They keep their entity IDs, names, areas and labels, so automations and dashboards built on them carry on working. Two exceptions are in the table below: the release_summary attribute and templates that ask for HACS entities.
HACS itself
The HACS integration and its files are removed. Bookmarks to /hacs open the Marketplace, and HACS cannot be installed on 2026.11 or newer because Home Assistant blocks it.
What to check after updating
Most setups need no changes. These are the cases that do.
| If you use | After 2026.11 |
|---|---|
| AppDaemon apps or Python scripts from HACS | They keep working, but the Marketplace no longer manages or updates them. A Repair lists the affected ones. |
| Dashboard resources added in YAML | Downloaded cards are now served from /local/community/. The old /hacsfiles/ paths still work, and a Repair reminds you to update the YAML. |
| Templates with integration_entities('hacs') | They come back empty; switch them to integration_entities('marketplace'). |
| Restart hints in the release_summary attribute | That attribute stays empty. The Marketplace asks for restarts through a Repair. |
| Scripts or tools calling hacs/ WebSocket commands | They get an unknown-command error. The Marketplace has its own marketplace/ commands with a different format. |
Do you need a GitHub account?
Not for the catalog: browsing, installing and updating catalog content works without one. A connection matters for custom repositories: you need it to add one with Add from link, and with it the Marketplace checks your custom repositories for updates every 48 hours. It also raises GitHub's request limit. The connection uses GitHub's device flow: Home Assistant shows a code, you approve it on GitHub, and your password never goes into Home Assistant. It can read public information only. Without one, the requests from your home count against a single hourly GitHub allowance that all devices on your network draw from, so they can be refused when it is used up.
What the Marketplace checks
Before and after installing, the Marketplace runs a few checks of its own.
Archived and removed repositories
Repositories their authors archived are refused, as are most of those dropped from the catalog. If the catalog drops something you already have, it keeps working but stops getting updates, and a Repair explains why.
Clashes with built-in integrations
If a community integration uses the same domain as a built-in one, the install dialog asks you to confirm. After a restart, the community version replaces the built-in one for that domain.
Older Home Assistant versions
When the latest release requires a later Home Assistant version than the one you run, you are offered earlier versions that fit.
Size limits
Downloads over 100 MiB or with more than 50,000 files are refused.
Critical repositories
If a repository is marked critical, the Marketplace removes it at once and restarts Home Assistant, with a Repair that asks you to check the affected automations and dashboards.
Still on 2026.10 or older?
Keep using HACS. Nothing changes until you update Home Assistant, and the HACS documentation for versions before 2026.11 stays online. Read its upgrade notes before you update, especially if you use AppDaemon apps, Python scripts or dashboard resources in YAML.
Where Vulpo fits
Vulpo is a native Home Assistant app for iPhone, iPad, Mac and Apple Watch. It shows entities from Marketplace integrations like any others, and a few get their own cards: the 3D printer card for the Bambu Lab integration (part of Vulpo Pro), the plant card for Plant Monitor and the waste collection card for Waste Collection Schedule. Dashboard cards and themes from the Marketplace do not appear in Vulpo, because it draws its own cards instead of Home Assistant dashboards. Vulpo is made by the publisher of this site.
Questions
Do I need to do anything when I update to 2026.11?
Only one thing. The Marketplace replaces HACS by itself on the first start after the update and keeps what you installed. Afterwards, open Settings > Marketplace once and accept the warning if it appears, because nothing installs or updates until you do.
Will I lose integrations I installed with HACS?
No. They stay installed, keep their entity IDs and keep getting updates. Only custom repositories that lack hacs.json stop receiving updates.
Can I still install HACS on 2026.11 or newer?
No. Home Assistant blocks the HACS custom integration from 2026.11 on. The Marketplace replaces it and reads the same catalog.
Does the Marketplace install apps (add-ons)?
No. Apps, called add-ons before Home Assistant 2026.2, are still installed from the Apps page under Settings, and the Marketplace cannot add app repositories.
Do I need a GitHub account for the Marketplace?
Only for custom repositories: to add them by link and to have them checked for updates. Browsing, installing and updating catalog content works without one.
Sources
- HACS: HACS and the Marketplace
- Home Assistant: Marketplace integration (2026.11 docs)
- Home Assistant: Marketplace install checks
- HACS is moving to Home Assistant as Marketplace (issue 5590)
Facts about other apps come from their App Store listings and documentation as of the date above. Home Assistant is a trademark of the Open Home Foundation; Vulpo is not affiliated with it. Corrections: josh@vulpo.app.