#Prevent automation executions from spamming the logbook
1 messages · Page 1 of 1 (latest)
Could you just not trigger it every 30s? What is it doing?
I think you can exclude domain automation in your logbook settings. I exclude automation at the recorder level.
it's a keepalive. it's publishing a mqtt message so that another device can see that and keeps publishing its mqtt stuff. If I don't do it every 30s the other device will stop updating the data via mqtt and only start again when I send the message again. I have no control over that other devices behaviour sadly.
ohh, I did not think to check the logbook integration itself. I can see that I can exclude entities, so I shoudl be able to exclude that specific automation, thanks!
Ah fair enough then. Yeah definitely a good idea to filter it out of the logger in that case
Not logger, logbook
Logger is the "integration" that controls what goes in the logbook
hm, than what is the logbook integration doing? https://www.home-assistant.io/integrations/logbook/
Ok, so this does not work:
logbook:
exclude:
entities:
- automation.victron_mqtt_keepalive
Logbook still shows that automation triggers.
excluding it from the recorder works, but that of course also does not record anything anymore
Yeah, try the logger instructions I linked
and how should I set those up? IMO this is not logging related.
anyway, it works by exlcuding it from the recorder, so that's fine for me
on my side i removed all automations at the recorder level...
Yeah, I don't want to go that far. Excluding only that specific automation also works
But now I have to investigate why the exclude on logbook does not work, according to docs it should be on top of the recorder exlcudes
maybe it's just buggy
I also removed script, sun, weather, media_payer, .... 😉 😉 😉
Follow this link
Yeah I did. It shows how to configure log filters for integrations. I'm not talking about log entries. There are no log entries that I want to filter. I'm talking about the logbook, which shows state changes.
ah! this does work! I had selected the logbook for that specific automation entity on the page and that took precedence over the exclude in the config. If viewing the whole logbook that automation is excluded as expected.