Sorry for my delay! I’ll send this to the team. @spamoni4, could you please recreate the failed firing issue and send in a log? Then please give me that log number.
I submitted my logs on 9/2/2020 and received 37751 as the ticket ID.
Hope this helps. However, nothing shows up in the Rules History.
Thank you very much!
I’ve been seeing the same issue, but what’s odd is sometimes my rules with times do fire, other times they don’t. I have mine set to start at 8pm and end at 6am.
So we found 2 work arounds which seem to be pretty consistent. I like @Cap solution as it does not require me to adjust outside of the hours I wanted.
Here is what we found and I sent to @WyzeGwendolyn:
@Cap suggested the following to correct the trigger issue: Do not set the start and end time on the hour or half hour. simply add or subtract a minute. For example: My trigger was set for 8pm to 6:30am, simply changing it to 7:59pm and 6:31am actually made it work.
My initial fix the other day was to ensure the end time was after the start time, if you were to ignore the am/pm. Meaning: if you look at the start time of 8pm and end time of 6:30am and then eliminate the am/pm, the system could see that the start time is after the end time by 1.5hours. This would cause the trigger not to fire as it would think there is nothing to do. I simply changed the start time to 6:00 pm and end time to 6:30am and the triggers fired as expected.
@WyzeGwendolyn I reported this issue with logs last year. Still no fix.
Thanks, I’ll give this a shot and see how it works. Hopefully this bug is on the team’s radar @WyzeGwendolyn. Sounds like it’s been an issue for a while.
yea - as with @Cap, I reported it. So far no fix or feedback yet
Unfortunately adding or subtracting a minute to the start and end times on the rules didn’t work for me, and I tested on two different cameras that have triggers set up multiple times. None of them fired.
Interestingly, triggers that have start/end time with a motion sensor work very reliably, so it seems like this issue may be specific to camera triggers?
I’ll still give setting the start time to an “earlier” time than the end time (ignoring AM/PM) a shot and report back.
Interesting, my issues were with Motion and contact sensors. When I corrected my issues, I actually deleted the old rule and created it again.
This gets more confusing.
@WyzeGwendolyn This issue seems to be a time zone problem, but only with certain rules. I’m in Mountain time, but my triggers scheduled for 8pm don’t work until 9pm, suggesting it’s using Pacific time. Likewise, they are scheduled to stop at 6am but continue to fire until 7am. This is only for my rules that use cameras as the trigger. Rules using sense devices or bulbs work fine.
I tried recreating the rules but no luck.
Thanks for letting me know! I’ll send it over. Any chance you have a recent log I can give the team?
I spoke with the team and we’re still having trouble reproducing this. Could you please answer these questions for us?
- Which time zone are you currently in?
- Have you changed time zones since you set up the Rules in the Wyze app?
- Did you set up camera rules and bulb rules at the same time?
- In US Mountain time (and my phone is set to the correct time zone)
- No I have not changed time zones
- Yes, I set up rules for both at the same time. Both use the same start and end times but only the Bulb and Sense rules trigger correctly. The camera rules seem to be affected by the time zone issue.
I also submitted a log right after triggering an event that should have triggered the rule but did not. Hopefully I submitted that correctly. Ticket number is 43701.
Sounds like you did! Thank you for the prompt response. I’ll give this all to the team!
Eastern time zone
Have not changed time zones
Yes setup all at same time
Thank you! I sent this over as well.
I think I just developed this issue.
Two of my 4 motion sensors in the past few days are no longer triggering time constrained rules to turn on bulbs. The non-time constrained rules to turn off the bulbs when motion has been clear for 15 seconds are still working. This is only affecting 2 of my 4 motion sensors (the other two are triggering time constrained rules just fine). I’ve had these rules in place for over a year with no issue until a few days ago.
The bulbs are working appropriately when controlled by the app and the motion sensors are both detecting. I’ve tried deleting and re adding affected devices and deleting and re adding the rules but it’s still not working. I also tried swapping out the bulb with no improvement. I tried the trick of not using times set exactly to the hour with no improvement. I can’t really make the other solution mentioned above work for the rules as I need them.
I’m located in Mountain time zone and have not changed time zones.
Are there any other known solutions to this problem? It’s very frustrating to suddenly not have my kitchen and hall lights turn on.
I just triggered the sensors that should have turned on my bulbs and submitted log 75908.
Not sure this helps. I recently began testing again with my motion sensors and plugs . I am finding the following:
- the actual rule fires 2 to 4 minutes late on average. so even though I set it for 5pm, it goes off at 5:02 or later.
- The Rule History Menu shows that when a rule fires (mine is scheduled), it actually fires 5 times or so with all being succeeded. at 10pm, I have another rule which functions the same (Runs later than the scheduled time fires multiple times).
Not sure if this is causing all of the sporadic issues we all have been experiencing.
Have you tested the Rule and waited for a period of time to see if it actually fired?
Here is an image with my Plugs on a Schedule Rule. However, as indicated above, the actual time the lights come on is 5:04 or later and the actual time the lights go off is 10:05 or later. In addition, the Rules history will show multiple, 5 or more entries, of the rule being fired and being successful.: