Home Assistant 2026.8 Update: What's New and What Changed

The Home Assistant 2026.8 update is here, and it’s a safe, welcome upgrade for most users. Released on August 5, 2026, this release focuses on making the platform more approachable by removing the :8123 port for new installs, moving web server settings into the UI with auto-rollback, and adding quality-of-life improvements like editable entity IDs and a combined battery level entity. If you’re looking for a practical home assistant 2026.8 update guide, you should update when convenient — existing installs won’t break, and the new features are genuinely useful.

How This Guide Was Built

This guide is based on the Home Assistant 2026.8 release blog, the official core changelog, the GitHub releases page, the Open Home Foundation roadmap, and the community release discussion thread. We verified the port change behavior, entity ID editing, combined battery entity, device registry changes, and new triggers against these primary sources. We did not install or test every integration hands-on — all steps and descriptions here are based on official documentation and release notes. Last verified: August 2026.

What’s New in Home Assistant 2026.8

Home Assistant 2026.8 introduces several user-focused improvements centered on approachability. New Home Assistant OS installs default to port 80/443 instead of :8123, web server settings move to the UI with a 5-minute auto-rollback safety net, Developer Tools is renamed to “Tools,” entity IDs become user-editable, and a combined battery level entity aggregates device battery states. The release also restructures the device registry so integrations no longer merge, adds Z-Wave lock credential management, and introduces new vibration and moon phase triggers.

The End of :8123

For new Home Assistant OS installations, the web interface now defaults to standard HTTP port 80 or HTTPS port 443 instead of :8123. Existing installs keep their current port and are completely unaffected. You can change the port from the UI under Settings > System > Network > Web server, and any change auto-reverts after 5 minutes if you don’t confirm. YAML web server config migrates to UI settings stored in config/.storage/http.

The :8123 port has been a long-standing quirk — every HA user had to remember to append it to their address bar. The release notes describe it as “a little piece of technical trivia that everyone simply had to learn.” As community member zweckj confirmed in the release discussion thread, the configuration still lives in a file (config/.storage/http) for emergency access — it just moved out of YAML into the .storage system that HA manages internally. Another user, Linwood, reported initial concern about the YAML-to-UI migration but confirmed after upgrading that the network changes only apply with specific user action.

How to Change Your Web Server Port

To change your web server port, go to Settings > System > Network > Web server in the Home Assistant interface. Enter the new port, then click Save. Home Assistant will apply the change and show a confirmation prompt — you must confirm within 5 minutes, or the change automatically reverts to the previous port. This safety mechanism prevents you from losing access if you misconfigure the port or network interface.

The same settings page also handles the listen interface (which network connection HA binds to) and trusted proxies for reverse-proxy setups. If the new settings cannot be applied at all, Home Assistant falls back immediately without waiting for the 5-minute timer. One important caveat from the release notes: anything that reaches Home Assistant using the old address may need updating to match the new port — including bookmarks, the companion app, and any external services pointing to your instance.

Entity IDs Are Now Editable

You can now rename entity IDs directly from the UI in Home Assistant 2026.8. Behind every device and sensor sits an entity ID — a short name like light.kitchen_ceiling that your automations, scripts, and dashboards use to reference it. Previously, changing an entity ID required editing the entity registry or using developer tools. Now, open the entity’s settings page, edit the ID field, and save. As the release notes explain, this was driven by community feedback — earlier attempts to auto-generate entity IDs from device areas didn’t suit everyone, so the team put users in charge instead. You can also control the ordering of entities within a device.

Combined Battery Level Entity

Home Assistant 2026.8 introduces a combined battery level entity that aggregates battery levels from multiple devices into a single sensor. This addresses a long-standing community pain point: previously, checking battery status meant scanning dozens of individual sensors. The combined entity surfaces the lowest battery level across all battery-powered devices — sensors, locks, remotes, and more — so you can quickly spot which device needs attention and build a single low-battery alert automation instead of monitoring each device separately.

Device Registry Changes

