Home Assistant 2026.6 Beta: 4 Changes That Matter

Home Assistant releases tend to bundle dozens of small improvements, and 2026.6 is no exception. Across roughly forty notable changes in the release notes, four stand out as ones non-technical users will actually feel in their day-to-day setup. The rest sit quietly in the background and improve with each upgrade.

You can now commission Matter devices through a Bluetooth proxy. If you've previously deployed a cheap ESP32-based BLE proxy for room-presence detection or BLE thermometers, that same proxy can now act as a relay for adding new Matter devices to your network.

Why it matters in your house: Matter pairing has historically required Bluetooth-range proximity between the device and the controller doing the commissioning - usually your phone or the Home Assistant box itself. If you're adding a Matter bulb in the loft, the garden shed, or a far bedroom where your phone's BLE doesn't quite reach, you'd have to physically carry the device next to the hub, pair it, then walk it back. The Bluetooth proxy approach reuses the £15 ESP32 boards you may already have scattered around the house as commissioning relays. Devices pair from wherever your proxies live.

The practical implication: your existing BLE proxy network (if you've set one up for presence detection) now doubles as a Matter onboarding fabric. No new hardware to buy, no awkward device shuffling, and significantly less friction when adding the next Matter device to your home.

When you add a card to your dashboard, the picker now shows you what each card looks like populated with your live entity data - instead of presenting a generic list of card-type names and forcing you to guess which one will work.

Why it matters in your house: building a dashboard has always been a slightly painful trial-and-error loop. Pick a card type from a name ("tile card", "button card", "area card"), configure it, save, look at it, decide it's wrong, delete, repeat. For anyone who touches their dashboard a couple of times a year, this loop is the difference between "I'll get round to it" and "actually done in an hour". Live previews collapse the loop - you see a card filled with your sensors, switches, or lights before you commit.

It's the kind of quality-of-life change that won't make a release-notes headline anywhere outside the Home Assistant blog, but it's the one most people will notice within a week.

The Z-Wave integration gains a dedicated UI for adding, naming, and removing PIN codes on supported Z-Wave smart locks - directly from Home Assistant, without touching the vendor's app or the lock's keypad.

Why it matters in your house: the most persistent annoyance with smart locks (Schlage, Yale, Kwikset on Z-Wave) is that adding a temporary code for a cleaner, dog walker, Airbnb guest, or visiting family meant either logging into the vendor's cloud app - which usually requires a cloud account you'd rather avoid - or wrestling with the lock's clunky on-device keypad. This change brings credential management into the Home Assistant UI where it belongs. Name codes by purpose ("dog walker", "Mum", "Airbnb 14–21 June"), set expiry, revoke when done. The information you'd previously juggle across two apps now lives next to your other automations.

Caveat: this UI is Z-Wave-specific. Matter-over-Thread smart locks (the newer wave of products) and Zigbee locks have separate paths and aren't covered by this release.

The default Bluetooth scanning mode for integrations that rely on it (Owntracks, Bermuda, private-BLE-presence trackers) has switched from "Active" to "Auto". The Home Assistant team is reporting battery savings of 95% or more on phones running these integrations.

Why it matters in your house: if you've ever set up room-level presence with a phone and a network of BLE proxies, you know the cost - your phone's battery taking a noticeable hit because Home Assistant was relentlessly scanning the airwaves. Auto mode adapts the scan rate based on whether anything is actually moving, which for most homes most of the time is "not very much". The flag is opt-out: you can switch back to Active under the Bluetooth integration settings if you have a specific integration that genuinely needs always-on scans. But the new default is the right one for the vast majority of setups, and it should have probably been the default all along.

Home Assistant has been moving steadily towards fewer surprise breakages, but this release does include a handful of changes that will catch out specific setups. Worth reading carefully against your own configuration before upgrading.

The pattern across the last few releases is clear: Home Assistant is gradually moving everyday smart-home tasks out of vendor apps and into the Home Assistant UI directly. Smart-lock credential management was a vendor-app job; now it's a built-in dialog. Matter commissioning used to require physical proximity to a phone or hub; now you can pair through a Bluetooth proxy you already own. The dashboard card picker is no longer a guessing game; it's a visual catalogue with live data.

None of these are revolutionary in isolation, but the trajectory matters. Each release shaves friction off the bits of smart-home life that used to require leaving the Home Assistant tab. That's a slow, deliberate game, and it's the one Home Assistant is winning against the cloud-platform incumbents.

It's also a useful reminder of why a local-first setup pays off over time. When smart-lock PIN management is a Home Assistant feature, you don't lose access to it when the vendor sunsets their cloud service in three years.