New Wyze App Firmware Available
Today, we are releasing the 4.53.9.3438 firmware version for Wyze Cam Floodlight v2, which includes the SightSafe security update.
SightSafe: enhances security by embedding user-authenticated signatures at the media source, adding an additional layer of security to event videos and live stream.
This will be a gradual rollout over the next few weeks.
Read our Release Notes:
I don’t have any Cam Floodlight v2s, but there might be a problem with this update:
I’d encourage anyone experiencing problems with this update to post here, in this topic, but I wanted to link that other one in as the issue is being explored.
Firmware version 4.53.9.3438 will not join a hidden SSID. You have to unhide the SSID, then allow the camera to join. Then you can hide the SSID again. But if power to the camera or wifi router is restarted it will not join the hidden SSID, you need to unhide again.
I was able to join a hidden SSID with the out of the box firmware but not with this latest release.
When can we see a new firmware update to address hidden SSID?
A few days ago a user with this problem reported that the Cam Floodlight v2 had joined a network with a non-broadcast SSID, or at least that’s how I interpreted the comment. I’ve still been asking Wyze for an update on this but haven’t yet seen anything from them about this specific issue.
Welcome to the Forum, @Driving! 
From my perspective, I have 2 brand new floodlights v2 installed earlier this week and able to join a hidden SSID out of the box. Auto update was left on and it updated to the latest firmware. Last night rebooted my router and these 2 cameras would not connect.
Today I went through the process of powering off, unhiding and hiding to test this theory. Every time it’s the same, need to unhide the SSID. This started with the latest firmware.
2.4 GHz
Hidden SSID
WPA2-personal
AES
3 locations, 23 various Wyze cameras, auto update off on all except these 2 flood lights.
Right. That’s been identified as a problem, which is why I’ve linked an appropriate topic above (twice). I’ve been told that the engineers were supposed to be checking for issues but have not received an update since then (that was on 30 May 2025).
Thanks for reporting that it’s still a problem! Hopefully we can get a better answer (and a fix) for this soon.
