I removed the controller from the app, and then factory reset and reconfigured the controller. I then did not activate sprinkler plus. It doesn’t matter, I still have the same exact issue. A rachio 3 will be here tomorrow to replace this if a firmware fix isn’t available by then.
Thanks, I just ordered an orbit.
@Shanee I’m considering returning my 4 controllers.
Can you let us know if the Wyze tech team is actively working on this, or you still determining wether or not the issue is user error?
@Shanee I am also tired of waiting and not getting any clear response from Wyze. I am seriously considering returning my controller if the matter is not getting addressed immediately. Do you have any updates for us from the technical team? And it is super ridiculous we cannot have a direct talk with technical folks at Wyze…
Hi all, our developers are actively working on the issue. We know for sure it isn’t user error, but it will take them time to identify and solve the root cause. This is their highest priority right now and I sincerely apologize for the wait!
@Shanee - Push a revision of 1.0.3 through an optional app build (testflight) until this is resolved. This would at least help with further troubleshooting, then run a diff between 1.0.3 (assuming it works correctly for all of us plagued) and 1.0.4.
I doubt Wyze is going to add their entire user base as testers on Testflight.
A rollback of the live version to 1.0.3 would be a better option.
For sure, but when I suggested it last time… Crickets. Opt in for beta/testflight, then push 1.0.3 optionally for us users with an issue.
Quick update - our firmware engineer said we cannot revert the firmware (I appreciate everyone’s suggestions though). He also does not think that the water stopping issue is due to bad schedule data - but he is working with our backend engineer to confirm if that’s true. They are providing a solution as soon as they can. I will keep you updated.
@Shanee - Love the communication. I sure hope they can get it sorted soon!
+1 on the communication @Shanee. Things happen, stuff goes wrong, how they are resolved is what matters.
I have been having similar issues that I had not noticed until recently when I need to start watering (installed the unit in Dec '21 and everything work when I tested right when i set up and it appears to always be online…but once I tried to water and schedule runs I am seeing the issue everyone is noting here)
Only works when I manual boot and stops working a few hours after. I know the firmware 1.0.4 introduced a 3 hour emergency shut off so just wondering if that has anything to do with it since it seems like it stops working a few hours after each power cycle
I also noticed in my router that while my other IoT devices show access time counts that continue from their first connection to the network, this devices stops at 18 seconds after every reboot. It still shows a good connection, but seems the router stops tracking its access connection. It still seems to get my commands from the app to water because the valve turns on, but if I hadn’t power cycled the device recently, it immediately turns off 1 second later and never even registers the run as happening at all.
Also my log number is #478807
I have the same issue. Quick run used to work, but the automatic schedule has not (and no notification that it didn’t run). Now I can’t run it manually either - from the app or the control panel. It starts and then stops after a few seconds saying that the schedule is complete. Also have V1.0.4.
I just purchased this controller and am regretting it. I set it up and it worked great. Now I’m having the same problems as everyone else. Only runs for about 1-3 seconds.
I replaced my controller this morning with a Rachio 3, and it works beautifully. Unfortunately, this Wyze controller is going back. On the bright side, I ordered four more Wyze V3 cameras since the RTSP firmware works great on them with Blue Iris, that I use for all of my other cameras.
I completely understand. Sorry for the trouble ![]()
Another update - we found many reconnect events in some of the logs, which may be due to the ESP firmware issue. We are working with the engineer for further analysis.
That Rachio looks nice. little pricey but if it works… Its in the Amazon cart, Just waiting to see how all this goes ![]()
Please provide an update on this. I live in the desert and going without being able to water is not an option since I won’t have anything to water pretty soon.
New update: we have found the direct reason for this issue: the timestamps in the schedule data are wrong, so the device stops watering immediately after starting. We still need some time to get to the root reason for this happening and confirm the firmware and backend solution. Our engineers said all work will be done before Friday (I don’t want to give hard dates in case it shifts, but this is their estimate).
Before this update is released, they suggest deleting all schedules and recreating them again, in case it helps solve the problem temporarily. We will continue to provide updates on potential temporary fixes and progress towards the full solution.