Did you volunteer for the Beta program?
No. Not sure how to do that.
And actually apprehensive that, given what theyāve already done with 1433, they may cause even further damage with their āexperimentation.ā 
The beta program is full 
. And that one blasted camera keeps dropping off again 
.1472 is still in Beta. I have not seen any public release for update to those not in the beta program.
If you did not sign up for the beta program and designate the cam as a Beta device, you wouldnāt be offered the update.
Also, the Beta .1472 isnāt being pushed. It is a voluntary update for beta testers who choose to update.
For Android, keep trying using the sign up link in the Wyze Web Page.
Testers are in and out regularly so an opening may come up quickly.
I donāt see any change! I did the app update this morning. And am still seeing ERROR 3001ā¦ Apparently just saying itās fixed doesnāt make it so.
This thread is for the V2 and PanV1 Public Production Firmware 4.X.9.1433. NOT the most recent Public Release firmware versions for these cams.
Perhaps you should post about your Error 3001 issues in the most recent Firmware Update Announcement Thread for the current version that was announced to have fixed the issue:
Or, if this is an app issue rather than a firmware issue, you can post in the App Update Announcement Thread for the update that you mentioned.
Did the new events recorded from the 4.9.9.1472 firmware still have the 3001 issue? Please let me know if the issue still happened on the new firmware. Thank you.
I just installed. Had to be set up again after install. Then I got daring and decided to hit the Reboot buttonā¦ Epic fail. Nice try, but no dice. Wonāt connect again 
It also took like 10 minutes to scan the freaking qr code, so I probably even had it updated before you posted 
Here, have another log. Itās currently set up as before, but had to be done manually. Same bug, same wyze channel, coming to a firmware near you! 
774716
Thank you for the feedback. The issue is that the firmware cannot reconnect after rebooting right?
The issue persistsā¦ No recconect on reboot or wifi loss.
EDIT: My other v2 in the garage is about the same distance from WiFi (if one were to walk through walls) and shows the same signal level has never disconnected. That is, has not disconnected since having to do resetup after the problem firmware was installed like a week ago or whenever that was. (Yes I realize wifi signal is more acoustics than penetration, and the acoustics are far better from the AP to the garage than the other v2). Iām going against my better judgement and pushing the update button on that one too.
Poof! Like magic, no connection booting up after flashing latest. Same yellow/blue lights. Called it. Mic drop.
ā¦and now back online after manual setup. Weāll see if this one remains the breadwinner and stays online, or if the new firmware is worse. Itās a race to see which one drops off first. Should be the other one, but Iām not willing to bet the farm on it.
At least Iām having a good time laughing at my own jokesā¦ but in all seriousness, this sucks.
EDIT2: Sorry for the stream of edits. Have already lit up this thread.
So you donāt have to rescan the entire thread, do recall that my setup includes WPA3 (unfortunately with WPA2 fallback) and no SSID broadcasting. Which may be the problem if others report that the new firmware fixes their issues.
4.9.9.1433 seems to have caused one of my two my contact sensors and my only motion sensor to become bricked.
I tried deleting the camera and resetting everything up, pulling the bridge off and moving it to another camera, changing batteries in the sensors, and even flashing back to the old firmware but nothing resolved it. Since I started over from scratch, I need to reconnect them, and they refuse to connect.
Thanks for yet another horrible firmware update Wyze! I swear, each update just makes the V2 cams (and now the entire system) worse. Iām about ready to just throw everything in the garbage so I donāt have to fight with it anymore.
Tried updating one to 4.9.9.1472 - and same as before - works fine until you restart it - then unable to re-connect to wifi (flashing blue/orange light).
How is this not fixed?
Sorry for the trouble. We found an issue on the v2/pan 9.x firmware. If your WiFi password is longer than 21 character, there is a chance that the v2/pan will not able to re-connect to WiFi after rebooting and need to be re-setup. We will make improvement on this issue ASAP. If your device currently has this issue and you donāt want to modify the WiFi password, please use this link to flash your device back to the 8.1002 firmware. We are really sorry for the inconvenience and we will fix this issue.
I was directed here from another troubleshooting thread. Sadly, I canāt get the older firmware to flash on my v2 cameras that are having the issue, the light never goes blue so it never flashes the files.
edit: I figured it out, had to partition down my SD to only 8GB, flashing now
This has been happening for a long time now, pull the broken firmware - it keeps prompting me to update my v2s.
My wifi PSK is maxed out at 63 characters, so I definitely fall into that category. Is there somewhere we can subscribe to this bug tracking so we know what firmware version it is that fixes it when itās released?
I often tend to do the same thing - max it out to the spec, gosh darn it!
So, to improve security, Wyze now requires a WiFi password, just not one thatās too longā¦
Probably a memory issue, trying to squeeze max code on old hardware.
So yeah, a bug track site per cam model would be most useful. Especially if it listed limitations per firmware version like this (ideally with affected MAC address ranges) so they could be planned forā¦
