Homelab

Before you update to Home Assistant 2026.11, check these five things

AusGeek · · 7 min read

Home Assistant 2026.11 is the release you shouldn't install at 10pm and walk away from. It isn't dangerous. It's just big: the release notes call it "the biggest release we've ever shipped, by far", and three of the changes touch things people tend to set up once and forget about. HACS becomes part of core, dashboard names change, and some old browsers stop loading the frontend. None of it is hard if you know it's coming, so here's the pre-flight list I'd run before pressing Update.

Quick note on what this is: I'm working from the 2026.11 release notes, the Marketplace documentation and the naming blog post, not from a month of living with it. At the time of writing the current patch is 2026.11.1, from 9 November, and the project aims for a patch release most Fridays through the month.

1. Take a manual backup, and find your encryption key

This is boring and it's the most important item on the list, because the Marketplace docs are explicit that rolling back isn't done from inside the Marketplace. If an update goes wrong, the advice is: "Restore a backup instead."

Per the backup docs, it's Settings > System > Backups, then Backup now, then Manual backup. The docs suggest leaving out media and the share folder to keep it small, which also makes it quicker to restore.

The bit people skip: backups are encrypted, and you need the key in the emergency kit to restore one. If you've never downloaded the kit, the Encryption key card on the backups page lets you download it again. Put it somewhere that isn't the Home Assistant box. A backup you can't decrypt is a very tidy file of nothing.

If your backups have been landing on the same drive Home Assistant runs on, 2026.11 also adds local disk storage under Settings > System > Storage, so a USB or internal drive can hold them. The docs say the disk needs to be formatted already.

2. Know what happens to HACS

If you use HACS, this is the headline. HACS is now built in as the Marketplace, under Settings, on every installation type including Container. The release notes say the migration happens automatically the first time Home Assistant starts after the update: what you installed stays installed and keeps getting updates, custom repositories and update entities carry over, and old /hacs bookmarks open the Marketplace. The HACS installer won't install on 2026.11, and the standalone HACS won't get new releases.

Honestly, I think this is a good outcome. HACS was donated to the Open Home Foundation about a year and a half ago, and moving it into the normal release process means one less thing to keep updated by hand. The release notes are also refreshingly blunt that everything in the Marketplace is community code, "not tested, audited, or supported by the Home Assistant project", and it runs inside your Home Assistant. You have to accept that notice before you can install anything. Worth actually reading rather than clicking through.

The Coming from HACS section lists the edges. The ones most likely to bite:

If you don't want the Marketplace at all, the docs say you can disable it from Settings > Devices & services > Marketplace. Installed content keeps working but stops updating. Deleting the integration entry doesn't stick, because it's set up again on the next start.

3. Expect your dashboard names to change

This one is cosmetic but it'll be the first thing anyone in your house notices. Entity naming has been reworked, and it's flagged as a backward-incompatible change. Cards, badges and rows that don't have a name set on the card now show the device name followed by the entity name. The release notes' example: an entity you named "Off-peak consumption" on a "Power meter" device shows as "Power meter Off-peak consumption".

What doesn't change, per the notes: entity IDs. Automations, scripts and dashboards keep working. Names you set yourself are migrated, and if a displayed name changes, the old one stays as an alias for voice assistants, so "turn on the ceiling light" keeps working.

To tidy things up after the update, the options are: rename the device rather than the entity, turn on Main entity of the device for the entity that represents the whole thing (the plug's switch, say), or set a name on the card. If you lean on custom cards, the notes say to update those first, since the authors of many popular cards were sent changes to match.

Template writers: friendly_name is planned for deprecation in favour of entity_name(), device_name() and area_name().

My opinion: give it a week before you start renaming things. The naming post makes a decent case that the new defaults remove the need for a naming scheme at all, and the fix for most odd-looking names is renaming the device, once.

4. Check the old tablet on the wall

This is the one most likely to catch someone out, because the device in question is usually a hand-me-down screwed to a wall and nobody has looked at its OS version since 2019. The frontend now needs Chrome 67, Safari 15.4 or Firefox 98 or newer. The release notes list what that rules out:

The notes say Fire tablets on Fire OS 5.6.4 or newer (2017 models), 6.3.1.2 or newer, or Fire OS 7 keep working, so check for a Fire OS update before you write one off. An older browser now gets a message on the launch screen instead of spinning forever. This isn't anyone pulling the rug. Software that's been held back to support the original iPad Air for this long is unusually generous, and there's a point where a decade-old WebView is the thing holding everyone else back.

5. If you reach it by public IP or Tailscale, read the Auth note

Most setups aren't affected, but if you are, the symptom is a confusing "Invalid client id" at login. Per the release notes, when you reach Home Assistant at an address that isn't on a local network (a public IP, a global IPv6 address, or a Tailscale 100.64.0.0/10 address), the address in your browser now has to match the scheme, host and port Home Assistant sees. Previously a bug let some of these through.

Opening it directly at that address still works, as does a reverse proxy set up as a trusted proxy in the HTTP integration. If you hit the error, the fix the notes give is to add your proxy to the trusted proxies, or reach Home Assistant through a domain name.

The rest of the list

There's a long tail of integration-specific changes in the backward-incompatible changes section: AdGuard Home, Z-Wave, ZHA, MQTT, Tuya, UniFi Protect and a few dozen more. Search the page for each integration you run. Five minutes is cheaper than an evening wondering why the porch light automation stopped.

Then back up, update, and give the dashboard a once-over before anyone else in the house does.