Exclude ZHA Events from Logbook

Configuration Zigbee
1

Is it possible to ignore any ZHA events from the logbook? I added ‘zha’ to the excluded domains, but ti doesnt seem to be working.

1 Like
2

Anybody have any ideas?

1 Like
3

Same here, its anoying and messing up the Logbook with spam from ZHA.

4

Is there not anybody else who are anoyed by the fact that ZHA is spamming the logbook?
Wish there was someone who could fix this.

image
image830×949 70.1 KB

Since the 2022.6 Logbook update (I believe) it brought in these attribute event updates. There are literally thousands of these over the past couple weeks, hundreds per day. As they are not selectable to see the event entity id, I can’t add them to the ignore list of logbook.

Does anybody have an idea on how to completely ignore these events in logbook?

1 Like
5

Anyone have any luck with this?

1 Like
6

Hi,

Anyone? I’m still getting a shitload of theese in my Logbook.
Would really appreciate a solution for this.

image
image1046×900 73.9 KB

7

If I remember correctly, when you exclude something from recorder it also excludes it from logbook.

Recorder has an option to exclude by event type. I think that’s worth a try.

8

Hi,

I tried this, but ZHA Atribute is not something i could disable. Its like its injected directly into the logbook.
All other lines in the logbook has a clickable entity wich leads to the integration it comes from except this ZHA Atribute wich is like a ghost in my logbook.

9

Still no one with a solution to this?

10

Hi Andre,

I have successfully managed to exclude [edit - SOME OF ] these ZHA Events as follows


recorder:
    exclude:
        event_types:
        - zha_event

Hope this works for you

Merry Christmas

11

Recorder is different than logbook

12

Recorder - Home Assistant (home-assistant.io)

If you only want to hide events from your history, take a look at the history integration. The same goes for the logbook. But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the exclude /include options of the recorder integration. That way they aren’t even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like sensor.last_boot ).

13

Thanks eggman…

I opted for Recorder as Logbook has no option to manage events whereas settings defined for recorder cascade down to logbook

Sadly my solution only appeared to work on first glance of the logbook entries - after a short period of time (15-20 seconds) the ZHA events started to weave themselves back in amongst the core logbook entries - they seem to be getting pulled into the logbook via a separate process then interleaved into the results

It seems that the ZHA Integration blatantly ignores the settings in the recorder

image
image959×261 22.2 KB

14

You should probably look to see if there’s an issue raised already, and if not, raise one

1 Like
15
2 Likes
16

Schrödinger’s Recorder…

Your solution seems to work. ZHA events are not recorded. When you open the Recorder, only the other types of events appear. After a few seconds, the ZHA events begin to appear again.

… curious…

17

You are excluding it from the recorder, which is different than (but related to) the logbook

18

I have this issue, too.

I was hoping I could use exclude entity_globs but that doesn’t work.

exclude:
  entity_globs:
    *Attribute Updated event was fired

You can’t start the thing to exclude with a wildcard.

I looked at the topic on github linked above and there are suggestions, but none of them sound quite like what I want.