---

⭐⭐⭐ NOTE: ⭐⭐⭐

This article belongs to a YouTube video. I wrote it before recording the video. You can help me continue doing this by checking out the video, commenting on it, giving it a thumbs up, and subscribing to my YouTube channel. This will ensure that the video is offered more frequently to new visitors, allowing them to stay informed about the latest Home Assistant tutorials and smart home-related product reviews.

I appreciate your support!

Ed

For as long as most of us can remember, setting up Home Assistant meant learning one small but universal piece of trivia: stick :8123 on the end of your address, or nothing loads. With Home Assistant 2026.8, now in beta ahead of its August 5th stable release, that trivia finally becomes optional — and it’s paired with a broader push to strip complexity out of the interface.

A New Default Web Address

New installations of Home Assistant now run on port 80 by default, so there’s no more colon-8123 to remember. You’ll find the new setting under Settings > System > Network, where the HTTP server port is now exposed directly in the UI instead of living only in configuration.yaml.

This mainly affects new installs, but some existing installs may also be switched to port 80. If that happens, Home Assistant asks you to acknowledge the change — and if you don’t within five minutes, it automatically reverts back to :8123. So if your server seems to vanish right after updating to 2026.8, don’t panic: wait five minutes, or head straight to homeassistant.local:80 to confirm the new port yourself.

“Advanced” Is Gone — Everywhere

In roughly 40 to 43 places across the interface, the word “advanced” has simply been removed. There’s no longer a distinction between an “advanced” setting and a regular one — everything is presented as just a setting. It’s a small wording change with a bigger implication: nothing new here is meant to feel gatekept from beginners.

In the same spirit, Developer Tools has been renamed to just Tools, and the Home Assistant Cloud settings page has been completely redesigned, making it easier to manage your subscription and cloud-connected features from one clean screen.

Full Control Over Your Entity ID Format

Under Settings > System, a new Entity ID Format option lets you decide exactly how new entity IDs are constructed. Want area first, then device, then entity? Done. Prefer to add the floor, or move the area to the end instead? You can rearrange it freely — for example, turning a default like sensor.thermostat_temperature into ground_floor.living_room.thermostat_temperature, or any other order that matches how you think about your home.

This only applies to new entities, or existing ones you choose to reset, but for anyone managing a large, evolving smart home, it’s a genuinely useful piece of housekeeping.

New Automation Triggers: Vibration and Moon Phase

Two new additions round out the automation trigger and condition options: a vibration trigger (vibration detected / vibration cleared, with optional duration) for vibration sensors, and a moon phase trigger that fires when the moon changes phase — including, if you’re in the mood for something silly, a full-moon trigger that could howl through your smart speakers.

Devices Split Across Multiple Integrations

Previously, a device delivered by more than one integration would often show up as a single device in Home Assistant. In 2026.8, that changes: the same physical device can now appear multiple times, once per integration that delivers it.

The practical impact shows up in Settings > Repairs, where you may see a batch of “replaced device” notices after updating. Each one lets you pick which integration’s version of the device your existing automations should point to — for example, choosing between a Reolink and a TP-Link integration for the same camera. It’s worth working through these one by one so nothing silently breaks.

Smaller Quality-of-Life Wins

• Template editor: the preview pane can now be repositioned to the bottom of the screen and resized independently, so you can keep a large editor and a compact preview side by side.
• Radio browser: the media browser finally has a search field, so finding a specific station (like a local FM station) no longer means scrolling through an alphabetical list.
• Energy Dashboard: home battery storage sources now have a battery capacity field, so the dashboard can show an accurate charge percentage instead of an estimate.
• Dashboards: when adding a card, you can now mark cards as favorites, which surface in their own section for faster access next time.

Verdict / Conclusion

None of the individual changes in Home Assistant 2026.8 is flashy on its own. But losing the mandatory :8123, combined with stripping “advanced” out of 40-plus places in the UI, tells you where the project is heading: less for a newcomer to memorize or feel intimidated by, without losing any power for people who want to dig deeper.

This is a quality-of-life and philosophy release rather than a landmark one — but it’s exactly the kind of friction removal that makes Home Assistant easier to hand to someone who isn’t a tinkerer. If you want to try the new web server settings or entity ID controls early, the 2026.8 beta is available now. If you’d rather wait for the fully tested version, that lands on the first Wednesday of the month, August 5th.