Everyday I check this thread, and everyday I try to set up my dead V1s, and everyday I grow most amazed that after a month wyze is still unable to fix this. At this point it seem to be either intentional or major incompetence.
2 Likes
@beemgee
I can say if it was intentional I would not be circling back to give updates and asking users to try things. I personally do believe the people working on it are very competent but just have not been able to track down the issue yet.
4 Likes
I do appreciate your effort, because you are the only one who seems to care. The discord channel basically said - if it requires any effort it won’t be fixed. If it’s not intentional and not incompetence then it has to be the absolute lowest priority because nothing (that is easily reproducible) should require a month to identify and fix.
2 Likes
I think it’s all about the mothership metaphor. All most all electronic gadgets from cameras to refrigerators to smart watches want you to open an account with the manufacturer. Furthermore, some features of many devices won’t even work unless you’re connected to THEIR severs. This kind of Draconian measure used to make my blood boil, but there’s no way around it anymore. Google laid the groundwork for this over 20yrs ago, and now everyone ones a piece of the action. Your DATA and usage habits action.
It’s all about marketing. Targeted marketing. These companies want to know when you used your computer, what you were doing with your computer, where you were last night, how long, what ads you viewed and/or clicked on and even and how well you slept, The list goes on. The current generation (young ppl) seems to have no problem with this type of privacy invasion, because that’s all they’ve ever known. The companies want everything to go through their servers - including Wyze. The big boys have been doing for decades now. Our data is priceless to them, and we don’t even get a cut of the action. How cruel is that?
I’ve been dabbling with the Wyze cameras lately as I want to put a couple outside to view the wildlife we have around our property. And bait the small critters to get some close-ups. The first thing Wyze should have done was to make these cameras operate just like other standard IP cameras. Now I’ll be forced to use two different laptops/tablets to see all my camera action. That, I do not look forward to. I know, I know I can create essentially an Android emulator space on my PC and then install their mobile app to support the Wyze cams. But that really is a PITS. Not hard, but the typical home owner that buys a couple of the Wyze cams will be extremely surprised when he goes to view anything on his Windows laptop.
Even though Wyze cameras - for the most part - are intended for indoor use, they’ve now become a hybrid product for outdoor use as well. Frankly, when I bought a couple of the newer WOC V2 cameras for outdoor use, I though about getting the solar charging panel - if for no other reason - but convenience of not having to remove the camera to charge it. I’ve since had a change of heart and may buy it now. Cameras should be designed to be installed and forgotten about, And, everything it records should be saved at the base station, or other device. I’ve also considered using long USB cables to charge the cameras as well. We’ll see what works out the best for my situation.
2 Likes
OK……just lost my 5th V1/ camera in a month.
Does Wyze need the MAC address?
Having known about this for a month or more,
I would think Wyze would have stepped up by now.
A general question to all on this thread….
What changed 30-40 days ago?
3 Likes
Speculation time! I love speculation time. So, we know V1s aren’t getting firmware updates. So that leaves the app and the servers. Both operating systems are impacted (according to reports) sooooo… it really looks like a server issue.
The V1s are getting to the Ready to Connect phase followed by “Connection failed.” I don’t think anyone has indicated how quickly they report “Connection failed” but if it is quick then something server side has probably changed to break the setup process. It doesn’t sound like a networking error but rather the server not handling the V1 requests properly.
Quick failure also makes me think it’s not a networking issue but possibly some parameter/variable that V2 and V3 both have by default that V1 doesn’t, then some internal server function is getting called that is breaking for V1s. Maybe some refactoring in the setup for V2/V3s caused a bug to be introduced.
At least, that’s where my bug hunt would start.
Alternatively, it’s possible the app is setting up things wrong. Maybe the method for generating the QR code changed in the app and it’s causing the camera to use invalid setup parameters which cause a connection failed – but that seems like a long shot, unless it impacted networks with some non-alpha-numeric character or something that the V1 encodes wrongly and the server is functioning properly but just can’t parse the bad encoding.
Who knows?! Hopefully, the Wyze devs know because otherwise you guys are out of luck.
My bet is still some server camera setup change that is just going 
.
Thanks for playing.
2 Likes
For what it’s worth……my setup attempts seem to take a long time from “QR Code”….to “Failed to connect”, or “Cant find specified network”
1 Like
Jackslack, mine too! (Failed to connect)
Good speculation. Happy anniversary Robo.
1 Like
how is this not fixed yet? a significant number of customers are experiencing the exact same problem - is this not a priority fix for Wyze???
4 Likes
Correct. They’ve severely deprecated the V1s and they are unsupported.
Having the same problem - it started about a month ago.
After trying everything i could think of i finally found this thread.
I found an old V1 in a drawer anD connected it - i heard the same “cannot find the specified network name” but to my supprise it actually connected?? (MAC: A4DA22206181)
I still can’t get the others to connect: LOG: 635637 - MAC: A4DA222062D1
As discussed in another thread earlier firmware before 3.9.3.96 will allow the cameras to authorize on the wyze servers however they can only live stream and record to sd. Motion events appear but no video or image and no notifications.
1 Like
mine have 3.9.4.16
the last v1 firmware was 3.9.4.32 (may be beta). I have a v1 on that firmware that is still running but my others with the same firmware aren’t. As I said the 3.9.3.88 firmware and previous will allow those failing cameras to still work although limited. You do have to manually flash it to the camera.
2 Likes
And what say WyzeJason?
So how can I get this firmware loaded into my 5 V1’s to get them back on line for at least remote viewing?
For example, exactly which firmware should I look for, and where do I find it?
Any help appreciated, and thanks!
An UPDATE….
Visited Firmware site, and only version that I could download was 3.9.4.32
All others will not download.
Was able to find a 3.4.3.96 zip per another thread on this forum.
Question for beemgee ……
Is only the 3.9.3.88 going to give limited functionality or if I was get 3.4.3.96 flashed to my V1, should I be able to at least add it back to my Wyze App knowing I’m only going to be able to view live video?
You can download the 3.9.3.88 firmware from wyze at:
https://download.wyzecam.com/firmware/v1/FIRMWARE_660R_F_3.9.3.88.zip
The url is hidden by wyze but the file is there.
This version is the latest that will still authenticate with wyze, flashing any later version will result in the flashing blue light.
3 Likes
Hm, well maybe it is a networking issue. Strike my speculation from the record 
1 Like
Thank you @beemgee! This got my v1 camera’s back online!
2 Likes
Have tried flashing 3.9.3.88 on 3 of my 5 down V1’s without success.
Here is my routine.
Downloaded the file and dropped it on Mini SD on my Mac, and renamed to
FIRMWARE_660R_F.bin
Then insertedin V1, holding down Reset button while plugging into power for 15-17 seconds, released and waited 3-4 minutes.
In every case I get Failed to Connect on trying to add to App.
Is there anyway to confirm my flashing the firmware to the camera is successful?
Thanks again beemgee