17 - Nov - 2026

Home Assistant’s new marketplace could change everything

Home Assistant is one of the most expandable pieces of software I’ve ever come across, but one of its biggest strengths is also a massive barrier. The platform can support a variety of devices, services, dashboard cards, themes, and automations, but most of its most interesting additions are found outside the official integration catalog.

Accessing them usually means installing the Home Assistant Community Store, also known as HACS. And while the installation isn’t overly complicated, it might seem like a hassle to newcomers. But that’s about to change as HACS is expected to become a built-in integration called Marketplace starting with Home Assistant 2026.11.

HACS finally stops being a homework assignment

No repo URLs, no download scripts, and no GitHub login for the main catalog

HACS has long served as Home Assistant’s unofficial app store, even though everything it offers is free and open-source. It lets users discover, install, update, and even remove community-built integrations and interface components without manually copying files into Home Assistant’s configuration directory.

The problem is that installing HACS has never been particularly beginner-friendly. Depending on how you’ve deployed Home Assistant, you might need to either add a third-party app repository or enter a container and run a download script. Then Home Assistant must be restarted, HACS added as an integration, and authorized via GitHub before you can access it. Even then, you might occasionally troubleshoot it via browser caching or due to installation problems.

HA’s new Marketplace removes most of that friction. It’ll be set up automatically and be accessible from the main settings menu. Users will be able to browse, install, and update items from the main catalog without connecting a GitHub account. GitHub authentication will still be required for custom repositories and versions outside the catalog.

This might only sound like a minor usability improvement, but it can significantly increase how many HA users explore community-made software. Currently, the easiest way to add integrations is via the Integrations menu in HA, which can be rather limited if you’re using anything outside standard smart home devices.

The community moves faster than core, and now it gets a front door

Integrations, cards, themes, and macros, minus the GitHub scavenger hunt

HACS page in Home Assistant.
Screenshot taken by Yadullah Abidi | No attribution required.

Now HA already has thousands of official integrations, but the community around it moves much faster than the core project. A developer can create an integration for a niche device, add support for a lesser-known cloud service, build an experimental dashboard card, or even fix problems with HA itself that the core project won’t address without waiting to meet Home Assistant’s requirements for inclusion in the core project.

Marketplace will give those projects a much more prominent front door. It will handle four main categories: custom integrations, dashboard cards and plugins, themes, and reusable template macros. Blueprints will continue to use import links and the Blueprint Exchange, while AppDaemon apps and Python scripts will not be supported.

This matters because discoverability is just as important as availability. A useful integration hidden in a GitHub repository isn’t doing anyone any good unless someone spends the time and effort to dig it out for themselves. Put it in a searchable interface that ships with every Home Assistant installation, and suddenly it’s much easier for it to become part of the usual setup experience.

Marketplace also provides a much smoother path for an experimental project to make it as an official integration. Home Assistant’s contributor documentation explicitly presents it as a place where new integrations and dashboard cards can build a user base before maintainers consider bringing them into the platform itself.

Updates finally show up where you already look for updates

One update entity per download, release notes included, no more guessing

Home Assistant update screen.
Screenshot taken by Yadullah Abidi | No attribution required.

Installing community software is only half the problem. Keeping it updated and active is equally important, especially when Home Assistant’s rather fast-moving release cycle can occasionally bring up compatibility issues.

Every Marketplace download will have its own update entity. This means new versions will appear under Settings and Updates alongside Home Assistant’s other updates, complete with release notes. Developers can specify the minimum compatible Home Assistant release in the project’s hacs.json file, preventing incompatible versions from being offered to older installations and removing yet another hassle for inexperienced users.

Existing HACS users shouldn’t have to rebuild anything either. On the first startup after upgrading, Marketplace is designed to take over the existing HACS configuration. Installed content, custom repositories, dashboard resources, update entities, entity IDs, labels, and areas should simply carry across, while old HACS URLs automatically redirect to the Marketplace.

Marketplace doesn’t mean Home Assistant vouches for it

Easier to install, not safer to trust, and a warning label isn’t vetting

Home Assistant Featured Image
Shaun Cichacki/MUO

Calling HACS a marketplace inside HA can cause one potentially dangerous misunderstanding: it may make community projects seem officially vetted. Just because a project exists on HACS or Marketplace, that doesn’t mean it’s becoming an official Home Assistant integration.

Home Assistant will not test, audit, support, or guarantee everything distributed via Marketplace. You’ll have to accept a warning before installing or updating any community-made content, and replacing a built-in integration requires an additional confirmation.

There are some technical safeguards in place, though. Marketplace itself validates catalog data, confines extraction and removal to expected folders, checks required files, and can even roll back an installation if validation checks fail. As someone who’s submitted projects to HACS, the approval process can take months, and your extension can be sent back for changes if the reviewer isn’t happy.

Themes, templates, integrations, and dashboard plugins each receive type-specific checks. However, custom integrations still execute code inside Home Assistant, while custom cards execute code inside your browser. The current design also doesn’t add package signatures or checksums to the downloaded content for validity either.

All things considered, Marketplace makes community software easier to install, but not inherently safer to trust. You’re still responsible if you end up downloading a malicious or broken extension, although the submission standards are good enough to keep this a rare case.

HACS changed what Home Assistant could do; Marketplace changes who tries it

The immediate version of Marketplace is intentionally close to HACS rather than a complete reinvention. The existing catalog remains in place, and developers will continue submitting repositories through the same hacs/default project.

The bigger change is cultural. Community extensions will no longer feel like power-user features added on top of Home Assistant. They’re on their way to becoming a visible, built-in layer of the platform. HACS already changed what Home Assistant could do. Marketplace is just expanding who feels comfortable doing it.

Leave a Reply

Your email address will not be published. Required fields are marked *