Smart Home Assistant

Home Assistant 2026.11 Beta: Marketplace, Exclude Targets and Entity Names

SepehrBy Sepehr· 28 October 2026· Updated 28 October 2026· 4 min read
✓ Independent — no paid placements✓ UK-tested in real homes✓ Cited sources
Smart thermostat mounted on a concrete wall beside a window in a naturally lit room

Key takeaways

  • Home Assistant 2026.11 beta replaces HACS with a built-in Marketplace, and existing HACS installs migrate automatically without needing a restart to install.
  • Entity names now combine device and entity, so templates using friendly_name should move to entity_name(), device_name() or area_name().
  • The beta adds 38 new integrations, including Bosch Smart Camera, LoRaWAN, ChirpStack and Philips Infrared.
  • Z-Wave now needs zwave-js-server 3.11.0 or later, and ZHA group entities move to their own group devices.
  • Wait for the stable release, which the notes point to as 4 November 2026, unless you have a spare test instance.
On this page[tap to expand]

Home Assistant 2026.11 beta turns HACS into a built-in Marketplace, adds exclude targets for automations and rebuilds entity names from the device and entity together. The stable release is expected on 4 November 2026, so use this beta guide to check the breaking changes first.

What is new in the Home Assistant 2026.11 beta?

The 2026.11 beta release notes lead with the Marketplace (Settings > Marketplace), which folds HACS into core for community integrations, cards, themes and templates. Installs no longer need a restart, and existing HACS installs migrate automatically. Our Marketplace migration guide covers what to check by hand.

For automation builders, exclude targets let an automation or script skip specific entities, devices, areas, floors or labels within a wider target. Dashboard sections such as Common controls, Device and Entities now fill themselves as devices are added, and forms and blueprint inputs can show fields only when relevant.

Debugging gets a "Triggered by" activity filter, links between script traces, per-integration live logs, statistics deletion by time range and an Action history tab. Matter 1.5 cameras and a Labs preview of two-way audio for Matter and Reolink cameras arrive, plus LoRaWAN support (ChirpStack, The Things Network, SenseCAP) and Zigbee Green Power for batteryless switches. The LLM API can read system logs, and the MCP server can be limited to read-only tools.

Which new integrations arrive in 2026.11?

There are 38 new integrations, including Bosch Smart Camera, ChirpStack, Flic Button, HP Printer, LoRaWAN, Nature Remo, Philips Infrared, Seafile, SenseCAP, SilverCrest Infrared, The Things Network, Škoda, Spin EV Charger and Xiaomi Weather. Infrared and radio-frequency support also widens across Shelly, LG, Gree and Alpha Bidet. Bitcoin, Keyboard Remote, OpenWrt (ubus) and Sky Hub gain UI setup, and Flipr is cut back to a minimal stub because its company was liquidated. Quality-scale movers: 17 platinum, 2 gold, 6 silver and 4 bronze.

For the full list of what each new integration does, see the notes; most are niche, and the Marketplace is the story for UK users.

Which breaking changes should you check before updating?

The entity naming change touches the most setups, so read it first, then scan the table for integrations you run.

IntegrationWhat changes and what to do
Entity namesNames combine entity and device, e.g. "Thermostat Temperature"; entity IDs are unchanged and old names remain voice aliases. Switch templates from friendly_name to entity_name(), device_name() or area_name(), and update custom cards.
AuthNon-local logins fail with "Invalid client id" if the browser address differs from the scheme, host and port Home Assistant sees. Add your proxy to trusted proxies or use a domain name.
Calendar and SunYAML triggers without offset_type now treat a negative offset as before and positive as after. Flip signs where needed; UI triggers are unaffected.
Honeywell Evohomeevohome.reset_system, evohome.clear_zone_override and the Reset preset are removed. Use the Reset buttons, and include the controller's climate entity in set_system_mode.
HiveCustom polling intervals are no longer supported and are ignored.
Philips HueThe "None" effect is removed; change it to "off".
MQTTEntities without a unique_id no longer create devices from their device config. Add a unique_id.
MatterConcentration sensors use the device's unit (189 ppb now shows 0.189 ppm); climate.turn_on resumes the last non-off mode; tilt-only covers use cover.*_cover_tilt actions.
TuyaMulti-channel devices move channel entities to child devices, changing names. Update templates and dashboards.
Z-WaveNeeds zwave-js-server 3.11.0+ (Z-Wave JS app 1.9.0+ or Z-Wave JS UI v11.24.2+); multi-endpoint devices gain child devices.
Zigbee Home AutomationGroup entities move to their own group devices. Target the group entities or devices, and set areas on the new devices.
TelegramLegacy notify platform removed. Use the Telegram bot notify entities or telegram_bot actions.
RingThe siren switch is removed; use the siren entity.
NanoleafTouch gesture device triggers removed; use the Touch gesture event entity with an event.received trigger.
Python dependenciesCore no longer installs packages into deps outside a virtual environment. Run Core in a virtual environment and delete deps.

