Smart Home

Home Assistant 2026.10: a private map, simpler automations, and breaking changes to check first

October’s Home Assistant release rebuilds the map so your browser no longer talks to tile servers, makes paired automations far easier, and adds one-click setup for AI assistants. It also carries more than 20 breaking changes, so back up before you press Update.

By OwnYourStack Admin · Published

Home Assistant logo
Home Assistant © Home Assistant / Open Home Foundation

Home Assistant 2026.10 arrived on 7 October 2026 under the title “You are here”, a nod to its headline feature. It was a record month for the project, with well over 2,000 merged pull requests, and also one with more backward-incompatible changes than usual.

A map that respects your privacy

The previous map provider started requiring an API key, so Home Assistant has moved to vector maps based on OpenStreetMap data. Roads and labels are now drawn on your device, so they stay sharp at any zoom level, and there is a proper dark mode. People in the same zone share a single marker with their photos instead of overlapping pins.

The part we like most is how the tiles are fetched: a new Map tiles integration downloads and caches them through your Home Assistant instance, so your browser or phone no longer contacts an external tile server directly. The trade-off is that an installation with no internet access will only show tiles it has already cached.

Paired automations without trigger IDs

Many homes have automations that come in pairs: one turns a light on when motion starts, another turns it off when it stops. Merging them meant setting up trigger IDs by hand, buried in each trigger’s menu. The new Triggered by condition lets you simply tick the triggers a branch should react to. Existing trigger IDs written in YAML keep working.

One-click MCP for AI assistants

Home Assistant can act as a Model Context Protocol (MCP) server, which lets AI tools read and control your home. Setting that up used to take several manual steps; there is now an MCP card under Settings, System where you enable the server and copy the connection details. A word of caution: new setups expose all of your entities to the AI tool (access is limited to administrator accounts), so decide carefully what you share before pointing a cloud AI service at your house.

Smaller things you will notice

  • The Home dashboard now shows the active alerts introduced on the Security dashboard last month, such as a door left open or a smoke alarm.
  • Every user can edit their own name and profile picture, and the profile page is reorganised into clear groups.
  • Password managers, including Firefox’s built-in one, can fill in the login page again.
  • The Energy dashboard shows the discharge of each battery separately.
  • There are 15 new integrations, many of them for solar and battery hardware.

Check these before updating

  • Eight integrations removed, including SolarEdge Local (use SolarEdge or the new SolarEdge Modbus), Sigfox and Zestimate.
  • Authentication: the legacy mode of the authentication provider is gone, and usernames are normalised to lowercase. Expect a repair prompt if yours differ.
  • Admin-only actions: MQTT publish and dump, and Synology DSM reboot and shutdown, now require an administrator account, so scripts run by non-admin users will fail.
  • State conditions that combine a duration with an attribute, a list of states or another entity’s state now fail validation.
  • Energy sensors from easyEnergy, EnergyZero, OpenEVSE and Sofar were renamed or changed, which can break Energy dashboard history.

Our advice: take a full backup, read the breaking changes for the integrations you actually use, and, if your home relies heavily on automations, consider waiting for the first patch release.

Sources

You might also like