Home Assistant 2026.8: What Actually Changes in My Setup

Every month, the Home Assistant changelog runs two or three pages: 15 new integrations this time, a redesigned Home Assistant Cloud page, more inclusive language across the UI (the word “advanced” quietly disappeared in about forty places), and new installs no longer defaulting to port 8123. Most of that doesn’t touch my setup directly: I don’t own a Dyson, a Midea air conditioner, or a Modbus NeoPool controller, and I’m not on Nabu Casa Cloud. Here’s what actually matters for my install.

Lots of Headlines, Little Signal for Me

Of the 15 new integrations in this release (Dyson Infrared, Midea, NeoPool, LiteLLM, llama.cpp…), none of them match my current setup. Same story for the redesigned Home Assistant Cloud page: it streamlines Nabu Casa onboarding, but I manage my own remote access and backups, so that work doesn’t concern me. That’s the whole point of triaging a changelog: keep only what will actually touch your day-to-day.

My YAML Templates Just Got Faster, for Free

This is the change that helps me the most in practice, even though it’s a single line in the changelog: numeric-result templates are now up to 40% faster, and templates used on dashboards can be cached. My config leans heavily on template: blocks (calculated sensors, conditional cards, helpers), so this kind of optimization shows up directly in interface responsiveness, without touching a single line of YAML.

Related change: template entities (fans, covers, device trackers) now restore their previous state after a restart, instead of resetting to a default. Good news for the overall stability of my calculated entities, though it doesn’t fix my recurring issue with the custom Tesla integration coming back as unknown after a reboot (a third-party component issue, not a Home Assistant core one — see my TeslaMate write-up).

Pool: Shelly Gets a Stronger Security Mode

My pool runs on a Shelly Pro 3 (pump, light, chlorinator — see how I automated its runtime). This release adds support for Shelly’s “Enhanced Security” mode (HTTPS-only, from firmware 2.0 on gen2+ devices), plus better support for connected circuit breakers with on/off control and output-state sensors. Nothing breaks in my existing config, but it’s the kind of firmware update I’ll flip on as soon as I can: a device driving an outdoor electric motor might as well be talking HTTPS.

Blinds: Overkiz Keeps Quietly Improving

Nothing dramatic, but Overkiz (the gateway behind my Somfy blinds — see my Somfy TaHoma Switch gateway) picks up binary window and tilt sensors for contact sensors, plus support for the Somfy PRO thermostat. It won’t change my life, but it confirms the integration is still actively maintained, which matters when the entire solar-shading automation in the house depends on it.

Heads Up If You’re on UniFi Protect

This is the only real breaking change that directly affects me. Starting with this release:

• UniFi Protect 7.1 or later is now required. On an older console, the integration simply refuses to set up.
• Detection scores (event_score) are gone. Binary detection sensors (motion, person, vehicle, animal) now rely on UniFi Protect’s public API, which no longer exposes a per-event score. The event ID and detected type move to new dedicated entities: Motion detection, Smart detection, and Sound detection.

I checked my automations on my VLAN-segmented network: none of them rely on event_score, so nothing to fix on my end. But it’s the kind of silent change that can quietly break an automation if you were filtering on it. In exchange, the integration gains support for UniFi USL sensors (entry, environment, glass-break) starting with UniFi Protect 7.2.

Everything Else Worth Knowing, No Rush

• Manual entity ID renaming directly from the UI, with display-order control: handy for cleaning up a config that’s grown over months without a strict naming convention.
• No more automatic device merging across integrations: each integration now keeps its own device entry, avoiding metadata conflicts when the same physical device is seen by multiple integrations. Migration happens automatically on startup, no action needed.
• SMLIGHT SLZB reaches Platinum, the top tier of the integration quality scale, with Bluetooth proxy support thrown in: a solid reliability signal if you’re using it as a Zigbee coordinator.
• Netatmo moves up to Bronze on the same quality scale, after maintainers brought it into compliance.
  

Bottom Line

As usual, it’s not the headline features (15 new integrations, a Cloud redesign) that change anything day-to-day — it’s a quiet line about template performance and another about state restoration that you’ll actually feel while using the system. The one real action item from this release is checking your UniFi Protect automations for any lingering event_score reference. Beyond that: update, flip Shelly firmware to HTTPS-only when you get a chance, and carry on.

FAQ