The issue is back for me, too. Here’s the log number: 498379.
Sigh… no longer working. It worked just long nenogh for me to delete all my posts complaining about it
Glad i haven’t returned the Rachio yet… upgrade worked for one cycle. Back to brick status!
FYI, the Wyze Plug, nor the Wyze Outdoor Plug, with the Power Brick for the Wyze Sprinkler Controller connected will fit inside the Wyze Weatherproof Sprinkler Controller Box 
So, I thought I’d try a Wyze Outdoor Plug that was sitting on my desk, new in the box…
that was strike two, no way to get the Wyze Outdoor Plug, and the Wyze Sprinkler Controller power brick to fit in the space available in the Wyze Weatherproof Sprinkler Controller Box :
So, 3rd try, was a short one foot power extension cord, and that was the winner:
I opted to go with the NON Wyze solution for a power plug as the Wyze Plugs I own are having issues with staying connected to my wireless, and the TP-Link (Kasa HS105) Smart Plug has never lost connection with my wireless network in the two years I’ve owned it.
So, now I can create a routine in Alexa to power cycle my controller once a day (or more if needed) to try to make it usable until Wyze fixes this issue…
That said… I powered the device down before installing the TP-Link (Kasa HS105) Smart Plug to ‘automate it’ and the first time I unplugged/plugged I did it fairly fast to 'reboot" the controller and it did not fix the issue…
The 2nd time, I left it unpowered for over 1 minute or more, plugged it back in, and the controller successfully ran a quick run on the two stations I have connected.
latest log: 498487
SJ
Oh dear - I’m on it. Thank you for your logs.
If you would like a refund but are past the return window, please create a support ticket and get the ticket #. You can then tell the agent that I instructed you to get the ticket number only and will handle the rest, so the agent should not try to go through troubleshooting.
Provide me the ticket number so our team can issue the refunds through a secure communication (Wyze Forums does not allow personal information on posts or DM).
Once again I sincerely apologize and we are investigating it right now.
1 Like
@Shanee I’m not looking for a refund, I just want the Sprinkler Controller to work.
Let me know when I can test something again
SJ
1 Like
I think I would like to get a refund as I cannot wait anymore. Here’s my ticket number: 1880066
I appreciate your efforts.
Thank you!
Ran two Quick Run’s, one at a time for the two stations.
both for five minutes, both ran the full five minutes
Log: 499071
I did not power down the controller since the last Quick run (don’t recall if the previous quick run was successful or not)
I have no schedules currently created.
I will create two schedules for overnight watering to see what happens. (without power cycling the controller)
SJ
For me, the problem is for the days with a preset schedule. When a schedule is set for a day, it messes up the system, and even the quick run stops running for the day.
Same problem here. New to this forum. Installed the new firmware and it worked for one day. The issue returned the next day. Deleted all schedules and did not help. Unplugged and plugged back in and it works for one day still. Submitted a ticket.
After getting the quick run to work properly, I set a schedule for last night at 1am, 9 minutes per zone, two zones total, and shows it ended at 1:18am.
log: 499759
SJ
Tonight, I initiated a quick run on zone 1 for 3 minutes, and 4 minutes for zone 2.
It stopped as fast as I started it.
I haven’t power cycled the controller yet.
Log: 500080
I’ll power it off for five minutes, and then back on to see if that ‘fixes’ the issue
SJ
@Shanee I powered off for ten minutes, powered back up, initiated a quick run, succesfully.
LOG ID: 500107
Is anything being done to resolve this issue?
Or should I just rely upon a power plug to power cycle my controller once a day?
Perhaps you can enclose a working Wyze Plug with each controller and call it good? 
SJ
I have had good luck so far. 3 days in a row where both manual runs and scheduled runs are working. I haven’t powered off/on since Thursday
I had wiped all my schedules before I did the firmware update and deleted the cache in the app too.
I’ll update If stops working but keeping fingers crossed
I haven’t been able to narrow down any consistency on when it works, and when it fails…
Even the power cycle seems to be hit and miss.
SJ
How did people update to the 1.0.7 version of firmware? My Wyze app shows my firmware version is 1.0.4 and up-to-date. It used to be 1.0.1 and lat least the physical buttons were working and I updated to 1.0.4 now nothing works. I have been having the same issue for so long I’m so desperate…
Just checked, I’m on Firmware version 1.0.7, not sure why you are ‘stuck’ at 1.0.4.
SJ
@jabbari.nima Sure thing, our support lead should reach out to you very soon for the refund.
@Joey789 We have paused the 1.0.7 firmware update for now. I am very sorry about the persistent issues.
Our engineer said he recently found some clues so I will be asking for more detail on that and updating you all here. I am also doing a root cause analysis to see how this entire thing piled up, and hope to provide everyone with the full analysis for transparency.
1 Like
Here’s an idea… which I previous mentioned. Create a 1.0.8 build based on 1.0.3, and release it. Problem solved… then tackle the coding problem and release 1.1.0 with the emergency stop function for zones running more than 3 hours that was included in 1.0.4.
Update from our engineer:
"The logs show that the device timestamp still has an issue. The firmware gets this timestamp from the hardware RTC chip. I’m doing an improvement that uses another internal RTC of the MCU to double check the timestamp. If the external RTC’s timestamp exceeds a normal range from server time, normally we use server time as backup, but server time cannot be received in a stable manner. Thus we will use the internal RTC time if the external RTC timestamp deviates too far from server time. Then the firmware will reset the external RTC to do recovery. I think a double RTC verification will fix the Quick Run stop issue.
I think the root cause is the incorrect system time, so disabling the emergency stop cannot guarantee a fix. If we use old firmware, the RTC time may still have issues, hopefully double verification will address it."
1 Like