My floodlight v2 has been working fine for about 6 months. I found it listed as “unable to connect” in the app one day and so I attempted numerous power cycles (at the breaker because it’s hard wired) without result. Cycling the power brings the red led on then it turns off and the camera never connects. I tried removing the SD card and cycling the power. Nothing works. Pressing the setup button does nothing. All I can do is get the red led to turn on and then off. No other color led ever shows. Should I assume it’s dead, or is there anything else worth trying?
2 Likes
I don’t have one of these, but I wonder if you’ve tried a full factory reset. That seems worth trying, and I’d probably poke around in that Troubleshooting section of the Help Center (at that same link) for other ideas.
Just tried this with the same result unfortunately. I get a red led then nothing. I’m guessing it died somehow.
I’m not sure what else to try then. If the unit is less than six months old, then I’d definitely open a ticket with Wyze Support.
This is how I prefer to submit tickets (you can click/tap to expand this):
- Visit the Help Center: https://go.wyze.com/help[1]
- Click into the “AI-powered search” box in the middle of the page and enter
create ticket. - Click Yes, that is correct..
Repeat Step #3 or enter yes. (
UGH! 
)- When the “No, I want an agent.” option appears, enter
no. - Enter
product.* - Enter
other.* - Enter
ticket. - Enter your contact details and a brief issue description (include a Log ID if you have one) and click Submit.
* Make your own appropriate/relevant choices here.[2]
It doesn’t really matter how brief the description is. Wyze’s system will generate an e-mail message to you automatically with a Wyze Ticket number, and you can just reply to that message from your e-mail client and add as much detail as you want.
Note: A log is not the same as a ticket.
A frequent user complaint is the absence of follow-up from Wyze following the submission of a log from the app. If you choose to submit a log, then Wyze's system will generate an e-mail message to you with advice to contact Support if you need help, because the engineers will have access to the logs, but Support agents do not. You can include a Log ID when you create a Wyze Ticket in order to connect a log to an expanded description of an issue in a ticket, and that's information that the Wyze Wizards may be able to pass along to the engineering team, but those seem to be two separate systems, and it's important to understand the difference.
A relevant Help Center article goes into more detail.
I’d probably do a ticket anyway, but if it’s still under warranty, then I’d expect them to cover it for you or at least potentially offer other troubleshooting suggestions. Seems like you’ve tried the right things so far, though.
1 Like
I think I am having a similar issue with my Floodlight v2. I bought it in Feb 2024 when the product first came out. Two days ago, right around sunset, I noticed the ambient light was on but the light didn’t go full output as I walked past. Ignored it as a timing issue so close to sunset. Tonight, I went out in the pitch black and again the ambient light didn’t transition to full light. Went to my Wyze app and discovered my floodlight was offline. My other Wyze v3 camera on the same 2.4GHZ network is still working fine.
I tried switching the power off and on to recycle the unit. It would show the red light for about 15 seconds then I hear a click-click (camera shutter?). Wait for minutes but the device never connects within the app. Repeated the process with the same result. One observation, as soon as the power was cut, the ambient light went off and even when powered back on, neither the ambient light or full motion light were operational.
I went as far as to delete the device from the app and reset the floodlight. It says ready to connect and I go through the process on the app to add the device again. I can connect from the phone to the floodlight WIFI to attempt the 2.4GHz WIFI connection but it eventually times out and the floodlight says could not connect to local network. I tried repeating the process and even tried rebooting my router but no change.
Before I deleted the device, I could see I have events last recorded on May 23. I noticed a new update was announced May 22. Could our floodlights be picking up the new update automatically and bricking themselves? If it did update, would there be any indication (log) on the SD card if I pulled it out and put it in a computer?
1 Like
Welcome to the Forum, @ajbeck33! 
Thank you for writing such a detailed description of your experience! As I was reading it, I began to think about the timing of recent firmware updates and wondered if something hosed your camera and @Greeeen’s. Then I got toward the end and saw that you were also headed in that direction. 
This is what I think, yes.
I can’t say with certainty that this would be the case for that particular camera model, but I know that other Wyze Cams do write a log subdirectory in the root of the card, so I would expect to see the same with Cam Floodlight v2, and you’ll likely find multiple files there if you decide to pull it.
Also, I think that “click-click” is the camera’s IR filter cycling during startup.
I really wanted to suggest flashing your firmware from microSD with an older firmware version, but it looks like Wyze doesn’t make those available or allow that camera to do that, anyway, so this is my next thought:
Since that camera model doesn’t have Bluetooth or require you to scan a QR code but instead uses “access point setup”, I would consider taking it off the wall and temporarily moving it inside so it’s near your main wireless access point. If you have a strong Wi-Fi signal at the floodlight’s location then you can try leaving it there; if you decide to temporarily remove the floodlight, then you can power it indoors using an old extension cord or something similar. I would also temporarily disable mobile data on the phone being used to set it up and turn off every Wi-Fi radio on your gateway/router/access point(s) except for the 2.4 GHz band on your main wireless access point. The idea is to force your phone to connect to the 2.4 GHz SSID and maximize the signal strength to the floodlight in order to improve its chances of successfully getting the hand-off from your phone and binding to your LAN. I’ve had to take similar steps with other stubborn IoT devices in the past, including an original Wyze Plug last year. If you can get the floodlight connected to your home Wi-Fi that way, then you can turn the other things (5 GHz SSID, phone’s mobile data, etc.) back on and then re-mount the floodlight outdoors (if necessary).
It’s a huge pain in the bum, but I’m not sure what else to suggest at this point. Since this has happened to more than one person following this recent firmware update, I’m going to ask for some other eyes on this, too, and I’ll report back here if I learn anything.
Thank you both for reporting this!
1 Like
Looking at the app, it appears I did have automatic update on for the floodlight. I didn’t even think about that since I usually update my other cameras manually. Unfortunately, like you mentioned it doesn’t appear there is a way to manually rollback the firmware on this device so I’m probably out of luck. My light sits right on the wall where my wireless router is, and I turned the power on that up to the maximum without any change. Mine is just stuck with the red led, I can also hear the click you mentioned but nothing else.
I’m wondering if that’s what did it then. Thanks for that update!
@Greeeen & @ajbeck33, what firmware versions are your floodlights showing? I realize that getting an answer from the app might not be possible because of this:
I’m trying to find out if it’s easily possible to determine the device’s current firmware version from data on the microSD card, and I’ve been told that the Wyze engineers are going to look into this firmware rollout for issues.
My app shows the firmware as 4.53.3.9759 which appears to be the previous firmware. I guess if the new update failed the app might not show an update.
1 Like
Thanks for posting that. I’ll pass that along.
I wonder if it’s possible to get a partial update that fails and then continues to report the previous version. 
I’m not sure what firmware version my floodlight has right now. The device went offline days before I realized it had a problem, and I haven’t been able to get reconnected to it since. I deleted the device out of the app and reset the floodlight in an attempt to completely start over after power cycling proved unsuccessful.
I get connected to the floodlight’s internal WIFI Access Point during setup, but the app doesn’t show me any information about the device at that stage. Not sure if there are any tricks like using a browser on the phone while connected to the camera’s AP that would tell me any info about the device.
Over the weekend I’m going to try the following:
Take out the SD card and use my PC to see if it happens to have any logs for any update activity.
Use a second cell phone as WIFI hot spot in close proximity to the floodlight to see if that helps it make a connection.
I’ll report back.
1 Like
Thanks for checking into that. Because I knew that you’d previously reported deleting the device and that you also mentioned the microSD card, I asked if there’s an easy way to grab the device’s current firmware version from the card (like in a log or something). I don’t yet have an answer to that question, and I haven’t personally tried to figure that out with other cameras, so I’ll be interested to find out what you learn from poking around.
I got mine resolved and here’s what I figured out.
First, I tried connecting the floodlight to my (not broadcasted) 2.4GHz SSID again without success.
Next, I tried connecting the floodlight to a 2.4GHz WIFI hotspot off a second cell phone kept in close proximity to the floodlight. This worked! I immediately checked the firmware version. It listed it is running the new 4.53.9.3438 update. Since it had the update, I’m led to believe the update originally caused my problem with the unit going offline with no ability to reconnect.
Next, I deleted the device and tried connecting the floodlight to my (not broadcasting) 2.4GHz SSID again without success. Since the cell phone WIFI hotspot was broadcasting its SSID, I decided to broadcast our home 2.4GHz SSID. The floodlight connected to the broadcasting home SSID! So, my conclusion is there is a problem with non-broadcasting SSIDs after installing the latest firmware.
I don’t recall when I first set this floodlight up in Feb 2024 having any issue with the SSID broadcast but I could have forgotten, or this could just be a bug with the new firmware. I would say with this new knowledge, the behavior of my floodlight after it got the new update make sense. It seemed like it powered on correctly and it probably was. It was just offline as it didn’t want to connect to the hidden SSID. It’s interesting that it stays connected if you stop broadcasting the SSID after the initial setup.
I’m not sure what to attribute the secondary issue which originally raised my suspicion of there being an issue. That being the PIR sensor not turning on the full brightness of the spotlight when walking by. I’m not sure why that would be impacted by the WIFI connection. The ambient light was still going on during its schedule while the floodlight was offline.
I’ll report back if anything goes awry but I seem to be fully operational again. Hopefully something I learned like the hidden SSID helps someone else. You may not have to go through the extra hassle of a complete reset like I did. You may be able to try just broadcasting the SSID to see if it connects.
1 Like
I can’t recall a specific incident or topic where that was mentioned, but I believe I’ve seen this described before elsewhere in the Forum. It’s something I almost never think to ask about, so nice job of figuring that out!
Is that supposed to trigger full brightness based on generic motion detection or is it specific to a Smart Detection, like Person? If it’s the latter, then the camera would need an active Internet connection to send the event to Wyze’s servers for interpretation so that the cloud could analyze for the presence of a person and then let the camera know to increase the lights’ brightness. That’s my understanding/expectation of how it work work, anyway, since I don’t believe this model has local Person Detection. In my mind, that would explain that issue.
I’m glad to read that. Thanks for checking in!
For sure this is helpful, and it’s something I should try to remember to ask about more often. Thank you for sharing your experience with that, too!
I don’t have a subscription. I just use the basic features with SD recording. So, I would have thought full brightness from motion should still trigger when the WIFI isn’t connected.
That seems like a reasonable expectation, and I appreciate the clarification.
For that camera, I’m not sure how much of the analysis and feature processing is done locally on the device itself. Here I’m thinking about how, for instance, I’ve seen parts of the app’s UI change even when the app on the phone itself hasn’t received an update, because at least some of the app is server-based and relies on a connection to the mother ship. I know that’s not quite the same thing, but the point I’m trying to make is that the cameras are heavily dependent on their Internet connections. Even for something like local recording to microSD, which seems like it should just work as long as the camera has power, a Wyze Cam (depending on the camera model and firmware version) will reboot itself after ~30 minutes without an Internet connection and then apparently set its time to the firmware’s build date/time and stamp recordings from that point on when it can’t get current time from NTP.
My best guess is that the loop between a visual indication of motion within the camera’s field of view (and possibly Detection Zone, if one is set) and the activation of increased floodlight brightness involves a call home to a server at some point. Without the Wi-Fi (and Internet) connection, there’s a break in that loop. That’s just speculation on my part, though. I don’t have one of those to test, and I could be totally wrong.
My flood light camera v2 stopped connecting to my network after Wyze made a firmware update on May 22nd. I have restarted router, cycled power on camera, and tried to reinstall the camera. My other 9 cameras do connect.
A post was merged into an existing topic: Wall-mounted Wyze display/tablet (10" or larger)
I asked to have your post merged with this topic because it seems like the same issue, and I’m still waiting for some more feedback from Wyze, as noted above.
Is it possible you’re not broadcasting your SSID? What firmware version is the app currently reporting for your Cam Floodlight v2?
3438 which was loaded on May 22nd.
1 Like