My Smart Homes

Home Assistant 2026.8 and 2026.9: What Actually Shipped

Home Assistant 2026.8 dropped the :8123 port, rebuilt the Cloud page and made templates 40% faster. Here's what landed — plus what 2026.9 added on September 2.

Back at the start of August we previewed the 2026.8 beta. The stable release landed on August 5 under the title “Approachable by design” — and now that it’s been in the wild for a month (through patches 2026.8.1, .2 and .3), it’s worth looking at what actually shipped, what changed from the beta, and what the September release has in store.

If you’re new to the platform, start with our complete guide to Home Assistant first — this post assumes you already have a system running.

The headline: the :8123 port number is gone

For years, reaching your own smart home meant typing an address with a random-looking number stuck on the end. Home Assistant’s own release notes put it well: it was “a little piece of technical trivia that everyone simply had to learn.”

New Home Assistant OS installations now use a normal web address — no port to append, no number to remember. Web server settings also moved into the interface, where you can see which network connection Home Assistant listens on and configure trusted proxies without touching YAML.

What this means for your existing system

Nothing. Existing installations are completely unchanged and keep working on the same port. Home Assistant’s own advice is the sensible one: if everything works today, leave it alone.

If you do decide to change it, there’s a genuinely thoughtful safety net. After you apply new web server settings, Home Assistant waits for you to confirm you can still reach it. Don’t confirm within five minutes and it assumes something broke, restores your previous settings, and restarts on its own. You cannot lock yourself out permanently — you just wait a few minutes.

One practical caveat: if you change the address, anything pointing at the old one needs updating — bookmarks, the mobile app, and any connected services or dashboards on your network.

“Advanced” is no longer a label

This is a small change with an outsized effect on how the system feels. Words like advanced and expert were scattered across the interface, the documentation and the companion apps — roughly 43 places in total. All of them are gone.

None of the underlying features changed. The wording now describes what a feature does instead of rating whether you’re qualified to use it. In the same spirit, Developer Tools is now just Tools — because checking a device’s state or testing a template never required being a developer.

For homeowners who’ve been quietly avoiding half the settings menu, that’s a meaningful invitation.

The Cloud page finally makes sense

Home Assistant Cloud (remote access, fast local-first voice, encrypted backups) used to live on one long page of switches. It’s now a proper overview: remote access, backups, voice assistants and the companion app each get their own space, with detailed settings on their own dedicated pages.

More importantly for anyone setting up for the first time, there’s now a guided setup that walks you through Cloud step by step rather than dropping you into a wall of toggles. You can postpone it and pick it up later.

Entity IDs are yours to name

Every device in Home Assistant sits behind an entity ID like light.kitchen_ceiling, and automations, scripts and dashboards all reference it. Earlier releases experimented with generating those IDs automatically from the area a device belongs to. User feedback was split, so 2026.8 takes a different route: you can now rename an entity ID yourself and control how it’s ordered, so your naming follows whatever pattern makes sense in your house.

If you’ve ever inherited a system full of sensor.0x00158d0004a1b2c3_temperature, this one’s for you.

One device per integration

Previously, if the same physical device was set up through two integrations, Home Assistant merged them into a single entry — and fields that only hold one value, like model or serial number, would clash. From 2026.8, each integration keeps its own device entry.

Merged devices are separated automatically on update and their entities move to the correct device. Most people won’t notice. In the rarer case where a device really was configured twice, it may now appear twice — once per integration — and Home Assistant will raise a repair explaining why. Automations keep working, because actions still route to the right device; the exceptions worth checking are automations that reference a device by ID directly.

Smaller changes that add up

  • Templates run up to 40% faster for numeric results, and dashboard templates can now be cached. Fan, cover and device tracker template entities also keep their state across a restart.
  • New triggers and conditions. Vibration gained conditions to match its triggers — so a “laundry is done” notification can wait until the washer has actually stopped shaking. The moon gained a trigger and conditions for phase changes.
  • Searchable media. Integrations can now offer search directly in the media browser instead of folder-by-folder clicking. Immich added a smart search that finds photos by what’s in them rather than by filename.
  • Z-Wave lock credentials got a serious upgrade via Z-Wave JS 1.6.0: multiple credential types per person (a PIN and a fingerprint), enrollment from the interface, a full audit log, and bulk credential management. Note this currently lives in Z-Wave JS UI rather than the Home Assistant Z-Wave panel. If locks are on your list, our roundup of the best Zigbee and Z-Wave devices for Home Assistant is a good starting point.
  • Weighted battery levels in the energy dashboard — assign each battery a capacity so a small full battery and a large empty one no longer average into a misleading number.
  • Favorite cards can be starred in the card picker so they float to the top.
  • Fifteen new integrations, including Google Health, Midea, NeoPool pool controllers, Harman Luxury Audio, and local AI conversation agents via llama.cpp and LiteLLM.

Breaking changes worth checking

A few items need attention before you update:

  • Robot vacuums: the deprecated battery_level property is removed from vacuum entities — use the battery sensor instead. Affects LG ThinQ, Neato, Romy, Shark IQ, SwitchBot Cloud, TP-Link and Xiaomi Miio.
  • UniFi Protect now requires version 7.1 or newer, and detection sensors no longer carry an event_score attribute — automations filtering on it need another condition.
  • Paperless-ngx requires server version 2.19 or newer; update the server first.
  • Volvo On Call has been removed — migrate to the newer Volvo integration.

Update: 2026.9 has now shipped

2026.9 landed on September 2 under the title There is room on this bus. Everything trailed in the beta made it into the stable release:

  • A Matter network map in the Matter panel, showing Wi-Fi and Thread devices alongside access points and Thread Border Routers — joining the maps already available for Zigbee, Z-Wave and Bluetooth.
  • Activity history that explains itself — not just what changed, but why: which automation or manual action caused it.
  • An active alerts section on the security dashboard, so you can decide per entity whether it alerts or merely warns.
  • A Serial panel that lists USB Zigbee and Thread radios, separating what’s in use, what’s connected but idle, and what’s expected but missing.
  • Sun triggers for golden hour, blue hour, midnight sun and polar night — useful if you want lighting that tracks the mood outside.

Should you update?

For most homes, yes — 2026.8 is a polish release, and after three patch releases it’s had a month to settle. Read the breaking changes above first, check whether you run UniFi Protect or a robot vacuum with battery-based automations, and take a backup before you start.

If you’re still deciding what to run Home Assistant on, see our comparison of Home Assistant Green vs Yellow vs Raspberry Pi, or the step-by-step Raspberry Pi install guide.

FAQ

Do I have to stop using :8123?

No. Existing installations keep the port and keep working exactly as they did. The change only applies to new Home Assistant OS installations.

What happens if I break my web server settings?

Home Assistant waits five minutes for you to confirm the new settings work. If you don’t, it restores the previous configuration and restarts automatically.

Will the device registry change break my automations?

Almost certainly not — actions still route to the correct device after the split. Check any automation that references a device by its raw device ID.

Has 2026.9 arrived?

Yes. 2026.9 was released on September 2, 2026. Alongside the features above it removes the VLC integration, strips the deprecated battery_level property from vacuum entities, changes LLM tool names, and raises the UniFi Protect requirement to 7.2.105 or newer. Installing or skipping updates, and Z-Wave JS lock credential management, now require an admin account.

Do I need a professional to manage Home Assistant?

Not necessarily — but if you’d rather have a working system than a weekend project, we design and install Home Assistant systems for homeowners across New Jersey. See what smart home installation costs in New Jersey.

Leave a Reply