Home Assistant Is Bringing HACS Into Core — And Marketplace Could Make Custom Integrations Much Easier

TL;DR

Before you orderOffer from Amazon

Get home appliances delivered free with Prime

• Fast, free delivery on millions of items
• Prime Video, Amazon Music and more included
• Member-only deals all year

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Home Assistant has merged a built-in Marketplace based on HACS into its development branches, with Core 2026.11 listed in documentation as the intended release. It is designed to let administrators find, install and manage community integrations and other add-ons in Settings, while leaving those projects community-maintained and unsupported by Home Assistant.

Home Assistant has merged Marketplace, a built-in component based on the Home Assistant Community Store (HACS), into its development branches. The planned change would give administrators a way to browse and manage community integrations, dashboard cards, themes and templates from Settings, without first installing HACS separately.

Marketplace is intended to bring HACS into Home Assistant largely as it exists today, with further enhancements planned later. Its catalog will let users search and filter projects, review project details, install content, select versions and remove installations. Browsing, installing and updating catalog items will not require a GitHub account. Adding a custom repository will still require connecting to GitHub.

According to the supplied report, existing HACS installations are expected to migrate automatically when Home Assistant first starts after the relevant update. Custom repositories, update entities and dashboard resources are set to carry over, while the old HACS integration and its files will be removed. Existing HACS addresses and project links are also expected to continue working, with links to individual projects opening their Marketplace pages.

Updates for installed community projects are expected to appear alongside other Home Assistant updates. The change is intended to bring installation and maintenance into the main interface. The report says it is not yet clear whether updates installed through Marketplace will avoid the need to restart Home Assistant, so users should not assume that behavior will change.

A Shorter Route to Community Projects

Home Assistant’s built-in integrations do not cover every device or service. Community-created integrations can fill some of those gaps, while custom cards, themes and templates offer other ways to adapt a setup. Putting their catalog inside Settings could make those projects easier to discover and install, particularly for users whose reason for trying Home Assistant is support for a specific device.

The change could also make independent projects easier to reach without requiring their developers to seek inclusion in Home Assistant Core. That matters because a project’s popularity does not necessarily mean its maintainer is prepared to take on the process or responsibilities associated with a Core integration. Marketplace would provide a more direct distribution path, while responsibility for maintaining each project remains with its community developers.

That distinction limits what the new interface promises. Home Assistant says, according to the source material, it does not test, audit or support content distributed through Marketplace. Users will have to accept a warning before installing or updating community content; replacing a built-in integration will require an additional confirmation. Easier access does not mean the items have received official approval or the same support as Core features.

HACS Moves Into Home Assistant

HACS is a separate store for community-created Home Assistant additions. It helps users find, download and update custom integrations, dashboard cards, themes and reusable templates. Until this planned change, users have needed to install and configure HACS separately from Home Assistant before they can access its listings.

Custom integrations can connect Home Assistant to devices or services that are not supported out of the box. The report notes that community projects have been useful to users trying to bring particular hardware into their smart-home setups. Marketplace is intended to make the store part of the Home Assistant interface, while keeping the projects themselves community-created rather than turning them into Core integrations.

The supplied report says the Marketplace integration and interface were merged into Home Assistant’s development branches this week. Documentation points to Home Assistant Core 2026.11 as the intended release; that is a planned target, not confirmation that the feature is already available in a stable release. The report also says device makers’ Work With Home Assistant certification requirements will not change: the Marketplace announcement does not replace the existing requirement for a Core integration where a maker does not use open standards such as Matter, Zigbee or Z-Wave.

Release Details Still Pending

The intended release is not a confirmed shipping date. The source material identifies Core 2026.11 as the target in documentation, but does not establish when that release will be published or whether the schedule will change. Further details about migration are expected in documentation when the update is released.

The exact scope of later Marketplace enhancements is also not specified. The report describes the initial change as bringing HACS into Core largely as it exists today, but does not list which capabilities may be altered or added. Users should check release notes and migration guidance before relying on any change to specific workflows, including restart behavior after updates.

Community content will remain subject to the risks that come with third-party software. The supplied material does not provide details about a review process for individual projects; it states that Home Assistant does not test, audit or support Marketplace content. Whether a particular integration works with a given setup, and how quickly its maintainer will resolve problems, will depend on that project and its community.

Watch for Core 2026.11

The next milestone is the release of a Home Assistant version that includes Marketplace. Documentation currently identifies Core 2026.11 as the intended target; users will need to wait for a release announcement and consult its release notes for confirmed availability and migration instructions.

When the change reaches an applicable update, existing HACS users are expected to see their installations migrate on the first start after updating. The reported plan is to carry across custom repositories, update entities and dashboard resources, while removing the former HACS integration and files. Users with important custom content should review the official migration documentation once it is published and confirm that their projects and resources remain available after the update.

Key Questions

What is Home Assistant Marketplace?

It is a planned built-in Home Assistant component based on HACS that would let administrators browse, install and manage community integrations, dashboard cards, themes and templates through Settings.

When will Marketplace be available?

The supplied report says the component has been merged into development branches and that documentation points to Core 2026.11 as the intended release. That target is not confirmation of a final release date.

Will community projects become officially supported?

No. The source material says Marketplace content will remain community-created and community-maintained. Home Assistant does not test, audit or support the content distributed through the store.

Do existing HACS users need to reinstall their projects?

The reported plan is for existing HACS installations to migrate automatically on the first start after the update, carrying over custom repositories, update entities and dashboard resources. Users should check the migration documentation when it is released for confirmed instructions and any exceptions.

Will Marketplace require a GitHub account?

The supplied report says browsing, installing and updating catalog content will not require a GitHub account. Users will still need to connect to GitHub to add custom repositories.

Source: rss