2026.6: Pick a card, any card

[Mariusthvdb (Marius)]

sweet release, a lot of smaller things to make life better in HA. thanks!

I got to admit, the new entity selection in adding cards for the UI is growing on me, the live previews for the selected entity are really cool. After objecting in Beta, this might even become the best feature for me haha, give it some time... yep. admit.

The one thing I cant get used to is the new columns in dev tools states.

I can see the occasional added value for the Areas and Devices columns, sure, but be default I dont use those and am mostly after the states or the attributes.

I do hope a FR for the optional user selection can be considered, and coming to think of it, re-ordering of those columns.

we have that for attributes, so 2 more wont hurt

[bigmac]

Opensprinkler barked and won't load.... it's looking for pyopensprinkler==0.7.17. Installed via PIP command line but still won't load.....was working fine in core 2026.5.4.

[soleen]

I am trying to use the Z-Wave PIN manager and cannot select custom usernames; it automatically sets them as user1, user2, etc. Is this a known problem?

[parautenbach (Pieter Rautenbach)]

It's not a built-in integration, so you need to report the issue to its maintainers.

[steuerlexi]

I’ve noticed a strange UI issue in the Helpers section (Settings -> Devices & Services -> Helpers).

Several of my helpers (specifically Riemann sum integral helpers like Grid IN, Grid OUT, Battery IN, Battery OUT, as well as some Utility Meters) are now showing a red exclamation mark icon on the far left.

Interestingly, they seem to be working completely normally in the background—data is still processing, and sensors are updating as expected.

Here is what I’ve noticed so far:

• The affected helpers include Integration (Riemann sum) and Utility Meter types.
• Clicking into them doesn't immediately show an obvious error message.
• In the UI, they are currently listed under the "Nicht gruppiert" (Ungrouped) section.

Has anyone else experienced this since the 2026.6 release? Is this a known UI bug, or is there a new configuration requirement / deprecation for these helper types that I missed in the breaking changes?

Any advice on how to clear these warning icons would be greatly appreciated!

[kirell]

I don't get it either. Even on the dashboard, there are constant issues with the non-responsive design. It didn't make sense to assign fixed widths to a design back in 2010, but in 2026, it's a real design flaw. And I thought I was the only one who found this annoying.

As for the “mobile audience” argument—that doesn’t make much sense either. Every phone and tablet has a different resolution. How old is Bootstrap now? It’s a grid system that automatically arranges elements based on available space. But limiting the width of elements everywhere really makes no sense at all... though maybe I’m missing something here.

That’s also one of my biggest criticisms of the entire back-end and front-end of Home Assistant. I hope this gets addressed and fixed soon, because otherwise the system is really strong and I enjoy using it.

[EpicLPer (Stefan Kern)]

I'm still heavily split on the decision to make the new Home dashboard as forced as it is since a few releases now. It's still buggy, when refreshing the whole HA page 6/10 times this dashboard loads up instead of the page I wanted to refresh. I also have multiple people on my HA instance which were, before this option was introduced to be set to "Admins Only", exposed to entities they shouldn't have been seeing suddenly even tho I'm trying my best to hide most entities from them.

I'd really love if HA focuses on multi-user usage next with a proper permission system for each of them, this is becoming a bit of a chore each passing month to keep people in check But please don't get me wrong here, Home Assistant is still one of my most used and loved homelab tools personally!

[zigomatic]

You can select any own dashboard and put as default instead of using integrated dashboard.

[EpicLPer (Stefan Kern)]

I already do, but when the new Home dashboard was introduced it still kept loading up no matter the set default dashboard. I've set my standard user dashboard as the default but 6 out of 10 times it still loads up the new Home dashboard regardless.

[Xornop]

Frustratingly the new template: standard doesn't support climate_template anymore. I use it to have a central climate control entity for all my heaters.
And in 2026.6.1 updating an addon (app) doesn't work anymore.

[LiQuid_cOOled]

A generic thermostat doesn't work for you?

Generic Thermostat

[Passific]

Color customization for graph cards. The statistics graph card and history graph card now let you pick a custom color per entity, both from the visual editor and in YAML.

While I was successful doing so in YAML, I fail to see where I'm suppose to see it in the "visual editor", anyone care to enlight me?

[LiQuid_cOOled]

It's not an available option via the UI editor from my understanding

Statistics graph card

[Xornop]

no, i believe i tried that first but i think the issue was that generic_thermostat doesnt support jinja templating.

EDIT: nope it turns out it is a hacs integration

[dcapslock (Darryn Capes-Davis)]

@Xornop

Frustratingly the new template: standard doesn't support climate_template anymore

It never did. Its a custom integration that used the same format and needs an update for 2026.6.0.

Release v1.4.0 · jcwillox/hass-template-climate

[LiQuid_cOOled]

@Xornop

he issue was that generic_thermostat doesnt support jinja templating

I'll have to verify, but I think

 {% set values = entities 
            | map('state_attr', 'current_temperature') 
            | map('float', default=none) 
            | reject('none') 
            | list 
          %}

is your issue

EDIT: I'm mistaken

[Xornop]

Hehe I guess running so many addons and integrations you lose track of which is default HA and which is custom. Thanks for that!

[petro]

Update the custom integration. Ha never supported climate entities. The legacy removal forced code changes in that custom integration.

[boheme61 (JC)]

@kirell

As for the “mobile audience” argument—that doesn’t make much sense either. Every phone and tablet has a different resolution.

I’m fully aware of that, thou i was referring to i.e the top/bottom menu ( 4 Icons / Elements, so it fits in Mobile ), And i.e 1 Single row(Scroll …) in Both /Settings & /System
It’s Simple and Plain, And from a system-administration point of view, i’ve never seen such bad and plain awful Design, for system-admin-pages
It’s diffidently not something that “sticks out” in favor of HomeAssistant , as a HomeAutomation System , From a System-Admin perspective
Maybe from a “New User” or today’s UI Designers perspective , beats me

Back in the days Max PX in width was Not “recommended” unless Needed, , and yes my dash boards beside testing pages is Grid-Layout ( Custom-Card ) , and it’s not random which “grid-area” turns up where, when i.e reducing browser width, or on different Devices

[bigmac]

Understood, just pointing it out for anyone else seeing the same issue. Already been reported to github.