HACS Is Becoming a Built-In Marketplace in Home Assistant 2026.11. Convenience Is Not the Same as Trust

A small compact mini PC on a desk, the kind of machine that runs Home Assistant OS bare metal

Home Assistant 2026.11 is scheduled to land today, and the line that made me put my coffee down is not the Matter camera support or the new automation exclusions. It is a small one: HACS, the community store I have leaned on for years, is becoming a built-in “Marketplace” under Settings. I have not updated yet, and I cannot verify the final release notes at the time of writing, so everything below is based on the beta coverage and the HACS team’s own preview documentation, linked at the end.

What is actually changing

According to simon42’s beta rundown, the Marketplace lives under Settings, existing HACS installs migrate automatically on first start, and a standalone HACS can no longer be installed on 2026.11. A fresh install of an integration no longer needs a restart, though updates still do. Peyanski’s write-up adds the details I care about: your existing downloads stay in place, repositories you added yourself and their update alerts should carry over, and old HACS links should open the new Marketplace page.

On paper that is a good change. Every new Home Assistant user eventually hits the moment where a forum answer says “just install it via HACS”, followed by a multi-step detour through GitHub tokens and a restart. Folding that into the product removes a real onboarding wall.

The part that makes me cautious

Convenience and trust are not the same thing. Once the store sits in the same settings menu as the official integrations, it will feel official. It is not. The same coverage points out that Marketplace content is community-made, that Home Assistant does not test, audit or support every item, and that community code can reach your Home Assistant data and system. A custom integration runs inside your instance with the same access as everything else. That was always true with HACS. The difference is that a menu entry carries an implicit “this is fine” that a separate install step never did.

I run Home Assistant OS on bare metal with a local-first rule: if something phones home or runs code I cannot read, it needs a good reason to exist. My habit with any custom integration is the boring one. I check who maintains it, when it last shipped a release, whether the issue tracker has real responses, and whether the code does what the README claims. The Marketplace does not change that checklist. It just makes skipping it easier.

The caveats I would read before updating

Two details deserve a closer look. First, AppDaemon apps and Python scripts that you downloaded through HACS stay where they are, but according to the preview documentation the Marketplace will no longer keep them updated. If you rely on any of those, you now own their update plan. Second, the browsing and installing flow for the main catalog reportedly does not require a GitHub sign-in, while adding a custom repository by its GitHub link does. If you add custom repositories, expect to connect GitHub.

There is also the other 2026.11 change that will bite at the same moment: entity naming. Entities are named by function with the device name prepended, entity IDs stay the same, and custom names migrate. Cards may display different names, and templates using friendly_name are being steered toward entity_name(), device_name() and area_name(). Custom cards installed from the community catalog are exactly where I would expect surprises, so those are worth checking first.

My update plan

I am not touching production on release day. My routine is the same one I used for the last few releases: take a full backup, write down every custom integration and card I run, skim the breaking changes list, then update a day or two later once the first patch release and the community thread have shaken out the obvious problems. For the Marketplace specifically I will note which repositories I added by hand, and confirm they still show up with update alerts after the migration rather than assuming they do.

I will also take this opportunity to audit what I have installed. If I cannot remember why a custom integration is on the box, it goes. A built-in store is a decent forcing function for a spring clean.

Is it a good change?

Overall, yes, with an asterisk. Lowering the barrier for newcomers is worth it, and having the project own the experience should mean fewer broken installs. The asterisk is on the project and the community: the clearer the “community-made, unaudited” label stays in the interface, the better this works out. I would rather see that warning stay boringly visible than quietly fade into the background once the Marketplace feels like part of the furniture.

I will report back after I have actually migrated, with what survived and what did not. If you update sooner than me, I would love to hear how your custom repositories fared.

Sources: simon42 on the 2026.11 beta, Peyanski on the Home Assistant Marketplace and HACS, and the official Home Assistant release notes, which I will check against once 2026.11 is published.

Leave a Reply

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