Smaller items: Control4 polls every 5 seconds regardless of settings, Electra Smart and Matter climate turn_on now resume the last mode, DoorBird events use the image entity as entity_id, and Xiaomi Home light, switch and fan actions need a target. Apple iCloud stops fetching completed reminders by default. See our template guide for rewriting name lookups.

Why does this matter for UK Home Assistant users?

The Marketplace and the naming change matter most. Anyone running HACS will be moved automatically, but YAML resources and AppDaemon need a manual check. UK heating setups should look at Hive and Evohome: Hive polling becomes fixed, and Evohome users must replace removed reset actions, as covered in our Evohome review. Z-Wave, Zigbee and MQTT owners have concrete migration steps; see the Z-Wave guide and MQTT guide. Matter users can read our Matter devices guide.

Should you install the 2026.11 beta or wait?

Wait for stable unless you run a spare test instance. The release notes warn that features may change before the final release, and the naming, Z-Wave and ZHA changes can rename or restructure devices. The notes invite readers to a release party livestream on 4 November 2026, which points to that date for the stable release. Take a full backup first with our backup and restore guide, and compare the table above with your integrations. The previous release is covered in our 2026.10 release guide.

Buy the picks in this guide

Recommended for Home Automation

See all devices →

Frequently asked questions

When is Home Assistant 2026.11 released?
The beta notes do not state an exact stable date, but they invite readers to a release party livestream on 4 November 2026, which is a Wednesday and fits the usual first-Wednesday-of-the-month cadence, so that is the date to expect. The beta was published on 28 October 2026, and the notes warn that features may still change before the final release. Treat the date as the likely target rather than a guarantee, and check the official release notes on the day. If you want to test early, use a spare instance or a restored backup rather than your live home, because the entity naming change and the Z-Wave and ZHA device changes can rename or restructure devices.
Will the Home Assistant Marketplace break my HACS setup?
Home Assistant says existing HACS installs migrate to the Marketplace automatically, and installing community items no longer needs a restart. Even so, the migration touches how community integrations, cards, themes and templates are managed, so take a full backup before updating and open Settings > Marketplace afterwards to confirm everything arrived. Our Marketplace migration guide covers the items that need a manual look, such as YAML resources and AppDaemon. The caveat is that this is beta behaviour: details may change before stable, so if your dashboards depend heavily on custom cards, wait for the stable release and read community reports before updating.
Do the 2026.11 entity name changes break automations?
Entity IDs are unchanged, so automations that reference entities by ID keep working. What changes is the displayed name, now built from the device and entity, such as Thermostat Temperature, and the old names remain as aliases for voice assistants. Templates that read friendly_name can return different text, so switch them to entity_name(), device_name() or area_name(). Unnamed dashboard cards will show the device name plus entity name, and custom cards should be updated first. If a name looks wrong, rename the device, turn on Main entity of the device, or set a name on the card. Notifications that quote names are the most likely place to notice a change.

Sources

Sources verified 2026-10-28

  1. Home Assistant — 2026.11 Beta release notes
›How we researched this

Claims in this article are checked against primary sources — manufacturer specifications, official documentation, Which? research, Ofgem guidance, or gov.uk — rather than forum threads or video reviews. Where the author has direct hands-on experience with a product (most Home Assistant, Zigbee, and home-networking gear is running in his own homelab), that is stated explicitly in the text.

For categories outside that personal setup — such as boilers, heat pumps, and other areas that are traditionally a heating engineer's domain — verdicts are built from cross-referenced manufacturer data, published lab results, and vetted expert and owner reviews rather than a claim of personal hands-on testing. See the editorial policy for the full methodology.

Sepehr

Written by

Sepehr

10+ years hands-on with Home Assistant & networking · Research-backed elsewhere · No brand deals

Smart home specialist with 10+ years running a self-hosted Home Assistant setup — Zigbee2MQTT, Frigate NVR, and local-first automations. Independent coverage for UK homes, no brand deals.

LinkedIn →

Citing this page? Please use a dofollow link back to the original article — it helps us keep the data on this page accurate and up to date.

Related reading