Home Assistant updates usually bring a handful of useful improvements, but the November 2026 release is a much bigger moment for the smart-home platform. Version 2026.11 brings the community’s HACS experience directly into Home Assistant as the new Marketplace, adds support for Matter cameras, introduces two-way camera audio, and makes a series of changes to automations, device organisation, energy monitoring and AI-assisted troubleshooting.
For anyone running Home Assistant at home, this is more than a routine update. It changes how you discover community projects, how some entities are named, and what you can do with supported cameras and connected devices. There are also a few things to check before upgrading, especially if you rely on custom integrations or dashboards.
Here is a practical look at everything new in Home Assistant 2026.11, based on the release published on 4 November and the 2026.11.1 patch released on 9 November 2026. This article reflects the status as of 12 November 2026.

Home Assistant 2026.11 at a glance
The Home Assistant team described 2026.11 as its biggest release so far. The headline changes include:
- HACS becomes the built-in Marketplace, available from Settings.
- Support for Matter 1.5 cameras, including live video and snapshots.
- A Labs preview of two-way audio for supported cameras.
- New LoRaWAN support and better visibility of connected networks and devices.
- Zigbee Green Power support for batteryless switches and sensors.
- More flexible automation targets, including the ability to exclude selected entities or areas.
- A redesigned entity-naming approach, with important compatibility implications.
- Improvements to dashboards, energy monitoring, backups, MQTT devices and AI troubleshooting.
- 38 new integrations and many improvements to existing integrations.
Let’s look at what these changes mean in everyday use.
1. HACS is now built into Home Assistant as Marketplace
This is arguably the biggest change in 2026.11. For years, Home Assistant users have relied on HACS—the Home Assistant Community Store—to discover custom integrations, dashboard cards, themes and other community projects. It was powerful, but new users had to install and maintain it separately.
With 2026.11, that experience moves into Home Assistant itself. Open Settings → Marketplace to browse community integrations, dashboard cards, themes and templates. There is no separate HACS installation step, and you do not need a GitHub account just to install or update projects.
If you already use HACS, the migration is designed to happen automatically when Home Assistant starts after the update. Your installed projects, custom repositories and update entities are carried over. Existing links and bookmarks that point to HACS should open the new Marketplace.
The Marketplace also adds useful browsing features. You can group projects by status, type or source; filter community projects separately from custom repositories; uninstall multiple repositories together; and share a Marketplace view because search, filters and sorting are reflected in the URL.
Important security note: Marketplace projects are community-made. They are not reviewed, tested or supported by the Home Assistant core team, and custom code runs inside your Home Assistant environment. Install only projects and repositories you trust. The new Marketplace makes discovery easier, but it does not remove the need to assess the risks.
The old standalone HACS installer stops at Home Assistant 2026.11. The Marketplace is now included with Home Assistant updates, so a separate HACS installation is no longer the route for this version.
2. Matter 1.5 camera support arrives
Matter has been expanding beyond its early focus on common smart-home devices. Home Assistant 2026.11 adds support for cameras defined by Matter 1.5, bringing another device category into the standard.
A supported Matter camera can appear as a camera entity in Home Assistant, with live video and snapshots. The live stream uses WebRTC, allowing video to travel directly between the browser and camera. The camera entity also reflects the camera’s state, including whether privacy mode is enabled.
There is a requirement to keep in mind: the Matter server connected to Home Assistant must be new enough to support cameras. If your Matter server is older, Home Assistant may not discover the camera until that part of the setup is updated.
3. Two-way audio: talk through supported cameras
Home Assistant is also giving cameras a voice. The new Two-way audio feature is available as a Labs preview. Once enabled under Settings → System → Labs, a talk button can appear in the live camera view for supported devices.
At launch, support includes Matter cameras and Reolink cameras whose integration supports the feature. For Reolink, the camera needs to use RTSP; RTMP and FLV streams cannot carry audio back to the camera in this implementation.
There is also a browser security requirement. Microphone access is allowed only over a secure connection, so two-way audio currently requires opening Home Assistant through HTTPS. The team says it is working on support for the Home Assistant apps over HTTP as well.
Because this is a Labs preview, expect the feature to evolve. Check your camera model, stream configuration and browser connection before relying on it as an everyday intercom.
4. LoRaWAN support expands the smart-home network
LoRaWAN is designed for low-power, long-range communication. It is useful for devices that send small amounts of information over a wide area, such as outdoor sensors, agricultural monitoring equipment and remote environmental devices.
Home Assistant 2026.11 adds a LoRaWAN integration that can bring devices from supported LoRaWAN networks into the platform. The interface includes network connections, devices and a map view to help users understand how gateways and devices are connected.
This is particularly interesting for larger properties, gardens, farms and monitoring projects where Wi-Fi coverage is not practical. Actual range and compatibility still depend on gateways, radio conditions, regional frequency rules and the network service you use.
5. Zigbee Green Power brings batteryless switches
Another useful addition is support for Zigbee Green Power in Zigbee Home Automation (ZHA). Green Power devices are designed to operate without a conventional battery. Some switches generate energy from the press itself, while certain sensors can harvest energy from their surroundings.
Friends of Hue switches are a familiar example of this approach. These devices behave differently from ordinary Zigbee devices, so Home Assistant now displays their network information accordingly. For example, a Green Power device can show its Source ID and does not have the same parent-device relationship as a typical Zigbee node.
For smart-home builders, this could mean fewer batteries to replace and more flexibility when adding a wall switch or sensor where running power is inconvenient. You will still need compatible hardware and a Zigbee coordinator and network that support the device.
6. Automations can now exclude targets
Small automation improvements can make a surprisingly big difference. Home Assistant 2026.11 lets you exclude specific items from an automation target.
Imagine an automation that turns off every light downstairs when you leave home, but you want the kitchen light to stay on. You can target the downstairs lights and exclude the kitchen. The useful part is that the exclusion can apply to the area, not just a fixed list of current devices. If you add another light to the kitchen later, it can remain excluded too.
This makes broad automations easier to maintain. You do not have to keep rebuilding a list every time a new device is added to a room or area.
7. Entity naming gets a major rethink
Home Assistant has changed how entity names are handled. The goal is to let users name a device or function once, while Home Assistant adds context where it helps. This should make names more consistent and easier to understand across a large installation.
However, this is one of the release’s most important breaking changes. Some entity IDs and names may look different after upgrading. Dashboards, templates, scripts, automations, MQTT configurations and external systems that refer to entity IDs directly may need attention.
Before upgrading, review the entity-naming migration notes and make a backup. After the update, check critical automations and any YAML that refers to entities by ID. Do not assume every old reference will continue to work unchanged.
8. Dashboards get more flexible sections
The dashboard editor receives improvements around custom section strategies. This gives dashboard builders more flexibility in how sections are arranged and populated. The aim is to make dashboards easier to maintain as devices and entities change, rather than forcing users to manually reorganise every view.
For users who like building detailed dashboards for energy, climate, security or room controls, these changes are worth exploring in a test view first. Existing dashboards should be checked after the entity-naming changes, especially if cards use manually entered entity IDs.
9. Energy dashboard improvements
Home Assistant’s Energy dashboard is especially useful when you have solar panels, a battery, grid consumption or smart plugs reporting energy data. Version 2026.11 adds the option to show your home’s total consumption in the Energy dashboard.
The legends in the power and device graphs also show the current value for each source. That makes it easier to see what is happening right now without relying only on the shape of a graph.
If you monitor solar generation, grid import, battery charge and discharge, or individual appliances, these improvements make the dashboard more informative. The quality of the results still depends on accurate energy sensors, correct units and reliable source data.
10. MQTT devices can now have child devices
Home Assistant’s MQTT device support has gained the ability to represent child devices. This is helpful when one physical product contains several separate components or when a parent device reports information about multiple parts.
Instead of presenting everything as one flat device, the device page can show a clearer parent-and-child structure. The MQTT entity editor also gains a unit-of-measurement picker, which helps avoid mistakes when defining sensor entities.
This is a useful improvement for DIY smart-home projects, ESPHome and MQTT-based sensors, custom gateways and multi-part devices.
11. AI assistants can help troubleshoot Home Assistant
Home Assistant continues to expand its Large Language Model (LLM) API. Compatible AI assistants can use tools to search for devices and automations, review logs and look up historical statistics. The 2026.11 release adds more ways for an assistant to inspect system information, search available actions and call actions through the Home Assistant LLM API.
In practical terms, this can make troubleshooting more conversational. Instead of manually searching through every page, you could ask a connected assistant to find a device, inspect relevant information or help identify why an automation did not run.
Access needs to be configured carefully. Some information, such as logs, requires administrator-level access. Only expose the entities and actions an AI assistant genuinely needs, and be especially cautious about granting permission to unlock doors, disable alarms, change security settings or control critical equipment.
12. Backups and system management improvements
The release also includes improvements to the backup experience, including support for backup storage on local drives and the ability for backup agents to be renamed. These changes make it easier to organise backup destinations and understand where backups are being handled.
A backup is only useful if it can be restored. After changing backup settings, check that a backup completes successfully and that you know where the files are stored. For important installations, keep an additional copy away from the Home Assistant host.
13. Thirty-eight new integrations and many improvements
Home Assistant 2026.11 adds 38 new integrations, along with updates to existing ones. Some notable additions and improvements include:
- A Better Routeplanner: Bring electric-vehicle information such as state of charge, range, battery temperature, odometer and charging state into Home Assistant.
- aerosmart: Monitor supported ventilation and heat-pump systems over Modbus, including TCP gateway or serial connections.
- Alpha Bidet Infrared: Adds integration support for compatible bidet devices.
- Midea: Expanded support for washing machines, dryers, refrigerators, water heaters, air purifiers and dehumidifiers.
- GoodWe: Adds a battery charge current limit control for supported inverter systems.
- OpenEVSE: Adds an EV charging status binary sensor and manual override functionality.
- Google AI and Gemini: Improvements to speech, text-to-speech options and model support.
Integration support varies by model and region. Check the official integration documentation before buying hardware specifically for Home Assistant.
14. Accessibility, security and developer improvements
Not every important change is a headline feature. Home Assistant 2026.11 also includes improvements to accessibility, configuration and developer tools. Data tables can be operated with a keyboard and read by screen readers, and icon-only controls receive clearer accessible names.
The HTTP integration adds TLS profile selection, with an updated default intended to work with modern browsers, apps and devices. Authentication providers also change how they opt in to multi-factor authentication. Developers get new lifecycle hooks, integration categories, improved configuration flows and other internal changes.
These changes may not be immediately visible on a dashboard, but they help make the platform more maintainable and accessible over time.
Home Assistant 2026.11.1: the first November patch
The initial 2026.11 release was followed by 2026.11.1 on 9 November 2026. This is a bug-fix patch rather than a separate feature release. The published fixes include updates to several integrations and libraries, fixes for HomeKit camera motion events, restored Shelly RPC devices, and other compatibility and reliability improvements.
If you are updating now, check the latest patch available for your installation rather than stopping at 2026.11.0. Review the release notes for each patch before applying it, particularly if your setup depends on a specific camera, network integration or custom component.
What should you check before upgrading?
With a release this large, a little preparation can save a lot of troubleshooting. Before installing Home Assistant 2026.11, follow this checklist:
- Create a full backup: Make sure you have a recent backup and know how to restore it.
- Read the breaking changes: Pay particular attention to entity naming and any integration changes that affect your setup.
- Check custom integrations: Review Marketplace/HACS projects and confirm that critical components are compatible.
- Review automations and scripts: Look for hard-coded entity IDs, templates and external references.
- Check camera requirements: Update your Matter server if you plan to use Matter cameras, and confirm RTSP/HTTPS requirements for two-way audio.
- Verify energy sensors: Confirm units, device classes and state classes before relying on the updated Energy dashboard.
- Test critical functions: Check door locks, alarms, heating, cooling, cameras and safety-related automations after the update.
- Update in a maintenance window: Avoid upgrading just before travel or when you need the smart home to work without interruption.
Is Home Assistant 2026.11 worth installing?
For most users, yes—after taking a backup and checking the breaking changes. The built-in Marketplace removes a long-standing installation hurdle, Matter camera support expands the platform, and the improvements to automations, energy monitoring and device organisation are genuinely useful.
However, this is not an update to rush into blindly. The entity-naming changes deserve particular attention, and community projects in the Marketplace still need the same caution as custom integrations installed through HACS in the past. Two-way audio is also a Labs preview, not a universal feature for every camera.
Final thoughts
Home Assistant 2026.11 is a substantial step forward. Bringing HACS into the built-in Marketplace makes community development easier to discover, while Matter cameras, two-way audio, LoRaWAN and Zigbee Green Power broaden the kinds of devices that can become part of a connected home.
The quieter improvements may matter just as much: better automation targeting, clearer device structures, more useful energy information, improved backups and AI-assisted troubleshooting. Together, they make Home Assistant more capable without changing its central idea—your smart home should remain under your control.
If you are already running Home Assistant, make a backup, read the entity migration notes and plan your upgrade. If you are new to the platform, 2026.11 makes it easier than ever to explore the community ecosystem and build a smart home that works the way you want.
Frequently asked questions
When was Home Assistant 2026.11 released?
Home Assistant 2026.11 was released on 4 November 2026. The first patch, 2026.11.1, followed on 9 November 2026.
What happened to HACS in Home Assistant 2026.11?
HACS has been brought into Home Assistant as the built-in Marketplace under Settings. Existing HACS users are migrated automatically when Home Assistant starts after the update, with installed projects and repositories carried over.
Does Home Assistant 2026.11 support Matter cameras?
Yes. It supports Matter 1.5 cameras with live video and snapshots, provided the connected Matter server is recent enough to support cameras.
Can I talk through a Reolink camera in Home Assistant?
Two-way audio is available as a Labs preview for supported Matter cameras and Reolink cameras. For Reolink, the camera must use RTSP, and the browser connection to Home Assistant must use HTTPS for microphone access.
Is Home Assistant 2026.11 safe to update?
The release is intended for supported Home Assistant installations, but users should back up first and review breaking changes. Entity naming, custom integrations and critical automations deserve extra attention.
Does Home Assistant 2026.11 include AI features?
It expands the Home Assistant LLM API so compatible assistants can search devices and actions, inspect system information and logs, and help troubleshoot. Access and permissions must be configured carefully.