#Prevent automation executions from spamming the logbook

1 messages · Page 1 of 1 (latest)

turbid hedge
#

Hi, I have an automation that is triggered every 30s. So every 30s I get a logbook entry that the automation has been triggered.

Can I disable that behaviour somehow? The logbook page is basically unusable because of this.

unborn forge
#

Could you just not trigger it every 30s? What is it doing?

pallid stratus
#

I think you can exclude domain automation in your logbook settings. I exclude automation at the recorder level.

unborn forge
turbid hedge
# unborn forge Could you just not trigger it every 30s? What is it doing?

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.

turbid hedge
unborn forge
#

Ah fair enough then. Yeah definitely a good idea to filter it out of the logger in that case

turbid hedge
#

Not logger, logbook

unborn forge
#

Logger is the "integration" that controls what goes in the logbook

turbid hedge
unborn forge
#

Great question

#

Try it and tell me when you find out

turbid hedge
#

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

unborn forge
#

Yeah, try the logger instructions I linked

turbid hedge
#

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

pallid stratus
#

on my side i removed all automations at the recorder level...

turbid hedge
#

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

pallid stratus
#

I also removed script, sun, weather, media_payer, .... 😉 😉 😉

unborn forge
turbid hedge
#

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.

turbid hedge