WTH - Why doesn't the Logbook show what triggered an event?

From time to time, some of my RGB devices (WLED based) turn on for seemingly no reason. Unfortunately, the logbook doesn’t show what triggered the action. Would be great if the Logbook could show what, if anything, triggered a given action, script, or status change.


If no context is given in the logbook that means it was not:

  1. A user from the dashboard, or
  2. An automation or script.

Which just leaves the physical device itself. Either someone/something operated it directly via the WLED web interface or API or it reset for some reason and you have it to default to the on state.

Well I must have ghosts in my house then. I was minding my own business in the room when the above device turned itself on. The physical on button is out of reach and the wireless remote was sitting on a table in front of me. No one else is home and these lights aren’t exposed externally. Spooky!

What other services are your lights attached to? Outside HA

More a FYI in case related: I had this issue with a couple of Bulbs (a Lifx & Yeelight bulb). They would mysteriously turn on. Might occur once a week or even a month might go by without the issue. Very annoying.
It wasn’t reset related as mine are set to “last position”…and I tested for that. In my case, I blame GoogleHome as I had them added there. Unfortunately nothing showed under “GoogleHome Activity” so couldn’t be 100% certain.
Solution: I removed the linked service and has never occurred since. That was over a year ago hence the reason I blame it.

I never got to the core cause as I added them to a different Google Account and over time (weeks/months), the same issue reappeared. I asked Lifx Support about it and their logs noted a trigger but they couldn’t tell me exact source so gave up!
Shame as they were two devices that I was ok with allowing GoogleHome to control via “HeyGoogle”.

Technically, WLED can control the lights. Aside from that, nothing else outside of HA.

Do you have an infrraed receiver for your lights? We found that the IR form our tv remote would trigger our LED light strip but only when we pressed the number 9. It took us a while to figure it out as we didnt hit 9 very often.

Go to Config → LED Preferences and make sure this box is unchecked:
Screenshot 2024-12-09 at 13-00-18 LED Settings

Interesting suggestion. I’ll test this out and see what happens. This is one of five, identically configured Dig2Go RGB controllers in the same room so I’m interested to see the results.

Regarding IR, the IR receiver is disabled on all of my Dig2Gos.