Regression - Turn On For x Minutes

Sensors
, ,
1

I have a rule attached to a motion sensor that triggers lighting for 15 minutes.
For months, it has been working flawlessly.

Recently (about 3 weeks ago), it started behaving by not enforcing the “stay on” delay properly. It appears to be “on” for about one minute only.

I deleted the rule, recreated it with no luck.
I also observed that sometimes, when going back to the rule, it was not saving properly the delay I set - reverting to 1 minute.
Now, it appears to be properly saving the rule but still, the delay set is not respected.

This is an extremely annoying regression as I use this automation to control lighting in a dark area. Having it turning off every minute is a pain.

2

Wyze must have broken the “turn on for X” action on the server. Until Wyze fixes this, separate turn on and turn off actions. Change your current action from “Turn on for X” to “Turn on”. Create a 2nd Automation Device Trigger to cover turning off. Set trigger to your bulb (or bulb group) with “has been on for X minutes” and action to “Turn off”.

1 Like
3

Yes, evidently a new bug. It’s unfortunate the Wyze development process was unable to spot this evident regression.

Thanks for the alternative solution. Not as simple as the “real” way but working fine.

1 Like
4

The Wyze dev team is looking for app logs to help debug this issue:

I plan on sending a few logs sometime today. If you wish to help expedite a fix, please send an app log file and post Log ID in this topic and tag @ WyzeDesmond. If not, no problem… they should be able to find the issue with my submissions.

1 Like
5

I’ll try to repro and get the log.

Meanwhile, since it appears to be a server side issue, I doubt the client side log will be useful.
Also, it’s so easy to reproduce, I wonder why they haven’t figured it out yet.

2 Likes
6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.