Home Assistant, the open-source smart home platform that runs on everything from a Raspberry Pi to a dedicated mini PC, has rolled out its October release. Home Assistant 2026.10, published on October 7 with a follow-up patch (2026.10.1) on October 10, is one of those updates where almost every change is something you’ll actually feel in daily use: a rebuilt map, automations that no longer demand you memorize IDs, and a one-click way to plug your entire home into an AI agent.
With Apple’s smart home hub event just around the corner, this release also quietly stakes out the opposite position in the smart home market: fully local, open, and yours.
A Whole New Map, Drawn on Your Device
The most visible change in 2026.10 is the map. In the previous release, every map in Home Assistant broke overnight when the project’s map provider began requiring an API key. Rather than chase another tile provider, the team moved to vector tiles served by the OpenStreetMap Foundation. The new Map tiles integration fetches and caches tiles through your Home Assistant instance, so your browser no longer contacts external tile servers directly.
The practical difference is immediate. The map is now drawn as vectors on your device, so streets and labels stay sharp at every zoom level, and zooming in and out is smooth. There is a dedicated dark style for dark mode, and older devices that can’t render vector maps fall back to the classic view.
Markers were redesigned too. People appear with their profile pictures, zones get a marker with their own icon and color, and everyone in the same zone shares a single bubble instead of a pile of stacked markers. Zoom out far enough and overlapping bubbles merge into one.
The Map dashboard now includes an overview panel with three tabs: People, Devices, and Zones. Select a person to see recent activity with each stop colored by zone, or select a zone to see who’s there. On phones, the map fills the whole screen edge to edge.
Automations Without the Memory Test
Home Assistant has long had a powerful feature almost nobody found: trigger IDs. Give each trigger in an automation an ID, and a single automation can replace two, three, or five — one to turn the hallway light on when motion is detected, another to turn it off when the motion clears. But the ID field was buried in a menu, you had to invent the IDs yourself, and then remember which was which.
That changes in 2026.10. Add a Triggered by condition and you simply check the triggers it should match. You see the triggers themselves — numbered by their position in the list — rather than IDs you made up. Home Assistant handles the IDs behind the scenes and cleans up after itself when you remove a trigger. If you wrote your own trigger IDs in YAML, nothing changes; they keep working exactly as before.
Related quality-of-life touches: each trigger, condition, and action row in the automation editor now shows its key details at a glance — the threshold a trigger checks, how long something must stay that way, or the offset on a sunrise trigger — instead of hiding them until you open the row. Dashboard cards also gained more powerful visibility conditions, so you can show a card only when it actually matters.
Connect Your AI in One Click
The headline move for the AI era: Home Assistant 2026.10 makes the Model Context Protocol (MCP) server a one-click setup from a new AI settings page. MCP lets AI models like Claude or ChatGPT talk to your local devices, and with this update Home Assistant can expose its integrations to any agent you choose. The endpoint sits at /api/mcp, authenticated with your existing access tokens or OAuth — local, fast, and free.
That’s a notable contrast with the big platform assistants racing toward conversational AI: instead of buying new hardware or a subscription, an existing Home Assistant user turns their already-running system into a context source for whichever AI they trust. The release also improves the LLM tooling for developers, with tools now declaring which integration provides them and annotations describing whether a tool reads only, writes, is destructive, or reaches outside Home Assistant — guardrails that matter when an agent can flip switches in your home.
Cloud Becomes Link, Matter Gets Smarter
Two naming and protocol notes worth knowing. First, Home Assistant Cloud — Nabu Casa’s remote-access service — is being renamed Home Assistant Link, with the change planned for the December release. Same service, new name; Nabu Casa says it’s about being clearer that its service, unlike much of Big Tech’s cloud, never locked users in or harvested their data. The team has also been speeding up remote access, migrating servers to bare metal and adding a latency checker that picks the best connection.
Second, the Matter integration gains more device controls. Switches can now turn the visual and audible alarms of supported leak sensors on or off — the IKEA KLIPPBOK is named as an example — and there’s a switch for one-touch locking, so you decide whether a single touch on your lock’s keypad is enough to lock the door. Devices measuring electrical power now also report frequency and power factor.
15 New Integrations, Many Improvements
Fifteen new integrations arrive in this release, with a clear tilt toward energy and local control:
- SolarEdge Modbus connects to your SolarEdge inverter over your own network — no account, no API key, no cloud. Readings arrive every few seconds instead of every few minutes, keep arriving when the internet is down, and you can adjust export limits and battery charging.
- KACO Modbus brings another solar inverter brand fully local over Modbus TCP, while Bitvis Power Hub and the Theben Conexa smart meter gateway read electricity data straight from your meter over the local network.
- Gree Infrared and OSRAM Infrared control air conditioners and RGB lights through an infrared transmitter you already have set up, with the entity following along when someone uses the physical remote.
- Threema lets automations send end-to-end encrypted messages without needing a phone number.
Existing integrations improve too: HomeKit Bridge can now show valve entities in the Home app as faucets, shower heads, or sprinklers; Roborock vacuums update in real time; Reolink can control pan-and-tilt lenses on multi-lens cameras; Hue gains a MotionAware zone switch and scene selects; and Z-Wave gets properly filled-in automation editor fields for device status, parameters, and values.
Should You Update?
Monthly Home Assistant updates are generally safe to adopt, and 2026.10.1 (October 10) already includes the first round of fixes. Nothing here is a breaking change in the classic sense, though a handful of dead integrations were removed — Dublin Bus, Etherscan, Melnor RainCloud, Sigfox, SolarEdge Local, Travis-CI, and Zestimate — so check your YAML if you still had any of those configured.
The bigger picture: 2026.10 is a statement release. The rebuilt map fixes a real breakage the hard way and comes out better. The automation editor keeps bending toward people who never want to touch YAML. And the one-click MCP server turns Home Assistant into arguably the most agent-ready smart home platform you can run on your own hardware — one week before Apple’s big smart home event tries to convince you that the future of the connected home arrives in a box from Cupertino.
Home Assistant 2026.10 is available now through Settings > System > Updates. The Home Assistant Link rename follows in December.