Smart Home Assistant

Home Assistant 2026.10: New Map, Trigger UI and What Breaks

SepehrBy Sepehr· 10 October 2026· Updated 10 October 2026· 3 min read
✓ Independent — no paid placements✓ UK-tested in real homes✓ Cited sources
World map on a table with coloured pins marking different locations

Key takeaways

  • Home Assistant 2026.10, released 7 October 2026, replaces the map with OpenStreetMap vector tiles fetched and cached through your own instance.
  • A new Triggered by condition lets you pick automation triggers from a list instead of typing trigger IDs.
  • The new AI page has an MCP card that enables the server in one click; new setups allow only administrator accounts.
  • Eight integrations were removed, including SolarEdge Local, Sigfox and Zestimate, and 15 new integrations were added.
  • mqtt.publish, mqtt.dump and Synology DSM reboot and shutdown now require an administrator account.
On this page[tap to expand]

Home Assistant 2026.10, released on 7 October 2026, replaces the map with OpenStreetMap vector tiles, lets you pick automation triggers without typing IDs, and adds one-click MCP setup for AI tools. It also removes eight integrations and brings more than 20 breaking changes, so read them before you update.

What is new in Home Assistant 2026.10?

The release is titled "You are here" and its headline act is a rebuilt map. After the previous map provider began requiring an API key on its tiles, Home Assistant moved to vector tiles from the OpenStreetMap Foundation, served through a new Map tiles integration that fetches and caches them via your own instance, so browsers no longer contact tile servers directly. There is a dark style, an automatic fallback to the classic map on devices that cannot render vector maps, and redesigned markers that show people's pictures and group anyone in the same zone into one bubble. A new Map dashboard overview has People, Devices and Zones tabs, and a zone editor sits on the map itself.

Elsewhere, the automation editor gains a Triggered by condition. You tick the triggers it should match instead of typing trigger IDs; triggers are numbered, missing ones are flagged and shared IDs get a one-click Fix. Existing YAML IDs keep working. The profile page is regrouped into Appearance, Localization, This browser and Security, and every user, not just admins, can now edit their own picture and name. For the pre-release view, see our 2026.10 beta preview.

Can Home Assistant 2026.10 connect to AI tools like Claude or ChatGPT?

Yes, with less fiddling than before. The page formerly called AI tasks is now simply AI, and it includes a Model Context Protocol card that switches on the MCP server and lists the URLs to copy into your AI client. New setups expose all entities and allow only administrator accounts, so check what you are sharing before pointing a cloud assistant at your home. Other small additions include a live pass/fail indicator on dashboard visibility conditions, a Modbus panel under Settings > Connectivity, a Use device name switch for entities, and timer actions and presets on tile cards.

Which integrations are new, and which are removed?

There are 15 new integrations, led by energy hardware: SolarEdge Modbus (Platinum at launch), Sunsynk, KACO Modbus, my-PV, Axle Energy and Zonneplan, plus Threema, INDI Allsky and Willow. Our guide to all 15 new integrations covers which run locally. Eight integrations were removed:

Removed integrationReason / replacement
Dublin BusAPI shut down in September 2020
EtherscanRelied on the retired V1 API; use the RESTful sensor with Etherscan V2
Melnor RainCloudDevice discontinued in April 2026
Orange and Rockland UtilityUse Opower instead
SigfoxRelied on the retired V1 backend API
SolarEdge LocalUse SolarEdge or SolarEdge Modbus
Travis-CItravis-ci.org API shut down in June 2021
ZestimateZillow retired the API it relied on

Linode and Tank Utility were also disabled because their libraries are unmaintained.

What breaks when you update to Home Assistant 2026.10?

Most homes will update cleanly, but several changes are easy to trip over. These are the ones most likely to matter:

  • Authentication: the legacy mode of the authentication provider is gone, and usernames are normalised to lowercase with no leading or trailing spaces. Expect a repair prompt if yours differed.
  • Admin-only actions: mqtt.publish, mqtt.dump and Synology DSM's reboot and shutdown now need an administrator account, so non-admin scripts will fail.
  • State conditions: combining for with a state attribute, a state list or another entity's state now fails validation.
  • Telegram bot: a directory_path for download_file must be listed in allowlist_external_dirs.
  • Mealie: needs server version 3.2 or newer.
  • Energy sensors: easyEnergy and EnergyZero sensors were renamed and lost their unit, OpenEVSE's charging status uses snake_case states, Proxmox VE uptime now reports a start timestamp, and Sofar lost six energy sensors on inverters without a meter.
  • UpCloud: the polling interval option was removed and it always polls every 60 seconds, so a 300-second interval becomes five times as many API calls.
  • Xbox: the Game Pass binary sensor was removed because it always reported false.

This is a selection; the full changelog lists the rest.

Should you update to 2026.10 now or wait?

Take a backup, then update if none of the breaking changes above touch your setup. If you run MQTT or Synology actions from non-admin users, or use easyEnergy, EnergyZero, OpenEVSE or Sofar sensors in dashboards and the Energy panel, check those first. Waiting for the first patch release is a reasonable choice for a production home. Also note that Home Assistant Cloud is being renamed Home Assistant Link, due in the December release, with the same service under a new name; see our explainer on the rename.

Buy the picks in this guide

Recommended for Home Automation

See all devices →

Frequently asked questions

When was Home Assistant 2026.10 released?
Home Assistant 2026.10 was released on 7 October 2026 and is titled "You are here", a nod to its rebuilt map. It follows the 2026.9 release from early September, in line with the project's monthly cadence, and is delivered as a normal update through Settings. Before pressing update, take a full backup, because the release removes eight integrations, disables Linode and Tank Utility and carries more than 20 breaking changes covering authentication, MQTT, Synology DSM, Telegram, energy sensors and more. If you only use common integrations you will probably be fine, but it is worth scanning the breaking changes list for the specific integrations you run before updating, since several sensors were renamed or lost units.
Does Home Assistant 2026.10 still need an API key for the map?
No. The previous map provider began requiring an API key on its tiles, so Home Assistant 2026.10 moved to vector tiles from the OpenStreetMap Foundation instead. A new Map tiles integration fetches and caches those tiles through your Home Assistant instance, which means your browser does not contact tile servers directly and you do not need to register for anything. The release adds a dark map style, redesigned markers showing people's pictures, and an automatic fallback to the classic map on devices that cannot render vector maps. The caveat is that your instance now does the fetching, so a Home Assistant install with no internet access will not load fresh tiles beyond whatever it has already cached.
Do I need to change anything in my automations for 2026.10?
Possibly, depending on what you use. Existing trigger IDs written in YAML keep working, so the new Triggered by condition is optional. However, state conditions that combine the for option with a state attribute, a state list or another entity's state now fail validation, so review any conditions of that shape. Actions such as mqtt.publish, mqtt.dump and Synology DSM reboot and shutdown now require an administrator account, which will break scripts triggered by non-admin users. Telegram downloads with a directory_path need that folder listed in allowlist_external_dirs. Check your configuration for the integrations named in the release notes, and read the repair prompts Home Assistant shows after the update, because it flags several of these issues automatically.

Sources

Sources verified 2026-10-10

  1. Home Assistant — 2026.10: You are here
  2. Home Assistant — Full changelog for Home Assistant 2026.10
›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