If device logs could show trigger sources, what would you want to be included?

Hey everyone!

Do you ever run into situations where your Aqara devices trigger unexpectedly, and you have no idea what caused it? :sweat_smile:

As I’ve added more devices and set up more automations—and integrated with multiple smart home ecosystems—it’s becoming harder to trace why certain devices act the way they do. Sometimes my lights change color or my curtains open out of the blue, and the current device logs don’t give enough context to figure out the root cause.

That’s why I think it’d be incredibly helpful if Aqara could enhance device logs to show the trigger source behind each action. For example, it’d be great to know if something was triggered by:

  • Manual control via App → Show which user performed the action
  • Automation → Show exactly which automation rule triggered it
  • Scene → Specify which scene launched the action
  • 3rd-party ecosystem → Name the platform (e.g., Apple Home, Alexa, Google Home)

This would make troubleshooting so much easier and help fine-tune our smart home setups without the guesswork.

Has anyone else experienced this? What other trigger details would you want to see in the logs? Curious to hear your thoughts! :point_down:

Hello, I have a pure Aqara, so I immediately go into history when the equipment does something incomprehensible. There are scenarios and automations, as well as a trigger that started the process. Regarding the one who turned it on manually from the application, I doubt that they will do it. (I’m talking about clicking on the device icon from the application).




As an addition, I often correct errors in my automations directly from this log.

2 Likes

Yes, Smart Logs are very useful, and I frequently use this feature myself. However, it’s only effective for tracking device execution triggered by automation or scene activation. For other scenarios—such as manual activation by family members or automation triggered within third-party ecosystems—it cannot provide confirmation.

1 Like

Hello, this is probably quite difficult to implement. I suggested that from each device (plugin) you could go into the history of automation execution (scenes), they wrote off “we can’t do this at the moment, maybe we will in the future”. And this is only an internal archive, what can we say about external factors that we want.
But dreams come true!
We will ask and wait.
Have a nice day.