Home Assistant 2026.11.0 upgrade: 44 breaking changes to check

released
lab run
upgraded from
2026.10.4
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

Home Assistant 2026.11 has 38 new integrations and 5,827 pull requests from 557 people. The GitHub release text only links to the blog post. The points below come from that post (reported, not tested by us).

  • HACS is built in, under Settings > Marketplace.
  • You can exclude entities, devices, areas, floors and labels from a target.
  • Dashboards get copy and paste for sections, and sections that fill themselves.
  • Entities are named once, with device and area context added where it helps.
  • New troubleshooting tools: a “Triggered by” filter, per-integration live logs and an Action history tab.
  • Matter 1.5 cameras, local disk storage for backups and media, LoRaWAN, and Zigbee Green Power.

Breaking changes and deprecations

Reported in the release blog post, which lists 44 backward-incompatible changes. The ones most likely to affect a home setup:

  • Entity names change. Cards, badges and rows without a name now show the device name followed by the entity name. Entity IDs do not change. friendly_name is planned for deprecation; templates should use entity_name(), device_name() and area_name(). Tuya multi-channel devices also change names.
  • HACS. A separate HACS install is no longer possible on 2026.11. Existing installs migrate on startup.
  • Remote access. Logins at non-local addresses must match the browser’s scheme, host and port, or fail with “Invalid client id”. Behind a proxy, add it to trusted proxies or use a domain name.
  • Core outside a virtual environment no longer uses the deps folder. Run Core in a virtual environment and remove the old folder.
  • Z-Wave needs zwave-js-server 3.11.0+ (Z-Wave JS app 1.9.0+ or Z-Wave JS UI v11.24.2+). Update that first.
  • Uptime Kuma older than 2.0.0 is no longer supported. Update it first.
  • Matter concentration sensors use the device’s unit, which can change values (for example TVOC by a factor of 1000).
  • ZHA group entities move to their own devices, so targeting the coordinator no longer reaches them.
  • Telegram: the legacy notify platform is removed.
  • Calendar and Sun triggers without offset_type: the sign of the offset now decides before or after. Flip the sign in YAML-only triggers.
  • MQTT entities without a unique_id no longer create devices.
  • Watergate shows a one-time statistics spike.
  • Several integrations (Hayward Omnilogic, Hive, Keenetic NDMS2, Kraken, Plaato, Risco) now ignore a custom polling interval.
  • Removed or changed: Bluesound join/unjoin actions, Nanoleaf touch gesture triggers, Ring legacy entities, Philips Hue "None" effect, UniFi Protect HDR switch, some Evohome actions.

See the blog post for the full list.

Tested in our lab

We tested a Docker (Container) install on a fresh Ubuntu VM. This was a minimal setup: one user, one input_boolean helper defined in configuration.yaml, and no hardware or other integrations. It does not exercise most of the breaking changes above.

  • Installed ghcr.io/home-assistant/home-assistant:2026.10, which was 2026.10.4. Completed onboarding through the API and restarted.
  • Stopped the container cleanly (docker stop -t 120), removed the stopped container, and started 2026.11.0 on the same /opt/ha config volume.
  • After the upgrade the web server answered, the version reported 2026.11.0, and the login flow and API worked with the same user and password.
  • The user and the input_boolean.lab_flag helper were still there.
  • Logs: the only error was the Bluetooth permission message (no NET_ADMIN/NET_RAW in the container). It also appeared on 2026.10.4. The 2026.10.4 logs also showed a cancelled “Shopping list” setup during our restart; that did not appear after the upgrade.

Not tested: HACS migration, Matter, Z-Wave, ZHA, MQTT, remote access through a proxy, dashboards, and the entity-name changes with real devices.

Lab log

$ docker run -d --name homeassistant --restart unless-stopped -v /opt/ha:/config -e TZ=UTC --network host ghcr.io/home-assistant/home-assistant:2026.10
[...]
$ docker exec homeassistant python3 -c "import homeassistant.const as c;print(c.__version__)"
2026.10.4
$ docker stop -t 120 homeassistant && docker rm homeassistant && docker pull -q ghcr.io/home-assistant/home-assistant:2026.11.0 && docker run -d --name homeassistant --restart unless-stopped -v /opt/ha:/config -e TZ=UTC --network host ghcr.io/home-assistant/home-assistant:2026.11.0
homeassistant
homeassistant
ghcr.io/home-assistant/home-assistant:2026.11.0
4b087b8bce8558486ca8e2cc5b675b783095cc797d8ac14ec0ad753da96a3677
$ curl -s -o /dev/null -w "%{http_code}\n" localhost:8123/manifest.json
200
$ docker exec homeassistant python3 -c "import homeassistant.const as c;print(c.__version__)"
2026.11.0
$ grep -o "\"username\": \"lab\"" /opt/ha/.storage/auth
"username": "lab"
$ curl -s localhost:8123/api/ -H "Authorization: Bearer [redacted]"
{"message":"API running."}
$ curl -s localhost:8123/api/states/input_boolean.lab_flag -H "Authorization: Bearer [redacted]"
{"entity_id":"input_boolean.lab_flag","state":"on","attributes":{"editable":false,"friendly_name":"Lab flag"},[...]

Reported by others

Everything in the breaking-changes section above is reported by the Home Assistant team in the release blog post. We did not look at user issue reports for this release.

Verdict

The upgrade itself was uneventful in our lab for a basic Container install. The risk is in what you have connected. Before upgrading, check the list for your integrations, update zwave-js-server and Uptime Kuma first if you use them, take a backup, and review dashboards and templates that rely on friendly_name or on old entity names.

sources

other Home Assistant releases