I have a v3 camera that reports that it was not able to complete the firmware upgrade to 4.36.11.4679, It will restore to 4.36.9.139. This is where it offers to upgrade to 4.36.11.4679 (Directly from 4.36.9.139) It does also fails to connect to wifi after the attempt to upgrade to 4.36.11.4679 on an attempted re-setup.
Welcome to the Wyze User Community Forum @noh! 
If I had a cam doing this, I would do one of two possible actions:
-
Flash the cam direct to the most up to date production firmware, 4.36.10.4054, and try the Beta Update again; or,
-
Remove the V3 from the list of Beta Devices within the Beta Settings and allow the cam to update thru to the latest production firmware. Reenable the V3 within the Beta Devices list and retry the Beta update.
What wyze isn’t saying is the bug also sent thumbnails of movement from cameras without subscriptions and event recording disabled. So the severity of the issue is much more then just a free no cool down. Wyze ended up uploading pictures of my kids bedroom as frequent as 5 a minute and even after reporting never got an apology.
As I understand it, the bug(s) in question that this firmware update addresses only affected us beta testers who signed up to test firmware that we were informed was not yet thoroughly tested and confirmed as ready for public release (because it is “Beta”).
While I don’t work for, speak for or represent Wyze in any way (I am just a user like everyone else, albeit one with 40+ cameras and 300+ total Wyze devices), I do like to help other users make sure they are getting the best experience possible for their expectations. As someone who has worked professionally in QA testing, I can say confidently that in many cases it is better for most users to keep security-critical or privacy-critical cameras unenrolled and out of beta testing because it is the nature of beta to have bugs that can diminish said expectations (unintentionally). I would only update important or high-expectation devices like those to production firmware and only use the production app. This will greatly improve most people’s experience in the long run.
Anyone who wants to reduce and limit the amount bugs/frustration/etc they may experience in the future can unenroll individual device types (ex: all V3 models, all Pan V2 models, all V3Pro models) from Beta by going into the account tab → About → Beta Program → Edit → Deselect Devices you want excluded from potential Beta firmware.
If you want some of a certain model to get Beta firmware (ex: V3 cams that are outside), but not all of that model device (ex: V3 cams in bedrooms, or other privacy critical locations, etc), you can leave it selected and then remember to only update the outside cams to new beta firmware when it is announced in the forums Beta category or on Facebook Beta…but only update the Bedroom/privacy critical cams when the announcement is made in the public news channels. I do this method for some of my critical cams (skip updating them to beta firmware because they are too important).
Another alternative we always have too, is that if we do experience a bug we dislike, we are never stuck suffering with it. Wyze has enabled manual firmware flashing for us and provides a copy of the public production firmware that we can download and load onto our cameras. So there is never any reason for us to be stuck and continue being frustrated at having loaded a firmware we find undesirable for any reason. We can thankfully resolve any issues within just a few minutes of time (I have done this several times myself over the years). I would suggest that in the future, if anyone experiences a firmware they dislike, ask a forum member how to roll back the firmware and there are several of us who are more than willing to help with that.
Sometimes leaving the App Beta is a good idea too: Account Tab → About → Wyze Beta Program → Leave.
Much appreciation to everyone and anyone who does voluntarily choose to help beta test devices and the app to help catch oversights like this and get them resolved before they ever go to Public Production Tracts. I know it can be frustrating when we experience beta bugs. I have had devices in beta go non-responsive or do weird things too, so I know how frustrating that can be when it’s not working the way I want. This is why I only beta test with less critical/important devices and leave others on production, including the ones I use as baby cams for my toddlers’ bedrooms. This method has worked out really well for me and I still get to feel good testing out new features as well as helping to identify and report any bugs I notice on some of the other cams. Please don’t let Beta Testing be an unpleasant experience. If you find that it is unpleasant for you in any way, consider switching to the public production firmware tract instead. For anyone still willing to put up with occasional bugs or discomfort in some way in order to help everyone else have a better experience, we all appreciate you.
3 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.