A very well documented test procedure and it should prove to you plus anyone who reads this that the problem is partially Wyze and maybe partially customers fault not firmware if I’m understanding what you wrote correctly.
I would like to commend you on the effort that you put into investigating it. Wyze should pay attention to your results.
Yes. Creating the need for Firmware Flash recovery or reversion updates is 100% on Wyze.
I have been posting for quite some time now that the high failure and Cam brick rates after firmware updates is being caused by what I imagine is a failure in the delivery and install mechanics, not in the firmware code. Else we would be seeing firmware failures across the board rather than only on a percentage of updated cams. However, local network connectivity efficacy does play a supporting role in the success of updates, and that is on the user. Where Wyze needs to grow to overcome this possible barrier to successful updates is in download package inspection after delivery and an abort sequence that returns the cam to prior firmware when errors are found on download or install. The OTA Update vehicle needs tightened up.
For some time now I have suspected that the Bulk Firmware Update procedure is blasting too much data across the network while trying to update multiple cams simultaneously and causing increased failure rates. I only OTA update single cams at a time and suggest the same to others. It also prompted this Wishlist post (unashamed self promo for votes): Progressive Bulk Firmware Updates.
I would put only a small responsibility for failed Firmware Flashes on the User. After all, Wyze did create the need.
Unless you have done it several dozen times, it isn’t intuitive and one must be really tech savvy at sussing out possible failure points to find out why Manual Flash Updates are failing. When all the moving parts do align, it does work.
Agreed. I now only perform individual updates after reading your previous post.
I am on v3 firmware 4.36.11.7095 and all the basic functions are working well for me (I don’t do Detection zones, Grouping, Alexa or any other Rules).
I do update each v3 individually too. I start with my backyard cam which only captures rabbits crossing through my yard. If the update goes well and function well, then I individually update the rest of my v3s.
I watch this forum closely. Users that update immediately will generally post about issues. This strategy has worked well for me
We just had this issue on 3 of our cameras. Apparently it doesn’t like something about the access point.
I reset the router and it didn’t make things work.
The same firmware is working on many of our cameras at other sights.
We have centurylink fiber internet with a C3000z? router.
I connected one of the two cameras I thought were bricked to my cell phone’s hotspot and it worked fine… I couldn’t make them connect to the centurylink router at all.
Of note, our TV and a few other devices won’t connect.
We had the router replaced a while ago but things were working after the router was replaced. The new camera was working just great until I let it do a firmware update… There may be some ipv6 or dns setting that is incompatible now.4.36.9139 works,
The error says: Your device has lost it’s connection. Please check your internet connection or try moving the device closer to your Wi-Fi router.
I litterly brought an AP that was working right next to the camera… it did not make it work… I tried a few different accesspoints, but what finally made it work was when I did another ISP… when I ran it on my tmobile hotspot it said connection successful and it worked great.
4.36.11.7095 works on cameras that are elsewhere.
4.35.10 something worked, the camera that broke went thru that firmware on it’s way to death.
I do have one camera with 4.36.11.70495 working here… so that is interesting. but we have a lot of devices not working, and the firmware update had something to do with it.
our floodlight pro with 2.2.1.1083 is also not working after today. no redoing the breaker and router have made it work.
btw, this is not Jerry, I set up a forum name and this was not the name I set up. These do not reflect the words of that person.
I just went into the router and found this:
4. Set the DHCP name special character state. It was OFF, I set it to on, and this may make it work… Wyze should not be using special characters in it’s name.
Greetings and welcome!
This leads me to believe there is a configuration issue. Have you tried resetting the router back to factory default? That would be the best way to proceed rather than trying to toggle various settings, etc. I suggest this because connectivity issue is not just with the wyze cam(s).
Let me know if that resolves your issue. Cheers!
The issue was solved after that message was sent; I verified that the cameras remained connected to my display this morning. --Jerry
The problem is that the wyze cameras now use special characters in their DHCP negotiation, earlier firmware did not have this issue.
We did a work-arround with the router, but the problem is with the new wyse firmware
I have the same problem, since the firmware update I did on my 3 cameras, I cannot connect to them, unless i restart the camera. After restarting cameras, then I can connect for a few minutes and view the videos… a few minutes later connection is no longer possible. I have posted the issue using the app 3 times… I am looking forward to a new firmware that will fix this problem. For the record, my firmware version on 3 different products are 4.9.9.306, 4.25.1.333 , 4.36.11.8391…
The solution is much simpler. I work with Point-of-Sale devices and updates. The first part of the communication protocol response is to include the checksum/md5sum of the software or firmware that is about to be delivered. If it doesn’t match, you don’t apply it and try again. Corruption is near impossible.
But checksums are only useful if the download completes because that’s the only time you can compare checksums. And I’m fairly confident Wyze already does that.
What the point of failure however with firmware updates, is that the camera loses network connection at some point during the download.
The solution is to be able to resume the download. There are ways to do that.
If the download isn’t complete or isn’t correct, then you don’t do the overwrite! Are you saying the download is done directly over the existing firmware? That’s just plain foolish. The download should be done to a temporary storage location.
It’s overwritten with the very first byte of the download. Which is why the camera is borked when the network connection is cut.
It’s because the camera has no place to store the downloaded file before overwriting the firmware; it has to overwrite the firmware as the download proceeds.
And the reason there’s no place to store the downloaded file is cost. Wyze targets the low end of the IoT market. The added space costs, and is useless during normal camera operations.
Would be nice if Wyze could use the SDcard to save the downloaded file. But then they’d have to require that everyone install an SDcard. Then Cam+ revenue goes down …
Please consider your router as the problem. I have replaced my sister’s router twice, and mine once. They don’t work forever. I am using many V3 cams on 4.36.11.8391 reliably.
Wow. That was quick. Could be a lot of things.
All my cameras are offline, starting at 06:38hrs this morning, I’m tired of having my system down whenever I update. I’m ready to dump Wyze! I have to reset all cameras that’s a pain! My Doorbell Ring and added Ring all work great.
I try to avoid doing the updates especially if my cams are working.
Updating usually brings frustration as Wyze doesn’t test their code that well and expects all of us too 
My other brands of cameras Never have these type of issues when updating so it is possible to write quality software & firmware but Wyze just doesn’t bother 
My latest incident of cameras not working after an update:
They goofed up the DCHP, now the cameras return invalid strings.
It works on some routers that are more lenient, but ones that are strict won’t work with it.
The camera basically tries to name itself something that has invalid characters in it.
As far as I know, they did not fix the bug. I was able to work around it by changing the router settings.
Same problem - How do I manually flash if camera won’t connect to network?