Those settings should be good.
You said you’ve already tried a different AC adapter? If so and this happened after a power issue, the wifi module in the cam may be damaged. Have you tried setting it up right near your router, in case the wifi is working but just very low power (range)?
Yes, ive tried a different power brick then the one it was connected to when the power surge occurred. I believe the cam itself is fine, I mean, why else would it connect on my friends network or to a hotspot created on my own network. This is such a unusual problem, and my trouble shooting have narrowed the problem down to my WiFi network. It just doesn’t make sense how this one device is problematic.
My thinking is when you tried hotspot the phone was nearby so if the power level of the wifi in the cam is diminished, it may have been enough. Not sure about how close it was when you tried the friend’s network.
That’s why I suggested trying with the cam right near your router just to see if that might yield any clues.
I think that’s a good idea. I also still wonder about answers to the questions I asked in the topic @jeffrey_martin_5 started about this. 
Good suggestion, however it didn’t make any difference. I tried to pair the cam within a foot of the router and it still failed to connect to the network
Seems you’ve narrowed it down to something to do with your router then.
Does your wifi name or password have special characters in it? Spaces? Those are both things that can cause issues with some devices. I typically try to stick to upper/lowercase letters and numbers, a fairly long string, just to avoid possible issues.
Dashes in the network name I’ve used very frequently and never had an issue, so that’s probably safe. Underscores seem to work fine also (many isp routers and extenders use those) but I still avoid them. I don’t think Wyze has any issues with those though.
I believe I’ve used exclamation points in passwords for people but I can’t recall if that’s ever caused any problems.
Other than that I can’t tell you which ones are or are not problematic. Maybe try setting up a guest wifi (if your router supports that) with a simple network name and password, see if it works, again will help narrow things down.
Or if it doesn’t support guest you could temporarily change the password at least on your 2.4ghz (and maybe the network name if it has special characters in it) just to see, then change it back so your other devices come back online.
I know you didn’t start this thread but pretty sure you mentioned this started after a power surge, or was that not the case? Hard to ignore that detail if so, but maybe there’s just some confusion there and it wasn’t anything to do with power. Did this cam ever work with this router and wifi network?
Some have also found that disabling 5ghz (if both frequencies share the same network) can help when setting up a cam, basically forcing the cam and phone to be on the same frequency, but really that shouldn’t be needed for the cams that use bluetooth for setup, which the v4 does.
And even with the ones that don’t, that really only helps with a few routers that for some reason block some traffic between 2.4 and 5. I’ve set my cams up multiple times where the cam is on 2.4 and the phone is on 5 with 0 issues. And my wireless does totally block communication between the bands, as well as between devices on the same band (intentionally). So not really sure why that even helps for some people.
Maybe it is an issue when communication partially works between bands, but not fully. Where mine is completely blocked, maybe it knows to fall back to something else. Who knows.
I actually partially suspect what might actually happen in that case is it just prevents people from accidentally picking the wrong network during setup since the 5ghz one will be missing. But just guesswork on my part.
All, I’ve resolved my issue — sharing what I did in case it helps the OP or anyone else running into something similar.
My troubleshooting showed the problem was isolated to my Wi-Fi network since the cam worked fine on a different one. My router is provided by my ISP, and most settings were locked down, so I couldn’t change much myself. The only thing I initially had access to was disabling either the 2.4 GHz or 5 GHz band. I tried disabling 5 GHz and forcing both my phone and the cam to use 2.4 GHz, but that didn’t work.
I then called my ISP and asked them to give me access to the modem interface so I could adjust some settings. I even preemptively ordered my own router in case they refused. Luckily, they agreed, pushed an update to the modem, and within minutes I had full control.
I tried a bunch of things — adjusting WPA security settings, changing the network name and password, even disabling WPA entirely so the network was open. Still no luck.
What finally worked was splitting the bands. Instead of one blended 2.4/5 GHz network, I set up two separate networks with the same password but slightly different SSIDs. Once I did that, the cam connected right away.
Out of curiosity, I switched the network back to a blended 2.4/5 GHz setup — and, as expected, the cam dropped offline. To fix that, I kept the cam paired to my account and pressed the setup button on the bottom to initiate the setup process again. Since the cam was already paired, it just reconnected to the blended network without any issues.
So now everything’s back to my original blended 2.4/5 GHz network, and the cam works perfectly. I still don’t know why a power outage caused this or why splitting the bands was the key to getting it reconnected, but if anyone else is stuck, this might be worth a try.
Splitting the bands was the first thing I did when I set up my own new modem/router I purchased earlier this year. In addition I named the SSID (s) the same as the previous unit because I didn’t want to set up 14 cams again. Glad to hear you’re back in business.
My only guess is that in many routers when you use the same network name for both, they try to “steer” clients to 5ghz. This attempt usually takes less than a second but I’m guessing when the cam tries to connect and sees the 2.4ghz network briefly disappear (which is how the steering happens) it interrupts the initial association. But once associated, it doesn’t care about that brief dropout, just takes it a split second longer to come online.
I haven’t seen this with my wyze cams and my shared 2.4/5 with steering, but each manufacturer implements band steering differently. Still doesn’t explain why this would have started with a power outage but who knows, maybe there was a firmware update to the router and the power outage was the reboot it needed to apply it….
I never had a need to split the 2.4 and 5 GHz bands on my routers. The only time I had to turn off the 5GHz band was when I was setting up my V3s. Once setup I would turn the 5GHz band back on and combined 2.4/5 GHz has always worked fine.
I think there are two possible reasons people have to split them or disable 5ghz temporarily:
Router for some reason blocks communication between the bands and the phone is on one, with the cam on the other (though oddly my setup blocks ALL communication between devices regardless of band and never had any issue setting up either Bluetooth or QR wyze cams)
Router uses band steering and has a poor implementation of it, so when the cam tries to connect, it stops advertising 2.4ghz capability to try to force it onto 5, which confuses the cam.
Given that the v4 supports Wifi6 on 2.4ghz, I’m thinking some Wifi6 routers just assume that means it can do 5ghz and try to steer it. In reality if the cam just tried a few times, it would succeed.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.