2025.8 Beta week!

[MissyQ (Missy Quarry)]

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:

• Dashboard/UI/Frontend Issues
• Integrations/Automations/Backend/Core Issues
• Documentation Issues

Here are this month’s Beta notes! July was a longer month meaning we were able to shove an extra week’s worth of work into it!

Here are some things that I think are noteworthy this release:

• AI AI AI - with the introduction of sub-entries in 2025.7, we’re able to build off of that to release AI tasks and Suggest with AI. There’s also a new integration called OpenRouter with access to over 400 extra LLM models.
• Control individual members of a group - the entity information dialog for light and cover groups now shows the individual members of that group.
• New integrations including OpenRouter as mentioned above, Ubiquiti UISP airOS, and a couple others.
• Noteworthy improvements to existing integrations - PlayStation Network got a ton of updates, Reolink gets more enhancements, OpenAI Conversation supports camera and file attachments (to go with AI Task), WiZ supports fans, SwitchBot Cloud also gained fan support, SmartThings added vacuum support, Pi-hole users can leverage API v6 functionality, and so much more.
• We’ve had 9 integrations achieve new quality scale levels - Amazon Alexa Devices keeps moving up that list, but special congratulations to those who made it to Platinum status: AirGradient, Discovergy, EHEIM Digital, and Pegel Online.
• Other noteworthy changes - a new absolute humidity device class was added, group management has been greatly improved, History Stats now includes a preview in the options flow, and more updates to the Template integration from the amazing @petro (if you use the Template integration, these changes are probably important to you!).

There is a hefty list of backward incompatible changes this release that some of you may want to know about - Apple TV, Ecovacs, Reolink, Templates, UniFi Protect, and Z-Wave are the big ones I’ll call out here, but there are more.

Build should already be available for y’all. Happy testing, friends!

[Mariusthvdb (Marius)]

wow this is empty still…

let me add my observations up to 2025.8.0b1

after an initial fluke with the new buttons without text, .1 fixed that, and we now have new buttons working as per new design.

Those still need some fixes here and there regarding their position and color setting

but all in all, it seems ok. In Default theme that is.

If you have carefully curated themes, as many of us do, you’re stuck with really nasty color clashes, because of the introduction of

src/components/ha-button.ts

and

src/resources/theme/color/semantic.globals.ts

Ive asked for some explanation which semantics is used where, as currently it will take some effort to untangle that spaghetti of new theme variables… and do:

1. So just set all of these core primary colors. And the semantics are build up on them

    --color-primary-05: #001721;
    --color-primary-10: #002e3e;
    --color-primary-20: #004156;
    --color-primary-30: #006787;
    --color-primary-40: #009ac7;
    --color-primary-50: #18bcf2;
    --color-primary-60: #37c8fd;
    --color-primary-70: #7bd4fb;
    --color-primary-80: #b9e6fc;
    --color-primary-90: #dff3fc;
    --color-primary-95: #eff9fe;

2. [07:30]

This is the beginning of our design system. We just use it for buttons now. But when we hopefully sometime use it on most parts of the software it will be really cool.

This is only about looks

more serious trouble I experience with the new functionality of the group members on the more-info of grouped helpers. Lights and Covers show their members as tiles, which seems very cool indeed!

If it didn’t grind the interface to an almost standstill…
Interaction is very very laggy in my setup, even on helpers with only 2 or 3 members.
I have to manually reload the view returning from those more-info panels, otherwise I am stuck with

Btw this also occurs on the other helper groups, as Ive documented in this issue more-info group functionality very slow and lagging interaction · Issue #26325 · home-assistant/frontend · GitHub

That’s mostly it for me, my use case doesnt benefit from the other changes in this release.
Although I do love the fact we can now add availability templates via the UI Helpers, thanks to Petro!

O, and 1 more titbit: use ha-button-radius in your themes to get rid of those rounded button blobs, my theme is squared mostly, so I set those to 0px, or more precisely I use:

    ha-card-border-radius: 0px
    ha-dialog-border-radius: var(--ha-card-border-radius)
    ha-config-card-border-radius: var(--ha-card-border-radius)
    feature-border-radius: var(--ha-card-border-radius)
    ha-button-radius: var(--ha-card-border-radius)

[Olivier1974 (Olivier Toussaint)]

Hello there,

As usual, I’ve installed the beta of 2025.8
The “blue” is gone …

[stefan1982 (Stefan)]

@Mariusthvdb

If you have carefully curated themes, as many of us do, you’re stuck with really nasty color clashes, because of the introduction of

