core: Unable to (find a way to) Exclude ZHA Events from Logbook

Issue is still present on 2023.11.0rc

Bump. The only reason that hasn’t been any activity on this lately is because we’re still waiting for the development team to chime in with their diagnosis.

Still ongoing on both web and phone.

+1 this issue, the lack of exclude filtering for the logbook in the ui, either temporary or ‘save preferences’ style, makes it very difficult to track a series of events and limits its usefulness. Now that I have a fairly large zigbee network I’m finding zha checkin event spam to create a ton of noise.

FWIW, I’ve managed to remove most of the ZHA stuff in the logbook with these bits of config. There’s still the bug where if you’re watching the live logbook update the ZHA events will appear, but they then disappear if you refresh the view, but I find this liveable-with.

The “logbook” section removes any events that don’t have a recognised filterable domain, so it’s a catch-all, and may remove some other events that you do care about…

recorder:
  exclude:
    event_types:
      - zha_event

logbook:
  exclude:
    domains:
      - logbook

Vote for it, that is annoying

+1 also having this issue. Would love to get these out of the Logbook

@luke7101 I’ve found most common blueprints for ZHA switches are always triggered by these update events also, but the logic within the automation means no action is taken. I’m not sure what kind of overhead this creates but similarly to the logbook it can spam automation traces making it harder to get useful info.

Why limit this to ZHA events? It would be great if we could click an event and ignore, trash, snooze any line item. Maybe

HA-PC-1 System Uptime changed to 29:16:22:25 2:50:22 PM - 2 minutes ago

HASPone p[2].b[4] displays a clock with a clock icon triggered by time pattern 2:50:00 PM - 2 minutes ago - Traces

Current logbook behavoir is that when I do a page refresh the ZHA and Hue events which should not be there are gone from the logbook. They are not written to the DB so the recorder ZHA and Hue events exclude works. So only in the live feed. This was discussed last year in another thread leading to #72728

Thanks doekwerk - you nailed it there

These events were definitely being added (interwoven) into the logbook AFTER the logbook page loads - it is something to do with the “previously introduced live logbook” mentioned on this page

https://rc.home-assistant.io/blog/2023/01/25/release-20232/#streaming-history

That does seem to be the case, although I would still like them to not be there

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (logbook) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

logbook documentation logbook source _{^{(message by IssueLinks)}}

I noticed that with @AndreFjeld and @Teskanoo have Zigbee motion sensors that appear in the Logbook. With me it is only the Hue switches that appear unwanted in the Logbook. My motion sensors and lights do not have this problem. They are in the domain light and binary_sensor. My Hue switches however are in the zha domain and are stateless devices. They cause an zha_event. These switches don’t have an entity as such only for battery, update and binary_input. Since it has no entity we are not able to exclude it…

Hope someone knows how to change that.

+1 dito

Hey there @dmulcahey, @adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

zha documentation zha source _{^{(message by IssueLinks)}}