Logbook doesn't filter anymore automations

[luca-angemi]

The problem

Automation used to be filter based on yaml config for logbook. Might be related to #36356?

Environment

• Home Assistant Core release with the issue: 0.111.0b3
• Last working Home Assistant Core release (if known): 0.110.5
• Operating environment (Home Assistant/Supervised/Docker/venv): venv
• Integration causing this issue: logbook
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/logbook/

Problem-relevant configuration.yaml

logbook:
  exclude: 
    entities:
       - automation.cuckoo

Traceback/Error logs

Additional information

[dshokouhi]

@luca-angemi seems you missed parts of the issue template, can you please edit your post and supply the requested info under Environment?

[luca-angemi]

My apologies. Updated.

[dshokouhi]

Thank you, knowing its a beta issue is important :)

[cogneato]

Cannot reproduce this on 111.0b3. Are you refreshing the logger page?

Edit: Can reproduce by excluding an automation on 111.0b3

[luca-angemi]

Yes, I refreshed it many times, algo logged from another browser in case of a cache issue.

[luca-angemi]

The filter is excluding properly other type of entities I have excluded such as swtiches, sensors, inputs.
Only the automations seems to be the issue. That's why I referred to that PR.

[cogneato]

Ok, I first tested with any entity, and then added an automation, but it turns out I executed the wrong one, sorry. I can confirm the automation is not excluded.

[frenck]

My current guess is that my PR in #36356 broke this, especially since I've removed a piece from the _keep_event method that filtered this.

I think this needs more general solving, as this probably will affect others that use the async_describe_event (e.g. HomeKit)