Release update Ecosystems
Home Assistant 2026.10: what's new, what breaks
The October release is called "You are here", after its redesigned map, but the bigger change is in the automation editor. Trigger IDs, long tucked away in a menu, are now a tick box rather than something you invent and remember. The map builds on the vector tiles that quietly replaced last month's broken one, and the profile page, Modbus and the MCP server all get proper screens.
2026.10 Released 7 October 2026
Update, after one check The headline: trigger IDs move out of a hidden menu and into the Triggered by condition, where you tick the triggers you mean and Home Assistant handles the IDs itself.
Check first
UsernamesState conditions with a durationMQTT and DSM actions need an adminSofar inverters without a meterTeslemetry streaming vehiclesTelegram bot downloadsUniFi Network reconfiguration
Affected only if you use one of these. None in your setup? You're clear to update.
The headline feature: trigger IDs you can actually use
Plenty of setups have automations that come in pairs: one turns the hallway light on when motion starts, a second turns it off when motion stops. Home Assistant has been able to fold pairs like that into one automation for years. You gave each trigger an ID, then used a Triggered by condition to branch on which one fired. The catch was that the ID field sat in each trigger's menu, you had to make the IDs up, and then remember which belonged to which when you picked them in the condition. The release notes admit most people never found it.
In 2026.10 you add a Triggered by condition and tick the triggers it should match. The triggers are shown as themselves, numbered by their position in the list, with the same number beside each trigger so you can tell them apart. Home Assistant creates the IDs behind the scenes and removes them when you delete a trigger. The ID field is gone from the editor entirely, so to run the same actions for several triggers you tick them all in one condition.
If you write your own IDs in YAML, nothing changes: they keep working, several triggers can still share one, and Home Assistant won't add IDs to your files. The editor does flag a condition pointing at a trigger that no longer exists, and offers to split a shared ID into separate ones, which you can ignore if sharing is what you meant. Each trigger, condition and action row also now shows its key details without being opened, such as a threshold of "above 10 °C", a duration, or a sunrise offset.
Seven smaller wins
The changes most people will notice day to day. Scan the tags for the areas you use.
Maps
A redesigned map
In late August the map provider Home Assistant relied on started stamping "API key required" across its images, breaking every map at once, and 2026.9 quietly switched to vector tiles from the OpenStreetMap Foundation, fetched through your own instance by the Map tiles integration. 2026.10 builds on that. The map stays sharp at every zoom level and has a proper dark style, people show their picture, and everyone in the same zone shares one bubble. The map dashboard gains People, Devices and Zones tabs, and picking a person shows where they have been recently.
Profile
Everyone can edit their own profile
The profile page is now an overview with an account card at the top and the settings grouped below it. Any user, admin or not, can upload and crop a picture and change their name, and the name carries across to the linked person entity.
Dashboards
Card visibility gets the full set of conditions
The Visibility tab on a card now offers the same conditions as the automation editor, including sun, zone, device and template conditions, alongside the existing screen and user checks. It also shows whether the card is visible right now and which condition is holding it back. Existing visibility rules keep working.
Connectivity
A panel for Modbus
Last month's Connectivity regroup gave MQTT and serial devices their own pages, and 2026.10 adds Modbus. The panel lists every Modbus connection, serial or network gateway, including ones set up in YAML, with the devices on each and the integrations using them. Solar inverters and heat pumps are common Modbus devices, so this is where to look when one stops reporting.
AI
Connect an AI assistant in one click
Settings, System, AI tasks is renamed AI and gains a Model Context Protocol card. Turning the MCP server on is one click, and the card lists the addresses to copy into your assistant. New setups expose all your entities, including ones added later, and only accept administrator accounts. You can change both.
Dashboards
Timer buttons on the tile card
Tile cards gain two timer features: start, pause and cancel buttons, and presets that start a timer for a set length with one tap. The presets are edited from the timer's own dialog. Select and input select entities also get a slider feature on the tile.
Integrations
Hue zones, Matter leak sensors and LIFX over Thread
Philips Hue adds a switch for each MotionAware zone and a scene picker on rooms and zones that shows which scene is active. Matter can switch leak sensor alarms on and off, such as on the IKEA KLIPPBOK, and reports frequency and power factor on devices that measure power. LIFX lights connected over Thread are now supported.
Integrations: 15 in, 8 out
Removals matter more than additions, because a removal can break an automation or dashboard that references it. They're listed first, with what to do about each.
Removed in 2026.10 8 integrations
| Integration | Why | What to do |
|---|---|---|
| SolarEdge Local | Replaced | SolarEdge disabled the local web API in its inverter firmware from 2020 onwards. Use the SolarEdge integration for the cloud, or the new SolarEdge Modbus integration for a local connection. |
| Melnor RainCloud | Discontinued | Melnor discontinued the original RainCloud WiFi Timer in April 2026 and its cloud no longer responds. |
The other 6 removals, all long-discontinued hardware
Dublin BusEtherscanOrange and Rockland UtilitySigfoxTravis-CIZestimate
Added in 2026.10 15 integrations
Axle EnergyBitvis Power HubGree InfraredINDI AllskyKACO Modbusmy-PVOSRAM InfraredPersang InfraredSolarEdge ModbusSunsynkTheben Conexa Smart Meter GatewayThreemaVitesyWillowZonneplan
Breaking changes
7 this month, all narrow. If the summary at the top already cleared you, nothing below applies to your setup.
Breaking changes · check before you update Most setups are unaffected
Usernames
The deprecated legacy mode of Home Assistant's own login provider has been removed. Usernames are now always treated as lowercase with no spaces at either end.
What to do: If Home Assistant showed you a repair about usernames that aren't normalised, change those usernames to match.
State conditions with a duration
A state condition that combines the for option with an attribute, a list of states, or a state taken from another entity now fails validation. Those combinations never supported a duration, so instead of a condition that quietly doesn't do what you expect, you now get an error when the configuration is checked.
What to do: Find state conditions that use for with an attribute, a list of states or another entity's state, and remove the for or restructure the automation. The duration was never honoured anyway.
MQTT and DSM actions need an admin
mqtt.publish and mqtt.dump, and Synology DSM's reboot and shutdown actions, now need an administrator account when a non-admin user calls them, whether from a dashboard button, developer tools, or by starting a script or automation by hand. Those calls now fail with Unauthorized. This continues the permissions tidy-up that made installing updates admin-only in 2026.9. Automations running on their own triggers are unaffected.
What to do: Let an automation run on its own trigger, such as a helper changing state, rather than having a non-admin user start it.
Sofar inverters without a meter
Sofar inverters that report no energy meter lose six energy sensors: load consumption, import energy and export energy, each for today and in total. They never held real readings on those inverters. Hybrid inverters and PV inverters with a meter keep all six.
What to do: If you used any of them on your Energy dashboard, or in a template or automation, remove them.
Teslemetry streaming vehicles
Vehicles that stream their data no longer get the entities that could only be updated by polling, because updating those cost a paid API call.
What to do: Check dashboards and automations that used those entities for a vehicle that streams.
Telegram bot downloads
A directory_path passed to telegram_bot.download_file must now be listed in allowlist_external_dirs.
What to do: Add the directory to allowlist_external_dirs in your configuration. Leaving out directory_path saves to the default folder as before.
UniFi Network reconfiguration
Changing the settings of a configured UniFi Network integration now goes through its Reconfigure option.
What to do: Use Reconfigure on the existing entry rather than adding the integration a second time.
Should you update?
Our verdict Update, after one check
Update, but check two things. If Home Assistant has been showing you a repair about usernames, sort those out, because the legacy login mode is gone. If you write automations in YAML, look for state conditions that pair for with an attribute or a list of states, since those now fail validation. Sofar owners without an energy meter should also tidy six sensors off the Energy dashboard.
Beyond that it is a good release to take promptly. The trigger ID change makes a powerful feature usable for anyone who builds automations in the editor, and the map finally gets the redesign that September's switch to vector tiles made possible.
Source: home-assistant.io
Frequently asked questions
When was Home Assistant 2026.10 released?
On 7 October 2026, the first Wednesday of the month, which is Thursday 8 October in Australia.
Where did the trigger ID field go?
It has been removed from the automation editor. Add a Triggered by condition instead and tick the triggers it should match, and Home Assistant creates the IDs for you. IDs you wrote yourself in YAML keep working.
Why did my Home Assistant maps say API key required?
In late August the map provider Home Assistant used started stamping "API key required" across its map images. 2026.9 switched to vector tiles from the OpenStreetMap Foundation, so updating to 2026.9 or later fixes it. 2026.10 adds the redesigned markers and map overview on top.
Why does my automation now fail validation after updating?
Most likely it has a state condition that combines for with an attribute, a list of states, or a state from another entity. Those combinations never supported a duration, and 2026.10 rejects them when the configuration is checked. Remove the for, or restructure the automation.
Is Home Assistant Cloud being renamed?
Nabu Casa has announced that Home Assistant Cloud will become Home Assistant Link, with the same service under a new name. The change is planned for the December release, so nothing changes in 2026.10.
Something broke after an update?
Tell us what changed and what stopped working, and we'll help you get it back.
Get in touch