My Blue Series devices send an update through Z2M for all values on the device if anything changes. It’s a lot of data…
It might be me hitting the breaking point then. I noticed it got even worse with the 2026.4.3 update, but I’ve added more Inovelli switches since then. It’s blinking so fast the hovering doesn’t even highlight it anymore.
I don’t understand what you mean by a 0 minimum. You mean the threshold is wrong or something?
I also removed the Apollo Zone Mapper completely, but that didn’t fix anything.
Maybe there’s an easy way to disable all the target-tracking entities for my presence detectors and only enable them when I’m testing something. That’d be pretty nice if that’s actually the cause. How can I tell? Is there any debugging I can do?
The Apollo R-PRO-1 sensors are chatty, but I don’t think they’re any more chatty than the Everything Presence Lite I replaced them with. I could be wrong though. Mine do have an extra mmWave sensor.
The Inovelli mmWave switches don’t push any more data than necessary, but like you said, a single state update may force all entities to update. How are you seeing that? I’d like to confirm if that’s my issue as wel.
There’s something else I forgot about until now. I am using a Zigbee quirk, some Python script, that allows me to have visual entities for a bunch of the mmWave Switch controls. They’re not changing or anything, but there are duplicates of many of them once I added the quirk.
I’m at a loss. I was hoping 2026.4.3 might’ve magically fixed it. I can’t figure out exactly what the cause is or if it’s been happening this whole time and only getting worse. I’d really like a way to debug, so I can start mass-disabling devices to see if that fixes the issue, so I know what’s actually wrong.
It’s very strange that the WebSocket connection is filled with entities that aren’t on the current page. It’s just getting everything.
Also, why those divs are flashing in HTML. That means there are tons of DOM updates. As a React developer, that’s a key sign of something unmemoized. A bug, not a “too many sensors” issue. Something that could be worsened the more state updates you receive. Considering everything else works fine in Home Assistant, I really do think it’s a bug, but I need some way to debug to be sure. Or a place to report it.