Home Assistant 2026.10 landed on October 7 under the title “You are here” — a fitting name for a release whose biggest change is a brand-new map. It has since received several patch releases (2026.10.1 through 2026.10.4), so it has had time to settle. If you’re newer to the platform, start with our complete guide to Home Assistant; this post assumes you already have a system running. For the previous release, see what actually shipped in 2026.8 and 2026.9.
A whole new map
The old map used pre-rendered images from a provider that began requiring an API key. 2026.10 replaces it with vector tiles from the OpenStreetMap Foundation. A new Map tiles integration fetches and caches the tiles through your own Home Assistant instance, so your browser doesn’t contact tile servers directly.
- Sharper at every zoom level, with a dedicated dark style. Older devices that can’t render vector maps fall back to the classic map.
- Recently viewed areas stay available during short internet outages.
- Redesigned markers: people appear with their picture in their own color, and people in the same zone share one bubble.
- A map overview with People, Devices and Zones tabs — beside the map on desktop, in a sheet on phones.
- A better zone editor that uses the new map, lists zones alphabetically and always puts Home first.
For households that use presence-based automations — lights on when you arrive, thermostat setbacks when everyone leaves — the zone editor and map improvements make those zones easier to set up accurately.
A “Triggered by” condition for automations
Until now, running different logic depending on which trigger fired meant typing trigger IDs by hand. The new Triggered by condition shows triggers by name, numbered by position, and Home Assistant creates and removes the IDs for you. Existing YAML trigger IDs keep working, and Home Assistant won’t add IDs to your YAML. The editor flags conditions that point at deleted triggers and warns about duplicate IDs, offering a one-click fix.
Automation editor rows also now show details such as thresholds, durations, sunrise and sunset offsets and wait timeouts, which makes a long automation far easier to read at a glance.
Cloud is becoming “Link”
Home Assistant Cloud is being renamed Home Assistant Link, planned for the December release. The service itself is unchanged. Behind the scenes, Nabu Casa moved its servers to bare metal and added more servers worldwide, and a new latency checker pings several servers at boot and picks the fastest connection — useful if you rely on remote access.
A tidier profile page and entity naming
The profile page is now an overview with sections for Appearance, Localization, This browser (or This mobile app) and Security. Nothing was removed. Every user, including non-admins, can now use an Edit profile button to change their picture and name, and the name also updates the linked person entity — handy for family members who just want their own face on the map.
There’s also a new Use device name switch that lets an entity take its device’s name, which helps keep naming consistent across a growing system.
AI and MCP in one place
The “AI tasks” page is now simply AI and includes a Model Context Protocol card. You can enable the MCP server with one click and copy the URLs for your AI app, and apps running their own MCP server are discovered automatically. Music search also improved, and the KNX integration gained AI tools for ETS project data, telegram history and bus values.
Smaller changes that add up
- Dashboards: visibility conditions now work like automation conditions (template, sun, zone, device), and each shows whether it currently passes. The home dashboard shows active security alerts.
- Tile cards gained a slider for select entities and timer actions with presets.
- Energy dashboard: separate battery discharge graphs.
- Matter: switches for leak sensor alarms and one-touch locking, plus frequency and power factor for power meters. If you’re choosing devices, our roundup of the best Zigbee and Z-Wave devices is a good companion.
- Philips Hue: MotionAware zone switches and an active scene sensor.
- UniFi Protect: key fob support and event entities.
- Z-Wave: three new automation conditions and improved triggers, plus an optional neighbors view on the network map.
- New binary sensor class for glass break, and fan modes can now be set by voice.
- Modbus panel under Settings > Connectivity, listing all connections and the integrations using them.
New integrations
Fifteen new integrations arrived, mostly on the energy side: local solar inverter data (SolarEdge Modbus, KACO Modbus, Sunsynk), smart meter gateways (Bitvis Power Hub, Theben Conexa), my-PV heating control, infrared control for Gree air conditioners and OSRAM lights, plus Threema messaging, Willow plant sensors and a Vitesy air purifier.
Removed integrations — check before you update
Eight integrations were removed because their services no longer exist: Dublin Bus, Etherscan, Melnor RainCloud, Orange and Rockland Utility, Sigfox, SolarEdge Local, Travis-CI and Zestimate. If you used SolarEdge Local, switch to the SolarEdge or SolarEdge Modbus integration; Orange and Rockland users can use Opower. As always, take a backup before updating.
Should you update?
For most homes, yes. 2026.10 is a quality-of-life release with no headline breaking changes beyond the removed integrations, and it’s already had four patch releases. Check the removed list above, take a backup, and update.
If you’d rather have a working system than a weekend project, we design and install Home Assistant systems for homeowners across New Jersey. See what smart home installation costs in New Jersey.
FAQ
When was Home Assistant 2026.10 released?
October 7, 2026, with patch releases 2026.10.1 through 2026.10.4 following in October.
Will the new map send my data to outside servers?
The new Map tiles integration fetches and caches tiles through your own Home Assistant instance, so your browser doesn’t contact tile servers directly.
Is Home Assistant Cloud going away?
No. It’s being renamed Home Assistant Link in the December release; the service is unchanged.
Do I need to change my automations?
No. Existing trigger IDs in YAML keep working. The new Triggered by condition is optional.