frontend/src/components/ha-button.ts at c2ca556151194555cf665d78341297173defa4a7 · home-assistant/frontend · GitHub

and

frontend/src/resources/theme/color/semantic.globals.ts at c2ca556151194555cf665d78341297173defa4a7 · home-assistant/frontend · GitHub

Ive asked for some explanation which semantics is used where, as currently it will take some effort to untangle that spaghetti of new theme variables… and do:

1. So just set all of these core primary colors. And the semantics are build up on them

    --color-primary-05: #001721;

--color-primary-10: #002e3e;
--color-primary-20: #004156;
--color-primary-30: #006787;
--color-primary-40: #009ac7;
--color-primary-50: #18bcf2;
--color-primary-60: #37c8fd;
--color-primary-70: #7bd4fb;
--color-primary-80: #b9e6fc;
--color-primary-90: #dff3fc;
--color-primary-95: #eff9fe;

2. *[*07:30*]*



This is the beginning of our design system. We just use it for buttons now. But when we hopefully sometime use it on most parts of the software it will be really cool.

This is only about looks

Now… How does that work on overriding?
I’m not able to find any documentation on the :host([***]) part, or in the CSS docs?

Why is --color-primary-** hardcoded in true hex-color-codes? Why don’t use 1 primary-color and use HSL to do the variants and mix with more or less shades and shifting of white/black?

[francisp (Francis)]

Noticed it too

[Mariusthvdb (Marius)]

as is explained in my post

[Mariusthvdb (Marius)]

@stefan1982

I’m not able to find any documentation on the :host([***]) part, or in the CSS docs?

you dont need that, you should only set this color variables in your themes, and they will be applied by the frontend accordingly

however, it is not yet very clear which color is used where, and that is why I asked for some extra documentation

Check this discord link, you can see that they will try to add something.

[Mariusthvdb (Marius)]

there is a lot to do about the Visualization of the Zwave and Zigbee networks. Suffice to link to the issue and not repeat all that.

[sparkydave (🇦🇺 Dave)]

I don’t see anything in my logs relating to this but for some reason on this beta it would appear that none of my Xiaomi zigbee buttons work. Other zigbee devices are fine. Anyone else having the same issue?

[Mariusthvdb (Marius)]

yeah, I believe Missy and others noticed their devices not being functional, next to not being visualized. Not sure if an issue was raised yet

[chimeranzl]

FYI, 2025.8.0b1 breaks my zigbee IR blaster. It’s effectively a ZS05 with custom quirk as per Tuya Zigbee Infrared Blaster ZS05 Review - SmartHomeScene

With the beta version installed, it doesn’t respond to reading ‘last learned code’ attribute from the device. Rolled back to 2025.7.3 and it works again.

EG: doing this returns no value (value shown when running 2025.7.3)

Unsure if the same applies with other zigbee devices.

[chimeranzl]

yes. as per my above post + now you mention it the buttons on my zigbee switch to open/close blinds failed to work.

i’ve since rolled back to 2025.7.3 and its all good again.

[Mariusthvdb (Marius)]

see GitHub · Where software is built for what has been raised, please add if you have additional info

[sparkydave (🇦🇺 Dave)]

2025.8.b2 fixed it for me

[francisp (Francis)]

2025.8.0b2 has a strange integrations screen

[Mariusthvdb (Marius)]

you sure you refreshed cache, this is what I am seeing

however, you’re bringing up a valid point: the new (button) theming in the color variables. the consequences are huge.
Unless you only use default theme. Personally I have 4 main themes that are used in various states of the home, and depending on sun up or down.

in the current state of affairs, those bright blue buttons show in all of my themes. 1 example

Upon request, Wendelin was kind enough to add some text in the resource file, but that doesnt really help us to fix our themes.

imagine we now have all of this

and more for that single button, and there is a serious amount of extra variables for other types of buttons, let’s not forget the other frontend elements, see Add color palettes by wendevlin · Pull Request #26271 · home-assistant/frontend · GitHub

Again, I am appreciative of the fact the Frontend needs modernizing. This is a real breaking change though and imho requires a serious bit of documentation, in the Frontend documentation, not only inside the resource file itself

[francisp (Francis)]

Picture coming from Firefox in incognito window, so cache should not be a problem.
ctrl-F5 does not help

[Mariusthvdb (Marius)]

Odd, this is supposed to be fixed (.0 suffered this) so if you really updated to .2 now and still see it I guess you should add that to the closed issue

[petro]

Are you running the default theme?