Home Assistant 2026.11 Moves HACS Into Core Settings as the Marketplace
The Home Assistant open-source smart home platform released version 2026.11 with a major restructuring of its community extensions. The long-standing community store HACS has moved directly into the system’s core under the name Marketplace. Developer Joakim Sørensen originally built HACS before handing it over to the Open Home Foundation, and a team led by Franck Nijhof has now embedded the store directly into the base user interface under Settings > Marketplace. The Marketplace is available across all installation types, including Docker containers.
Installing community extensions no longer requires external installation scripts, a mandatory GitHub account, or a server restart. The system now lets users download integrations, cards, and themes straight from the official catalog without linking a GitHub profile, which is only required when manually adding external repositories. Clicking install instantly opens a setup wizard for the chosen integration, and every addon receives its own update entity managed inside the central system updates overview. For existing users, the transition happens automatically on first boot, migrating current addons and repositories while retiring the standalone HACS installer.
Preparation Steps Before Updating to Version 2026.11
Several preparatory checks should be completed before applying the November update to avoid breaking changes. Users running Z-Wave JS must update their app to at least version 1.9.0, or update Z-Wave JS UI in Docker to version 11.24.2, or use server 3.11.0 or newer, because Home Assistant now requires zwave-js-server 3.11.0 or newer. Uptime Kuma integrations older than version 2.0.0 are no longer supported and must be updated beforehand. Users utilizing Telegram with the old platform syntax in YAML must switch to the Telegram bot integration and delete the legacy entry.
HACS is becoming an official Home Assistant marketplace, so I cleaned out integrations I'd forgotten abouthttps://t.co/rqH74qIQR0 pic.twitter.com/dTrgyd2cbL
Templates using the lookup integration_entities(‘hacs’) will no longer find any results after the update and must be replaced with integration_entities(‘marketplace’). AppDaemon apps and Python scripts installed from HACS will continue running but will no longer receive automated updates, requiring manual maintenance going forward. ZHA groups managed through the coordinator device now assign each group its own device, meaning users must reassign areas and point automations at the new group entities.
System Tip: Review your dashboards for unfamiliar entity names resulting from the platform’s new contextual naming architecture, and check Settings → System → Repairs for any post-update messages.
New Automation Controls and Hardware Integrations Added in November
Beyond the Marketplace integration, version 2026.11 introduces exclusion filtering for automation targets. Users can now target an entire room or zone while explicitly excluding specific devices, such as turning off an entire ground floor except for a single nightstand lamp. The update also adds contextual entity naming that automatically appends room and device context to eliminate cluttered dashboard names. The Matter standard expands to support cameras with two-way audio through built-in speakers, and the platform gains native LoRaWAN support for long-range wireless sensors without requiring external gateways.
Backups and media files can now be saved directly to attached physical storage drives, complementing 38 new integrations, live system logs, and a manual history deletion tool for erroneous measurement values. Users can find the complete list of changes and a commented changelog on the official Home Assistant developer blog.
Common Questions About the Marketplace Transition
What happens to existing HACS extensions during the update?
HACS transfers automatically on the first system start after updating to version 2026.11. All previously installed custom cards, themes, and repositories migrate into the new Marketplace without manual intervention, and the old HACS installer is permanently removed.
Do I still need a GitHub account to install community cards?
No, downloading items from the official Marketplace catalog no longer requires a GitHub account. A GitHub profile is only necessary if you manually add external repositories that are not part of the core catalog.
Why do my YAML sun or calendar triggers behave differently after the update?
Triggers using an offset without an explicit offset_type now rely on the sign to determine timing, where negative values fire before the event and positive values fire after. Users must flip the sign on those specific YAML triggers immediately after updating to maintain identical timing.
Where is the Marketplace located in the user interface?
The Marketplace is located under Settings > Marketplace in the main interface, completely replacing the former sidebar location used by the standalone HACS panel.
Home Assistant 2026.11! 🎉 HACS is now the built-in Marketplace 🛍️, exclude items from targets 🧠, a new way entities get their names 🏷️, LoRaWAN 📡, and 38 new integrations!https://t.co/yYuDtamgt1 pic.twitter.com/ZKkOlHl7bh
More on Home Assistant
Home Assistant 2026.11: HACS wird zum Marketplacehttps://t.co/S0x2AsMcWH