A member reported that one H2 long press disarmed an alarm and was followed by Away mode turning on; their app activity attributed Away mode to the press. That record alone doesn’t establish which rule, scene, or other source caused the second change.
If this happened in your home, what would you check first? I would want an event trail that connects the input event to each matching automation or scene, shows any manual or remote mode change, and separates a command being sent from the resulting mode being confirmed. Is there a reliable way in Aqara Home today to trace a mode transition back to its exact source? If the current log falls short, which missing detail would help most?
My own setup is Home Assistant, so I can’t confirm an equivalent end-to-end trace in Aqara Home. If HA is involved in the mode change, I’d inspect the Traces view for each automation that can change that mode at the incident time. The official documentation explains how traces record the trigger, condition results, executed action path and the configuration used for that run. That only covers HA’s runs, not logic executed entirely inside Aqara.
I’d save the incident’s traces before editing anything, then compare the action timeline with the alarm entity’s reported state changes. A completed action is not, by itself, confirmation that the requested mode was reached. For Aqara’s activity view, a useful addition would be separate timestamps for the command request and the reported mode change, linked to the exact automation or scene run. I’d investigate existing records first rather than repeatedly switching a live alarm just to reproduce it.