2026.8 Beta week!

[tom_l]

There is a link here to the Discord server where the beta developers hang out and assist with issues: https://www.home-assistant.io/faq/release/#helping-test-the-next-release

Also have you tried clearing your frontend cache?

[mundschenk-at (Der Mundschenk & Compagnie)]

Yes, this will be terrible with Powercalc

[tom_l]

@Mariusthvdb

or mold indicator.

I have a bunch of the sensors set up. I’m not seeing any issue?

[GregoryWest]

Oddly enough, cleared cache, and 4 reboots later everything came alive

[Mariusthvdb (Marius)]

well, can explain either.
I also have 3 of those, and only 1 popped up.

as did 5 covers all of a sudden, like these

which is even more or a mystery as they dont contain any batteries. After having had a more thorough look, I still cant find how these were discovered (besides the inexplicable fact this happened only after having restarted more than 20 times this beta..)

I would hope some logger would be added so we can find why these discoveries happen

[tom_l]

Are they Bluetooth sensors?

All my temperature and humidity sensors used in my mold indicator integration sensors are from ESPHome. No extra discoveries for me.

Battery notes appears to be a 3rd party integration. You should take that issue up with them.

[Mariusthvdb (Marius)]

Battery Notes Issue seems found

Was a newly included device definition in their library which falsely identified these mains devices as battery devices

Author took measures to fix

As for the mold indicator, yes I have one of those . But also a Matter device and a Hue integration sensor

[uschindler (Uwe Schindler)]

Hi,

It would be great, if the Home Assistant Cloud page could be hidden completely. If you don’t use those features and gave a local installation with local reverse proxy, having it on top of the list is just annoying.

So best would b
To habe a checkbox to hide it, if not enabled. To Allie you to re ert back a setting under system to revert it would be fine.

Uwe

[uschindler (Uwe Schindler)]

@Participant

Not a fan ot this; I’ve got many devices exposed through multiple integrations (most commonly Unifi + native device, but there are others.) Being able to see all the entities affiliated with a single device is useful (is a button or sensor unavailable because the device is disconnected from the network?) having to jump around to different integrations sounds like a step backwards in usability. If anything, I’d want a greater ability to merge devices so that integrations that aren’t able to get auto merged due to differing identifiers could be put together (ex: ADB and bravia integrations for a sony tv.)

Yes, this is annoying. Please allow multiple integrations to show as one device. If the integrations habe incompatible device, i’d suggest to add a “manual merge”.

The problem is: often devices are on different granularity. This was also a problem with the “automatic friendly name” which was — good luck — reverted. I just also want entity names be completely detached from devices. Often you gave just compound devices like Zigbee switches with 4 channels controlling devices in different rooms. The entity friendly name should be named without device name. And therefore I’d like to add a single entity from a compound device and add it to another device: like if I have a switch to turn off power from the tv, I may want it part of the tv device!

Uwe

[Mariusthvdb (Marius)]

@mundschenk-at

Yes, this will be terrible with Powercalc

My guess is it wont be as bad as you fear…
in my rather extensive Powerful setup, there was not a single issue, and author is well aware, and made precautions so using profiles with devices wont cause false discoveries

[Mariusthvdb (Marius)]

@Mariusthvdb

Battery Notes Issue seems found

Was a newly included device definition in their library which falsely identified these mains devices as battery devices

Author took measures to fix

As for the mold indicator, yes I have one of those

as it happens, is seems that HA migration didnt take care of removing the entries from the device_registry as it would have.
so they were discovered anew.

taking them out manually solved my issues, but of course that should not have happened.

I reported as such in the beta channel

[tmatheussen (Tom Matheussen)]

Due to the device splitting, for some reason all my WLED automations raised repairs (thanks to Spook ) stating the device didn’t exist.
Simple fix just picking the correct device again for each automation but I’m not sure if this is a known issue or not. Couldn’t find any WLED related change on the changelogs, previously these devices were also linked by Unifi (which actually caused the uptime sensors to keep switching between WLED uptime and Unifi uptime), in case that helps somehow

EDIT: It seems when devices are split, they get replaced with new ones. I updated the first batch of automations before reloading my browser, now after reloading I see a ‘replaced device’ selection, so it’s actually easier than I thought!

[NathanCu (Nathan Curtis)]

@tmatheussen

: It seems when devices are split, they get replaced with new ones. I updated the first batch of automations

Thats going to be fun… Not.

[petro]

There should be no manual updates, it should automatically transfer over.

[tmatheussen (Tom Matheussen)]

None of my other previously merged devices had the issue, only the WLED ones.
All of the things I needed to update were Automation actions, specifically Turn on/turn off lights targetting the whole device (all the devices consist of more than 1 segment).
I’m not sure anybody else already encountered this issue or not

[MissyQ (Missy Quarry)]

AND WE’VE REACHED THE END!

2026.8 is now released. Please head to the release blog thread to continue any feedback regarding this release.

Thanks, y’all!