I have two Samsung Smartthings Multipurpose Sensors that are clogging up the logbook when they fire events. All it says is “{Sensor name} Attribute Updated event was fired” and no entity is provided or referenced. Below is an example of the Smartthings Dryer Door
I have already excluded all of the related entities in configuration.yaml under logbook exclude and restarted but the messages still appear in logbook.
What is the text that I need to put in the logbook exclude list so that the event firing doesn’t appear?
1 Like
I’m wondering the exact same thing. My logbook is completely spammed with messages from ZHA regarding events fired.
jproios
(Jproios)
November 3, 2022, 2:45am
3
i have the same thing in my logs. has anyone solved this yet?
Jon123
(Jon)
January 6, 2023, 7:11pm
4
Same problem with Aqara door/window sensor (via ZHA/SkyConnect).
teskanoo
(Teska Noo)
February 4, 2023, 7:46pm
5
I raised an issue recently - giving it a bit of traction there might help get the developers moving on a solution
opened 09:52PM - 26 Dec 22 UTC
integration: logbook
integration: zha
feature-request
### The problem
Since I switched from Deconz to ZHA, my logbook is overrun with… entries created by the ZHA Integration
I have found no way to prevent these entries from appearing in the logbook (which makes the logbook very difficult to read)
![image](https://user-images.githubusercontent.com/65863752/209585076-5ec950a0-98c0-4900-826f-180e873d6315.png)
Having over 100 Zigbee devices this results in the Logbook consisting of about 70-75% ZHA Events with the remaining 25-30% being those events in which I have expressed an interest in being reported
I have attempted to exclude ZHA events in the logbook configuration by domain
```
logbook:
exclude:
domains:
- zha
```
I have attempted to exclude ZHA events in the logbook via recorder configuration where I can exclude event_types
```
recorder:
exclude:
event_types:
- zha_event
- zha.zha_event
```
Recorder config, IMO, should be the solution to remove these logbook entries - I can only imagine that I am targeting the wrong event_types, however this is how they appear in my (MariaDB) Database
I have attempted to prevent the logging in logbook by reducing the logging level for the integration (in the vain hope that this might be a factor)
```
logger:
default: info
logs:
homeassistant.components.zha: critical
```
I have verified that this issue occurs regardless of the Enable/Disable debug logging setting for the integration
![image](https://user-images.githubusercontent.com/65863752/209584437-6f7e4c9b-43eb-41ca-9891-cc2470f92f0a.png)
I have attempted to identify in the codebase if and where any recorder and logbook exclusions are taken into consideration when the deciding to log into the logbook
### What version of Home Assistant Core has the issue?
2022.12.8
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
ZHA, Logbook
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
Snippets from recorder and logbook configurations that I have tried to exclude these events from the logbook
recorder:
exclude:
event_types:
- zha_event
- zha.zha_event
logbook:
exclude:
domains:
- zha
```
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
Forum post concerning this matter (which has been present since August 2021 but has not, as far as I can see, been raised as an issue)
https://community.home-assistant.io/t/exclude-zha-events-from-logbook/452501/13
3 Likes