Home Assistant 2026.6 dropped on June 3rd, and I updated my EliteDesk over the weekend after the usual ritual: read the breaking changes twice, check that last night’s backup actually exists, hold my breath for ninety seconds. The release is nicknamed “Pick a card, any card”, and for once the headline feature is the one I’d actually point a newcomer at. But there are a few quieter changes buried further down the release notes that matter more for a local-first setup like mine. Here’s what I found.
The card picker finally starts from your home, not from jargon
If you’ve ever sat someone in front of the dashboard editor and watched their face when the old card dialog opened — tile, glance, gauge, markdown — you know exactly why this change exists. Those are internal building-block names. Nobody opens the editor thinking “I need a glance card.” They think “I want the living room light on this page.”
The new dialog opens on a By entity tab: a tree of your floors, areas, devices, and entities on the left, and live previews of cards that actually fit the entity you picked on the right. Choose a light and you get a plain tile, one with a brightness slider, a toggle, color temperature. Choose a temperature sensor and you get a trend-graph tile. Every suggestion renders with your real data before you commit, which kills the old add-it-look-at-it-delete-it loop entirely.
I rebuilt part of my hallway dashboard with it as a test. It’s faster, but the bigger win is that I can now hand the editor to my wife without a twenty-minute vocabulary lesson first. The Home Assistant team says this is the first step of a broader roadmap effort to make dashboards start from what you want to control. Good. That’s the right direction.
Infrared now listens, and ESPHome is the first ear
Two releases ago, infrared became a first-class platform in Home Assistant — but only one-way. HA could blast commands at your TV or air conditioner, but if someone used the original remote, Home Assistant was left holding stale state. 2026.6 closes the loop: the Infrared platform gains a receiver event entity, and any ESPHome device with an IR receiver wired up can now report what it hears as events you can automate on.
This is the kind of feature that sounds niche until you live with it. Stale state is the silent killer of trust in a smart home — the dashboard says the TV is off, the TV is very much on, and the family stops believing the dashboard. Listening to the original remote fixes that without forcing anyone to change habits. It also means a spare IR remote in a drawer can become a cheap, battery-sipping, fully local controller. I have an ESP32 with an IR receiver on my bench already; this just moved up my project list.
The automation editor grew up a little
Three small things landed in the automation editor that together remove a lot of low-grade friction. First, every floor, area, device, and label target now shows how many entities it expands to — so “Bedrooms” reads as “Bedrooms · 12” and you know before saving whether your automation hits twelve lights or thirty. Second, condition rows now show a live pass/fail badge that updates in real time as your home changes. Debugging “why didn’t this fire” used to mean digging through traces; now the failing condition literally has a red dot on it while you edit. Third, every step can carry a proper notes field, separate from its name. Future-me, who will absolutely not remember why there’s a four-second delay on the porch sensor in winter, thanks present-me already.
None of these are flashy. All of them are the difference between an editor you fight and an editor that helps. The zone-based triggers and conditions in Labs also keep maturing, if you’ve opted into that preview.
The quiet wins for a local-first house
The changes I care most about are further down the release notes. Bluetooth scanning now defaults to a new Auto mode — active scanning only when an integration actually needs it, on one scanner at a time, instead of every proxy constantly waking up your battery-powered sensors. Home Assistant claims around 95% less battery drain from Bluetooth scanning. If that holds up, it’s the single most valuable line in this release for anyone running a fleet of coin-cell sensors. I’ll be watching my battery graphs over the next month and will report back honestly.
Z-Wave smart locks got credential management — add, edit, and remove users and PIN codes from a dialog in Home Assistant, with everything happening directly between HA and the lock. No cloud account, no vendor app, no internet required. Matter locks got this two releases ago; Z-Wave catching up matters because Z-Wave locks are still the sensible choice in much of Europe. You can even hand out a one-time guest PIN from an automation. That’s the local-first promise actually delivered, not just marketed.
Smaller notes from my own shopping list: the Shelly integration now exposes an occupancy binary sensor, OpenThread Border Router 1.4 is out of beta with a built-in mDNS implementation that should calm a class of stubborn Thread connectivity gremlins, and Matter device setup now asks you to name the device and assign an area immediately — a tiny change that will save every household one confused “which ‘Contact Sensor 3’ is this” moment.
Advanced mode is gone, and I think that’s right
2026.6 removes the “Advanced mode” toggle from user profiles entirely. Everything that used to hide behind it is simply available to everyone now. Some long-time users will grumble. I won’t. The toggle always carried a quiet insult — the suggestion that parts of your own home automation system were above your pay grade. A wall of hidden features never made anyone an advanced user; using the features did. The YAML editors even got inline linting this release, which says it plainly: you don’t have to write YAML, but if you do, the UI will help rather than gatekeep.
Should you update?
Yes, with the usual discipline. The first patch release, 2026.6.1, already landed on June 5th with a batch of fixes, so you’re not even taking the .0 risk anymore. Read the backward-incompatible changes — if you’ve been using the Labs purpose-specific triggers, the behavior options were renamed (any is now each, last is now all) and your YAML needs updating. And while you’re in the backup settings, do what the redesigned page now nags you to do: save your backup encryption key somewhere that isn’t inside the thing being backed up. A backup you can’t decrypt is a very well-organized way of having no backup at all.
My install went through clean: Zigbee2MQTT untouched, automations intact, one dashboard happily rebuilt with the new picker. That’s two smooth upgrades in a row on the EliteDesk, which I’m choosing to interpret as the universe rewarding boring, well-supported hardware.
Full details in the official 2026.6 release post. If you find something in this release that breaks — or quietly improves — your setup, the comments are open. I read all of them.
Leave a Reply