Logbook upgrade - what is changing the states

Been using home assistant since 2016 and my config files are massive and broken up into packages and it works great BUT when something starts happening it means that I have absolutely no idea what it is that’s causing it to do it. Is it someone on the app messing with me? is it an automation based on the plethora of sensors that i actually wanted to happen at some point? or finally something that ive done that i didn’t intend to happen?
The logbook shows what has happened (if it loads at all) but not how that action was triggered (switch, automation etc)

Is there a way that i can find this information out? instead of looking at all my automations and seeing which was triggered roughly the same time and then finding out what actions that automation carries out?

If not, is there a way i can add a feature request?

Thanks in advance,
Sam

The only way to find and see what caused the triggers is to use the debug log:

logger:
  default: debug

Debug will show all triggers and events. But it is verbose. I don’t recommend keeping it on for long, your .log file will get huge.

If you have ssh access, you could capture the output of a command like

journalctl -u [email protected] -f

But beware, this outputs a lot of Information. You’ll need to be able to parse all that info.

You can pipe the output and look only for specific events by adding | grep -i

journalctl -u [email protected] -f | grep -i broadlink

will output only events related to broadlink devices:

2 Likes