If that’s the case, then the reasonable place to post this would seem to be in the official announcement topic for that particular firmware version. Since that topic was initiated by a Wyze Team member, I would expect that to be the relevant place where it might draw the attention of an actual Wyze employee.
1 Like
Thanks for the response but I’ve done that and wrote about this above : Cam V4 - no longer sees my wifi after FW upgrade to 4.52.8.0648 - #12 by tomekgg
But it doesn’t matter what my router is doing (or not doing).
- Other Wyze cameras work fine with my mesh config.
- Cam V4 woks fine on older firmware.
All is good - except when Cam V4 is upgraded to new firmware.
This is not the router issue. This is camera firmware issue.
If you are telling me that it’s my wifi config issue - maybe try explaining why the same camera works well with this wifi on older (slightly older) firmware.
Cheers
Maybe. Maybe it was better.
My intention wasn’t to familiarize myself with full extent of Wyze forum. I simply came to “Camera” section, because I had problem with camera. Simple logic.
Cheers.
Do you mind explaining why my V4 with the same firmware that you are having issue is working fine?
1 Like
The other cams use 802.11N 2.4ghz. The v4 uses 802.11AX 2.4ghz. As I mentioned before, since 802.11AX supports 5ghz (but the camera doesn’t have a 5ghz radio in it) your mesh may be getting confused and trying to force it onto 5ghz.
If you’re certain you’ve ruled out your wifi, then there are 3 things I can suggest. You can obviously skip to step 3 if you want:
- Factory reset the cam and re-add it. As long as you don’t delete it from the app and give it the same name, it should retain all/most settings.
- If that doesn’t work, do the manual/recovery process using the latest firmware. Factory reset before and after. Maybe the firmware update corrupted and manually loading will fix it. Again, name it the same thing in the app when re-adding it.
- Same as step 2 but use the previous firmware (make sure you have auto firmware updates disabled first).
Exactly. Maybe he can mail his cam to my house for a chance at a “good” network.
I gave up trying to convince him. He seems pretty much set like concrete. 
Some people have hard time admitting that they are wrong 
2 Likes
Wow, Wyze has really a huge problem with software quality and … quality of forum members.
If you have nothing to contribute - wise choice is to sit quiet. @ssummerlin @habib - this post was an opportunity for people who faced the same issue or who have some useful advice to help. Just skip it if you can’t offer none.
you are acting like a person who goes into the dentist’s office and yell “my teeth are ok” to the guy who is on the chair, getting his filling.
The fact something works for you, IT DOESN’T mean it’s problem free. There are thousands of different configurations and many may be affected by the issue while many may remain unaffected. Is this so difficult for you to understand?
So difficult?
@dave27 I appreciate your help but you don’t seem to be reading what I wrote.
I already responded telling you that my Cam V4:
- DOESN’T see my wifi on the most recent firmware (4.52.8.0648)
- and when I downgraded the firmware (via recovery) to 4.52.7.0367 (previous version of the firmware) - Can V4 WORKS FINE and sees my Wifi.
Short story: - New firmware = Problem
- Old firmware = No Problem.
Cheers.
I gave you some reasons why that may be, and some things to try, but given the low quality of forum members, why are you even here? Contact Wyze Support.
1 Like
My teeth are okay, but I still get them cleaned every 6 months.
Mate, you are asking me to do sth I clearly wrote I tried before. Still, I appreciate your effort, because it’s good to occasionally re-check if one has done all that is needed.
Regarding the quality of forum members - yep, you may be right. I thought Support was bad. Lesson learned.
Although, I received some helpful advice from other forum members. Maybe I just need to ignore certain … individuals.
Cheers.
I have heard you can mute people in the forum. Ignoring works for me.
Okay this is my last post on this thread. Sorry if I came across rude.
2 Likes
Hi, I found this post because I updated my cameras yesterday and ran into the same issue as the OP.
After update to latest firmware (4.52.9.xxx) the 2 cameras I have suddenly weren’t connecting to WiFi. I tried reconnecting them, but my WiFi wasn’t listed anymore and entering it manually didn’t help anything.
I went through the pain of manual updates starting with 4.52.4.xxx, then 4.52.7.xxx and those worked fine. Then I updated to 4.52.8.xxx and it broke again and stayed broken if I updated to 4.52.9.xxx. This was identical for both cameras.
Looking at the release notes for 4.52.8.xxx I think one of these 2 might be the problem:
- Fixed an issue where the indicator light flashes red and blue after the router loses connection
- Fixed an issue that would return a -90 error
It’s not a direct issue, but probably a new bug introduced.
Like the OP I also have a mesh setup (a pair of Nokia Beacon 2 from my ISP) at home with both 2.4GHz and 5GHz WiFis using the same SSID and I have bend steering enabled (can’t turn it off on main network).
I tried a few things, but what I think was the part that solved it is that I changed the 2.4GHz to only use b/g/n modes, no ax and also the switch from WPA2 to WPA/WPA2 (with TKIP/AES encryption). Make sure you power-cycle your router/modem when you do this as it didn’t take hold for me until I rebooted them. I left my bandwidth and channels to auto.
While I do think my mesh system is somewhat to blame, I agree with OP that Wyze should fix this in firmware as they’ve obviously changed something that broke everything and the reason it works for a lot of people is because their WiFi setup is different. A consumer product like this camera should however support a variety of WiFi setups.
1 Like
Welcome to the Forum, @gligoran! 
The experience you describe reminds me of this recent topic, which may be instructive:
1 Like
Yeah check out the thread that @crease mentions, based on what was in there I personally think it is likely the WPA3 causing issues (or possibly WPA3/2 transition mode which has always been problematic, but in this case I think WPA3 may have been broken on the camera in recent firmware).
You can try leaving AX enabled on 2.4 and just setting it to WPA2 (I would leave it to AES only, not TKIP) to confirm. Don’t use WPA2/WPA mode, that is very old and insecure and any devices that connect using WPA will slow down your whole network. WPA2/AES should work fine (in either N or AX mode). Always recommend disabling B, and G if you can (some older N devices need G enabled though).
I notice you said you switched from WPA2 to WPA/WPA2, are you sure it didn’t have WPA3 enabled? Typically when you have AX enabled, it turns on WPA3 support (often in addition to WPA2), so disabling AX may have just had the additional effect of disabling WPA3.
1 Like
It was previously set to WPA2 + AES and to the whole b/g/n/ax and it didn’t work. Disabling AX and downgrading to WPA2/WPA was the only way I found it to work.
I’ll do more testing in the coming days as I need to isolate some variables and I also need the time to power-cycle both the camera and the AP after each change.
I’m planning to ditch these ISP-provided APs and router soon anyways and move to UniFi anyway, so we’ll see if the issues persist there.
2 Likes
I would definitely recommend turning it back to WPA2 (AES only) for security.
Disabling AX may also disable WPA3 (if the router doesn’t have a separate option for that) or maybe it is the AX protocol causing issues, but either way hopefully you can get it to work with at least WPA2, the person in the other thread is successfully using them with AX disabled and WPA2 only.
Finally had time to test this out when others in the house wouldn’t be constantly complaining about the internet dropping out.
Interestingly enough I was able to turn it both back to WPA2 (AES only choice available) and also the ax mode (technically the Auto (b/g/n/ax)) and both cameras still connect even after AP restart, camera restarts, router restart, …
So now the only thing that remains that I did change since I initially had the issue is that the cameras are now on their own IoT wifi, that’s set to be 2.4GHz only.
I’m not suspecting that the mesh had something to do with this, because it doesn’t seem that setting propagation is instant between the root and the satellite AP, so the cameras might have gotten into a weird state.
I’ll see if they keep functioning, but hopefully they do.
1 Like