I have a cube controller and a T1 LED strip. Within the aqara android app automations section, I’ve set up timer automations for my son that start with solid green, decrease to 3/4 length and change to yellow after a quarter of the time has passed, decrease to half length lit and orange when half of the time has passed, etc, until all of the time has passed and the whole thing blinks red for 1 min before turning off. I use wait conditions to control the amount of time between color changes. The face of the cube that’s turned up triggers the automation and determines the length of the timer (5, 10, 15, or 20 min). The 5th face turns off the light and disables the 4 timer automations. The 6th face turns on the whole strip solid white and re-enables the timer automations. This all works as expected except turning off the light mid timer automation using the 5th face of the cube. The light goes off, but the timer automation continues to turn the strip back on once a wait condition is met even though the automation is disabled. Is this expected behavior? If so, what’s the proper way to stop a running automation?
@newkirkfamily2011 It sounds like you’ve set up a creative and fun automation routine with your cube controller and T1 LED strip! Based on the reference information available, it appears that automations in the Aqara app may continue to execute if they are triggered before being disabled, which is why you’re seeing the LED strip turn back on despite disabling the automation mid-timer.
In your case, the automation likely continues because the “wait” conditions have already been initiated before the automation is disabled. Unfortunately, the current reference information doesn’t specify a way to halt an ongoing automation that has already triggered.
To stop a running automation effectively, you might need to consider:
-
Adjusting the Automation Logic: You could add an additional condition in your automation that checks the state of the cube face before executing each step. This way, if the face changes to the one that turns off the automation, it also stops any further actions.
-
Manual Intervention: You might need to manually stop the automation from the app if it continues to persist even after attempting to disable it with the cube face.
I recommend checking for any updates in the Aqara app as new features or bug fixes might address this behavior. Meanwhile, let’s open up this discussion to the community to see if anyone else has found a nifty workaround!