While I agree it’s a cloud to client issue, the only problem I see with this theory is that I moved a schedule to a time 2 minutes into the future and it still skipped then moved it again 1 minute into the future and it worked. The schedule should have reset the cancel reason both times but for some reason still skipped the first time.
The only other theory I have at the moment is if they’ve set this up to check every minute for what schedule should trigger and something slows the server down and it doesn’t finish all schedules within the minute. The next minute it completely cancels the minute it was working on and starts sending commands for the current minute. Of course, this would assume only one active server and that it’s set up in this manner instead of some more fluid system
However, it could also be that our issues are slightly different. In fact, I’m starting to think there might be 3+ issues going on here that all have the same end result: zones not running. If that’s the case, and there are multiple causes, it’s no wonder it’s been impossible to debug.
Another suggestion would be for Wyze to task someone to go through all 500+ post of this forum and start making a list of the factors involved by each person reporting. They may have to reach out to people to get the data. At first thought, relevant information from each person would be:
a) Smart schedule or fixed schedule
b) Number of zones
c) Skip setup
d) Rules setup
e) Firmware version
f) Zipcode
g) Does the issue happen intermittently, or consistently?
h) Does the system show the zone ran even though it didn’t, or is it simply not in the schedule when it should be? (I believe I’ve seen both issues reported on this thread)
Perhaps by collecting this data, some patterns will jump out to the developers.
It definitely seems like something is purposely cancelling it in the morning for no reason. I moved my schedules to set times in the evening. One is supposed to be triggered tonight at 10 PM. It’s been missing since 2 PM from the schedule. No reason listed, just completely missing and it’s before the time it’s set for
Can no longer get it to run even when putting it a few minutes into the future. Finally gave up and manually ran for a few minutes but we can’t do soak cycles with the quick runs.
Moved the schedule every few minutes between 1:10 and 1:30 AM CST with no luck. It would just skip over it and still claim it was going to run today at the set time despite being past. Hoping there’s something in the logs but already expecting nothing
you make a good point here: they should allow us to manually run with soak cycle so we can use that when needed.
for me schedule is still working by selecting days of week as my schedule. not the every 2 days I originally wanted but ot works for now.
Unfortunately I use days of the week and it doesn’t work for me
Something interesting last night, I started a quick run during the schedule (since it didn’t run) and after the quick run was done, it said “soaking” and showed it being in the middle of the schedule. I thought I had found a workaround but after the soaking timer was done, the schedule just disappeared
I feel like that’s a new scenario we haven’t seen before so hopefully it helps find the fix
@bsaraiya
Do you have any rain sensors attached to your system?
Also I did find out that if you do a quick run or a manual run that will automatically alter the Smart Schedule, it will adjust or push forward the schedule based on the quick run that was watered.
@cclarke96
I am being told your firewall could be affecting it.
If Wyze’s is experiencing communication problems delivering messages to it’s smart devices, like the sprinkler controller, why can’t they inform the account holder by email to let them know their communications is unreliable? It would help with diagnosing the situation and give users a heads up to monitor their devices more closely, rather than just waiting for a lawn full of dead grass to indicate a problem.
I think you should pass along the log 1101367 since that was in the middle of the supposed schedule and it skipped the first watering going straight to “soaking” message and then disappeared around 2:10 AM CST
How does the rain sensor work? Would Wyze get a flag telling it not to run or would it simply fail to run?
I think like most people, my router blocks all connections initiated remotely. The carrier NAT could be causing because it doesn’t share a true routable IP for callbacks. That could be game over for me. Anything else I can provide to further identify if that is the issue? Happy to jump on a call with an engineer if it helps.
Yeah that’s pretty common. The device should initiate & maintain the connection to the wyze server. There are hundreds of iot devices out there that are able to work behind a standard consumer router with normal security settings. Unless someone manually configures a very, very restrictive firewall in their home network then i don’t see why this device wouldn’t work behind a consumer router
If anyone experiencing this issue is willing to do a bit of troubleshooting/testing with us there is something we would like to try.
Could you turn off/disable your Fixed Schedule and create a rule to schedule your watering? We would like to see if this is failing like the Fixed Schedule seems to fail.
I’m willing to give it a try!
Disabled schedules.
Created rule - schedule
Start - 7am
no end time
s,m,t,w,t,f,s
Action : start watering: zone 2, 10 minutes
This user indicates that it is still skipping for them even when they don’t have any of the autoskip settings enabled. I thought that could be useful info.
I can confirm that I’ve tried turning off all the auto skips in both smart and normal schedules and it still skips. I tried turning back on and this week it marked a rain skip on Sunday but ghost skipped yesterday and today
Supposed to water the new grass every day. Old grass was killed from lack of water because of these ghost skips and now the new grass might too
i have always had all the skip features off, it didnt really skip. the schedule just went away, never said skipped, acted like ot was never scheduled. i am still fine selecting days of week, so havent changed it from that.
The Rule instead of schedule did work again this morning. No notification in the app of start or stop but I checked during the run time and the app indicated that it was running. And the overspray on the driveway confirmed