Home Assistant 2026.8 changes how it tracks devices behind the scenes. Previously, if one physical device was set up through two different integrations, Home Assistant merged them into a single device entry. Details that can only hold one value, such as model or serial number, could then clash. From this release, each integration keeps its own device entry. When you update, any previously merged devices are separated automatically, and their entities move to the correct device. Most users won’t notice — automations and scripts keep working because HA still routes actions correctly. If you have a device set up through multiple integrations, you might see it appear twice, and Home Assistant may raise a repair notification to let you know.

New Triggers and Conditions

This release adds two new purpose-specific triggers and their matching conditions, continuing the friendlier automation builder approach introduced last release. Vibration now has conditions to match its triggers — you can check whether something is vibrating (or not) as part of a larger automation, like only sending a “laundry is done” message once the washing machine has actually stopped shaking. Moon phase gains a trigger and matching conditions — start an automation when the moon enters a new phase, or check the current phase as part of a bigger automation for mood lighting or reminders.

Other Notable Changes

Developer Tools renamed to “Tools” — the section was always useful for everyone, not just developers. The shorter name matches how people actually use it.
“Advanced” label removed in ~43 places — reduces intimidation for new users. The features themselves didn’t change; only the wording did, across the app, documentation, and companion apps.
Home Assistant Cloud page redesign — each feature (remote access, backups, voice assistants) now has its own settings page, plus a guided setup flow for new users by Nabu Casa.
Z-Wave lock credential management — manage user codes and PINs directly from the UI.
Template editor improvements — a roomier editor with better usability.
New integrations — including Google Health, Gatus monitoring, Harbor Sleep baby monitor, and GeoSphere Austria Warnings weather alerts.

Should You Update?

Yes, you should update to Home Assistant 2026.8. The release is designed to be non-breaking for existing installs — your port, YAML config, and entities remain as they are. The new features are additive and improve usability. As always, take a backup before updating, and review the full changelog for any integration-specific backward-incompatible changes that might affect your setup.

Common Mistakes

Forgetting to update bookmarks — if you change your port from :8123 to 80, your old bookmarks will stop working. The release notes specifically call this out.
Not confirming the port change — the 5-minute auto-rollback will revert your changes if you don’t confirm, which can be confusing if you don’t expect it.
Changing the port unnecessarily — if your current setup works, there’s no need to change anything; the new default only applies to fresh installs.
Assuming YAML web server config is still active — it migrates to .storage, so manual YAML edits may be ignored after the update.
Not updating the mobile app — after a port change, the companion app may need to reconnect to the new address.
Panicking about device duplicates — if a device appears twice after updating, it’s the registry split working as intended. Check for a repair notification.

FAQ

Is Home Assistant 2026.8 a breaking update?

No, Home Assistant 2026.8 is not a breaking update for existing installs. Your current port, YAML configuration, and entities remain unchanged. The new port 80/443 default applies only to new Home Assistant OS installs. The release notes confirm that “if you are already running Home Assistant, nothing changes and there is nothing you need to do.” The changelog lists a few minor backward-incompatible changes for specific integrations, but standard setups are unaffected.

Do I have to change my port?

No, you don’t have to change your port. The :8123 port remains fully supported for existing installs. The change to port 80/443 only affects new Home Assistant OS installations. If you’re happy with your current setup, you can leave everything as is — the official announcement explicitly states that existing users are completely unaffected. The port change UI is there for those who want a cleaner address or need to change it for other reasons.

What happens to my YAML web server config?

Your YAML web server configuration migrates to UI settings in this release. The settings are stored in config/.storage/http, and the UI becomes the source of truth. If you have custom YAML for the HTTP integration, it will be imported once on first boot after updating, then managed from the UI. You may also see a repair notification letting you know the migration happened. Nothing breaks either way — you can clean up the old YAML at your own pace.

Where to Go Next

If you’re new to Home Assistant, start with our Home Assistant setup guide to get your system running. For hardware recommendations, check out our best HA hardware guide comparing the Yellow, Raspberry Pi 5, and Intel N100. If you’re planning to add camera surveillance, our Frigate NVR setup guide walks through the full process. For the complete list of changes, see the Home Assistant 2026.8 release notes and the official changelog. You can also track future development on the Open Home Foundation roadmap and goals page.

ToolBrain — tool reviews, LLM comparisons, and AI workflow guides

Cross-links automatically generated from SmartHome Field Guide.

← Back to guides