Attributing device actions

🎬 Get Started
1

Evening all.

A random question, I've had a quick search around the forum and scratched my head a fair bit but can't seem to fathom this.

Is there an easy way to identify why a device has just done something?

An example. Sat in the lounge tonight and one of the wall lights (two zigbee bulbs, usually controlled as a group) turns off. Check the logs, look at the device and I can see that the bulb switched off at %time_stamp but no information as to why it was triggered. While the lighting mesh is controlled by a hue hub all logic is on the hubitat and there's no obvious way to see what it was that suddenly decided to turn off one member of the group. None of the rules attached to those lights were in effect at that time.

Am I missing something simple?

2

i have not found anything,. it would be a nice feature.. what i have done if not too long after is look at the device events note the time and then goto past logs , select all and scroll down to that time and see if there is any other relavent logging.. if logging was not on for the rule, or app at the time you are probably sol,, turn on logging for any apps and rules that touch the device and wait till it occurs next time.. (the list of rules and or apps that a device is used in is at the bottom of the device handler page)

1 Like