Home Assistant 2026.10 lands today, and I will say up front: I have not installed it. My update routine since the 2026.9 patch notes is to read first, wait for the first point release, and only then touch the production box. So this is a read-through of the release notes and beta coverage, not a field report. Field notes will follow once I have actually lived with it.
Still, a few things in this release say something about where Home Assistant is heading, and two of them touch the local-first philosophy this blog is built on.
The map stops phoning a third party
The headline feature is a redesigned Map dashboard. According to the beta write-up at Smart Home Assistant, it moves from third-party tile providers to OpenStreetMap vector tiles, so streets and labels stay sharp at any zoom level. There is a new overview tab showing people, devices and zones with activity history, and markers now use profile pictures for people and icons for zones. On mobile, details move into a pull-up sheet.
I have ignored the map for years, mostly because it was a grey rectangle with a dot on it. Whether the new one earns a place on my dashboard depends on something I can only judge after using it: how much of this is rendered locally, and what still gets fetched from outside when I open it. Vector tiles are a good sign for sharpness, but tiles still have to come from somewhere. I will check the network traffic when I update, and report back.
“Triggered by” is the quiet winner
If you have ever written an automation with several triggers and then a choose block that branches on trigger IDs, you know the chore: invent an ID, type it in the trigger, type it again in the condition, and hope the two spellings still match three months later. The new “Triggered by” condition lets you pick the trigger directly, without managing IDs by hand. Per Smart Home Centre’s summary, existing YAML keeps working, so nothing forces a rewrite.
It is not glamorous, but it removes a classic source of silent breakage, and I expect it to shorten a few of my longer automations. Dashboard cards also gain broader visibility conditions (template, sun, zone and device on top of screen and user), which should help with the kind of “only show this when it matters” dashboard I wrote about after 2026.9.
An MCP server, one click away
There is now a dedicated AI settings page that exposes a Model Context Protocol server with a shareable URL, so tools like Claude or ChatGPT can talk to your Home Assistant. It is optional, and I understand why people want it. But my honest take is simple: a URL that lets an external assistant read and control my house is exactly the kind of thing I want to think about before enabling, not after. If you do turn it on, look carefully at which entities are exposed and who can reach that URL. I will not be enabling it on the production instance until I have read the access model properly.
Small things worth knowing
Matter leak sensors get separate switches for audible and visual alarms, which is a thoughtful detail: loud next to the washing machine, notification-only under the bedroom-adjacent sink. Smart plugs and energy monitors can report mains frequency and power factor. Household members can edit their own profile picture and name without an admin. Active alerts show on the Home dashboard, and there are separate energy readings for home battery discharge. Fifteen new integrations arrive and eight are removed because their services were discontinued.
Read the breaking changes before you click update
This is the part that matters most for an update day. The beta coverage lists legacy authentication being removed, with usernames normalized to lowercase without spaces. If you have an old account with a capital letter or a space in the name, check that before you update, not after you are locked out. Telegram bot users need to allowlist download directories, Sofar inverters without energy meters lose six energy sensors, and UniFi Network cannot be reconfigured by re-adding it. The official release notes carry the authoritative table; treat the list above as a pointer, not a substitute.
What I will do
Take a full backup, read the breaking-changes table against my actual integrations, wait for 2026.10.1, and then update. After that I will test the map with the network tab open and decide whether it earns a spot. If the traffic looks clean, expect a follow-up with screenshots. If not, expect that too.
Sources: details above come from the beta coverage linked inline; I have not yet verified them against the final release post.
Leave a Reply