adibou
(adibou)
June 13, 2024, 11:58am
1
Hi
My logbook is completely spammed by my occupancy sensors, and I can’t manage to exclude them from the logbook.
Here is what my yaml looks like :
logbook:
exclude:
domains:
- binary_sensor #I guess this should do the trick but it doesn"t
- sensor
- group
entity_globs:
- binary_sensor.presence* #also tried to double down as all occupency sensors starts with the same id, still no success
include:
domains:
- automation
- climate
- cover
- sun
- input_boolean
- weather
- button
- input_button
- script
adibou
(adibou)
June 19, 2024, 2:50pm
2
Can anybody help me please, it is driving me mad
Troon
(Troon)
June 19, 2024, 3:00pm
3
I assume you don’t actually have the comments in the YAML as above?
Are you sure you only have one logbook:
entry in your config?
adibou
(adibou)
June 26, 2024, 11:58pm
4
actually, I found out that it is a known issue with no workarounds being developped at the moment
opened 07:40AM - 21 Oct 22 UTC
closed 05:05PM - 23 Dec 23 UTC
integration: logbook
stale
### The problem
I have a few excluded entities from the logbook integration whi… ch still show up in the logbook view as it seems the exclude filters are not being applied.
Using packages to split the configuration:
```
homeassistant:
packages: !include_dir_named packages
```
And the logbook integration is configured under _config/packages/system/system_logbook.yaml_.
Here's the excluded entitities showing up in logbook:
![logbook](https://user-images.githubusercontent.com/47672949/197140535-c3e8cea4-e8dd-490d-9e0c-afb8e7bcf7a5.jpg)
### What version of Home Assistant Core has the issue?
2022.10.1
### 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
logbook
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/logbook/
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
logbook:
exclude:
domains:
- group
- weather
- device_tracker
entity_globs:
- sensor.accuweather_*
- sensor.openweathermap_*
- binary_sensor.rf_motion_*
- binary_sensor.paradox_<serial_omitted>_zone_*_open
- light.*_off_lights
- light.browser_*
- switch.schedule_*
entities:
- sensor.security_last_motion_index
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
Then probably the issue should be recreated (or reopened) if you are sure that this is a bug.
adibou
(adibou)
August 23, 2024, 4:09pm
6
don’t really know how to do that properly