2026.6 Beta Week

Configuration
1

A general reminder: Beta week is not designed to fully overhaul a new feature, but to identify bugs that may be introduced with the update.

If you have an issue, please let us know here! However, the developers are very active in the #beta channel of our Discord server during Beta - it's good to hop in there if you can. To ensure things are addressed in a timely manner, be sure to also submit issues on GitHub in their proper space:

Here are this month's Beta notes! This month has a smaller amount of feature releasing but a lot of QoL improvements.

These are my cliff notes for this month's release, in order of my excitement:

  • Quality of life improvements to the automation editor! We get closer to the purpose-specific triggers and conditions being complete in Labs, and this month is polishing some things up. See how many targets are in an automation, add notes to any step of your automations, and review the backward-incompatible change for the renaming of behavior options (which has the potential to break YAML automations).

  • Infrared can listen with its receiver event entity. Now you can turn any IR remote into a Home Assistant controller! :exploding_head:

  • Dashboard improvements include a friendlier way to add cards to dashboards with live previews and new tile card features for weather entities and the media player tile.

  • The Apps page receives a modern upgrade.

  • YAML linting in the UI editors! :tada: Very nifty for spotting those spacing issues.

  • The Energy dashboard is getting two quality of life improvements this release - a state-of-charge sensor for batteries, and you can now name your sources with custom names.

  • Quick links makes it easier to jump straight to a related item without the need for back and forth between settings pages!

  • To get it up to speed with Matter, you can now manage credentials for your Z-Wave smart locks.

  • New integrations this release are AiDot, CentriConnect/MyPropane, Cielo Home, Data Grand Lyon, Guntamatic, LG TV via Serial, Marantz Infrared, Mitsubishi Comfort, Ouman EH-800, OVHcloud AI Endpoints, PAJ GPS, PTDevices, Samsung Infrared, Vistapool, Xthings Cloud, and Yoto. Congrats to all the integration owners who made it in this release! :clap:

  • Noteworthy improvements to existing integrations - everyone’s favorite device brand, Tuya, received a massive update, MQTT has two improvements, Shelly exposes an occupancy binary sensor", you can search within Sonos now, SwitchBot gets more device support, UniFi Protect now has an alarm profile select entity, YouTube exposes a video count sensor, and so much more. Check out the full list to see if your active integrations are on it.

  • We had 8 integrations achieve new quality scale levels - 4 reached Platinum, 1 reached Gold, 1 reached Silver, and 2 reached Bronze. Great work to these devs! :partying_face:

  • We have three new integrations now available to set up from the UI: Elgato Avea, openSenseMap, and OPNsense.

  • Other noteworthy changes - the Matter integration now acts as a Bluetooth bridge for the Matter Server and sirens are exposed for Matter, check firmware versions in the devices table, grouping devices via ZHA is easier, search by label is in several new spaces, the Backup settings page has been reorganized to make it easier to find your encryption key, Bluetooth UI catches up with the new auto scanning mode (see backward-incompatible changes below), and the statistics graph card now lets you customize the colors.

  • The list of integrations impacted by backward-incompatible changes includes the mentioned purpose-specific triggers in Labs and Bluetooth as well as Certificate Expiry, ESPHome, HDMI-CEC, IronOS, ONVIF, Shelly, SmartThings, Template entities, Tuya, and Velux.

There are a ton of Developer blog posts for this release, including Frontend component updates for 2026.6. If you want to see the meat behind everything, you can see the full list of the posts important to this release at the bottom of the backward-incompatible changes.

The build is available now - happy testing, friends! :tada:

9 Likes
3

Nice improvements, again! :person_bowing:
Giving it a testdrive...

4

Really cool release. Noticed two things when trying to use the new z wave manage access feature:

  • Existing codes don't get displayed upon first opening (says no users configured)
  • When trying to add a new user/pin, get the following error message:

Failed to set user: zwave_error: Z-Wave error 322 - User Code CC requires a credential to be set before modifying the user. Use setCredential() first. (ZW0322)

Using Z-Wave JS UI...

1 Like
5

The upgrade to the Unifi Protect Alarm Manager is nice... but the profile selection should really be part of the arm/disarm selector like we have for other alarms.

I created an issue for it on GitHub here.

6

Color customization for the statistics graph card. The Statistics graph cardcatches up with the history graph cardand lets you pick a custom color per entity, both from the visual editor and in YAML.

