2025.7 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! Even with just two weeks of engineering work time since the last release to this beta, 2025.7 has a ton of quality of life updates that make the UI just that much better (at least in my humble opinion).

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

There are a few backward incompatible changes this month that some of you may want to know about but they will likely not impact most of you much.

Build should already be available and there are already adjustments being made based on testing in Discord. :clap:t2: Happy testing, friends!

4 Likes
3

Just installed the beta. No issues at the moment.

4

No functional feedback, just a small thing about the documentation, specifically 2025.7 Beta: That's the question - Home Assistant

Sometimes the entry starts with the name of the integration, sometimes with the person who made the change. Always starting with the integration name would improve the readability for people quickly flying over the release notes to find out if something relevant for them is mentioned.

2 Likes
5

Where is the correct place to report bugs?

I reported on the link below, but there are more than 2500 bugs reported marked as “Open”.

6

Right there. Issues tagged with the beta version are added to the beta milestone.

7

Since only one of 2,600 reports is actually marked as a bug, it seems humanly impossible to manage the remaining 2599 :pensive:

Screenshot_20250626-193120
Screenshot_20250626-193120626×637 60.3 KB

1 Like
8

The issue tracker is only for bugs. They are all bugs. Ignore the label bugs.

9

No issues for me on this beta other than a 3rd party Google Home Integration which has been logged on it’s Github already.

10

2025.7.0b3/b4.
Ollama has disappeared from the integrations page, and all conversation agents added through it are gone.
Attempting to re-add the integration results in a message stating that the service is already added.
It turned out that it had been deactivated and hidden.

But integration has been thoroughly broken; only one model can be added from one server.

2 Likes
11

Please be aware that B3 is buggy for many instances, and shouldnt be updated to.
It seems to be related to Unifi Protect Integration, so if you’re not running that, you could still try… :wink:

do
ha core stop
ha core update --version 2025.7.0b2
ha core start

if you already updated to B3, and are experiencing trouble: disconnect/restart no frontend etc

give it a bit of time between commands, the stop is essential…

see Discord #beta channel from Discord

1 Like
12

I don’t have Unifi equipment, and 0b3 runs fine here.

13

great. your one of the lucky ones :wink:
Rest issues were also reported, which havent been figured out yet. Be sure to check those if you use them

14
  • Device and entity management got better! @emontnemery made it so Home Assistant now restores user customizations when you re-add deleted devices or entities. No more losing your carefully crafted names and settings

What to do if I would need to start from scratch?
Such a need happened to me several times when developing scripts or playing with devices.

Also if HA got lost (ie during reflecting device rename into entities), device removal and readding it was the best option.

1 Like
15

Fix is coming in

for the often reported segfault issue, not sure yet if this will also see to the Go2rtc endless loop issue, as that doesnt mention segfault at all

update

meanwhile updated to B4, and all seems well.
no segfault error in the logs, no disconnects. Frontend stable.

16

Did anyone noticed strange transparency issues when edit card in fullscreen (in beta4)? All is there at the same time: basic HA page, fullscreen editor and edited card. I can write in fullscreen, and changes are reflected in that smaller card window, but there’s no “save” or “cancel” button active. CTRL-S works, though.

HA restarted, HAOS restarted, cleared cache and hard-reloaded.

image
image3829×1935 222 KB

17

Yes, its happening to me too.

1 Like
18

Yes, same here. Started in beta3, just updated to beta 4 and still happening.

1 Like
19

Yes, getting this too, only in Dark Mode.

2 Likes
20

I just noticed that there is no way to select a particular camera for the background in the new Area card. You can select ‘camera’ as the background but not select the camera entity, only end up with a HA auto-selected one… my area has 2 cameras and it simply selects one of these with no option to override it.