Not exactly correct. In fact, both History graph and Statistics graph cards got the “color” option in 2026.6, it is not about “card X catches up with card Y”.
And for Statistics graph card, technically it is NOT possible to define a color in UI editor because a corresponding PR is not merged yet.

7

Who are these people?

I have never done this. I always have a card type in mind and usually it is for a mix of entities, not just one.

Can we set the old behaviour as default somewhere?

16 Likes
8

In the main (right side bigger panel) there is a link 'Browse all cards' that opens the previous style of selecting cards including custom cards. It's an extra click but no big deal to me. Is that what you're looking for?

9

No. I'm looking for a way to make that selection permanent.

1 Like
10

Hm...same question... i'm on this forum pretty constantly, but i didn't see any discussion in this manner... (but then again, perhaps i did miss it...)

Same here. Since... say 60-80% of my cards are "custom button card" i basically don't have anything "in my mind", i just add mentioned card and voila.

Well... perhaps not a big deal, yes. But, extra click here, extra click there... and you quickly end up with tons of these "extra clicks"... this default should really be made user selectable.

1 Like
11

Here's another perfect example of such an inconvenience:
I selected 'copy' for an action within the Automation Editor UI, then select '+ add action' and I'm greeted with this popup:

image
image1084×844 52.4 KB

... which requires an extra click to open the 'by type' tab of the popup in oder to get to the 'paste' option. ALso, just noticing this now in the 2026.6.0b0 beta version that there is no longer the word 'paste', only the icon.... bug?

image
image1073×855 51.9 KB

2 Likes
12

Like the extra clicks to get to the attributes from the entity's modal. It's something I looked at more often than I even realised, until it changed. The collapsed section worked perfectly fine (even though that introduced 1 extra click, I could see the sense in that).

13

With the advent of User first approach for things like card picker, my feedback is that for card picker especially, not having quick access to Paste and manual is a drawback. Since there is a lot of dead space in the dialog header, can we have some quick buttons there for those sort of actions?

15 Likes
14

+1 for this.

Also, swap the tabs over so the default is the 'by card' tab.

6 Likes
15

Hi!
I saw that Home Assistant 2026.6 adds Infrared receiver support:

ESPHome is the first transmitter integration on board, so any ESPHome device with an IR receiver wired up can now act as an IR listener for your whole house.

Does this also work with the Seeed Studio XIAO Smart IR Mate and its built-in IR receiver?

Specifically, can it integrate with the new Infrared receiver entities/events in Home Assistant, or does it currently only support the older ESPHome remote_receiver functionality / learning mode?

Also wondering whether this works with the stock firmware from Seeed, or only with a custom ESPHome configuration.

16

Since it's running ESPhome, then it should work. The integration is based on the firmware, not the hardware.

1 Like
17

Not sure if this only just popped up after updating to this beta but I have this error:

Logger: homeassistant.components.automation.kitchen_downlights_auto_2
Source: components/automation/__init__.py:887
Integration: Automation (documentation, issues)
First occurred: 10:58:12 (1 occurrence)
Last logged: 10:58:12

Error while executing automation automation.kitchen_downlights_auto_2: Unable to set value 6-38-0-targetValue: zwave_error: Z-Wave error 200 - Timeout while waiting for a callback from the controller (ZW0200)

...talking about an automation which doesn't exist. I do have an automation created in the UI with the same name other than not having the '_2' on the end.

I'm guessing I may need to edit a JSON file in the .storage area to fix this?

18

I don’t mind tabs the way they are. I get the intention. Just need new muscle memory to replace typing manual. :rofl: And it’s not clickety clack….

2 Likes
19

AGREE. Seems like every app (phone or PC) I touch I am constantly being asked to do more clicks to do the same thing. It is VERY frustrating. I know everyone is trying to cater to new users (mostly a good thing) BUT some of the changes I see are "for the sake of change" (aka Innovation) and that is a VERY BAD THING.

It is particularly bad on Windows and Home Assistant!

20

I don't mind the default card choice. Whenever I used the UI in the past, I found myself searching for the tile card then replacing the entity. Now I just find the entity and the tile card is there as one of the choices.

Granted, my main UI is 100% yaml, I do not use the UI at all for it. So I'm only creating these tiles for tests or quick 1 up dashboards. All in all, it's a change I didn't know I wanted.

Just my 2c.

4 Likes