I have gotten about 123 motion notifications since the last firmware update. Of those 123, 1 was actually motion in my detection zone and not a car light 2 houses down. I have restarted it, reset it, fully rebooted it…nothing changes. Any ideas?
Welcome to the Forum, @nique1370! 
My first idea is wondering about details of your detection settings (how you have the sensitivity set, etc.) and especially what your Detection Zone and notification thumbnails look like, especially if you have Motion Tagging enabled. I should note that I don’t have Cam Floodlight v2, but the Wyze Cams I do use allow me to enable Motion Tagging (the green box that shows up on screen and indicates what in the image is triggering motion detection), and turning that on temporarily can be helpful in troubleshooting motion detection issues.
Do you use a subscription with your Cam Floodlight v2, and is it possible that the bulk of these new notifications are labeled as “Complete Motion Detected” when you’re trying to receive only Smart Detection notifications? If that’s the case, then you might be able to do something like this:
- Navigate to the camera’s Settings ➜ Event Recording.
- Under RECORDING PREFERENCES, select All Events and then tap Customize Detections.
- On the Customize Detections screen, deselect Other Motion (and possibly Other Sounds) in the NOTIFY column, then tap back to the previous screen.
- Back on the Event Recording screen, select Smart Detection Events (and optionally tap to double-check your selections on the Customize Recordings screen).
That may be necessary sometimes because the “Other Motion” and “Other Sounds” lines aren’t available when a user has Smart Detection Events selected, so you have to temporarily select for All Events in order to navigate to and deselect that option. It’s annoying, and some of us in the Forum feel that it’s a bug and have expressed this to Wyze.
Note that your selection on the Event Recording screen determines what destination is available:
- If the Event Recording screen has Smart Detection Events selected, then tapping Customize Recordings takes the user to the Customize Recordings screen.
- If the Event Recording screen has All Events selected, then tapping Customize Detections takes the user to the Customize Detections screen.
Since I don’t have this particular Cam model, I’m making some guesses about what options you have available in Settings, but this is another place I’d look if the issue is with an abundance of “Complete Motion Detected” events, because I’m wondering if something got reset with the update.
Something else you could consider is trying the Restart and Reset Services options on the main Settings screen, if those are available. If you do Reset Services, then I’d still go back through other settings to make sure the device is configured as expected.
@Crease Is there a way to notify the Wyze dev team to look into this bug/issue for Floodlight V2 since last firmware update? I have the same issue with getting hundreds of false notifications since the last update Sept 4th. It was working perfectly fine before this…
My first step would be to submit an app log and then visit the Support site to create a ticket that includes the Log ID. When you get an e-mail response from the “Wyze-E” bot after creating the ticket, use your reply to describe the problem and any troubleshooting steps you’ve taken in detail. It’s not a very efficient process, but that’s my understanding of how to get a log connected to an issue description so that it gets to the engineers’ attention.
When we see multiple users reporting the same problem here in the Forum, the volunteer team tries to ping someone at Wyze to see if we can escalate it (because there’s an indication that it’s more widespread and not isolated to a single user’s experience), but we don’t always hear back about that, so I’d try logging/ticketing first. 
The other thing that I’d recommend is describing your problem in an official release topic if you believe it’s related to a specific version of something. Those topics are usually in the Wyze News category (or possibly Beta if you’re enrolled and receiving those updates). For instance, if you think the problem is directly related to the latest Cam Floodlight v2 firmware, then you could post your Log ID and a problem experience/troubleshooting description (maybe just copy/paste from your Wyze Support ticket to make it easier on yourself) to Wyze Cam Floodlight v2 firmware update - Released 9/4/2025. Since topics in those categories are created by Wyze Team members, that should be another way to keep them informed of issues.
1 Like
Thanks appreciate the detailed information.
1 Like
You’re welcome! I hope that’s helpful. If I had a direct line to the developers, I could put together a detailed list of things I think need fixin’. 
@chris82, I have two additional thoughts:
- When reviewing events to see if the little USPS truck has driven by the front of the house today, I saw that I have a crazy amount of Vehicle events from a Cam v4 looking out a window toward the street. The Bulb Cam for the driveway that’s aimed in the same general area isn’t showing these. I think the tree in the front yard is triggering the Cam v4 (it’s breezy) and that’s causing a motion event, and then the Cam v4 is seeing the van parked in the driveway across the street, and then Wyze’s AI is labeling this as a Vehicle event. This smells like a back-end change that’s overly sensitive.
- New beta firmware for Cam Floodlight v2 has been released today: “Fixed a bug that caused device having higher event recording sensitivity.” That’s something you could potentially try if you’re feeling adventurous.
(That’s probably easier said than done with iOS devices. If you have an Android device, then opting into or out of the beta program is pretty easy.)
1 Like
Heyy ! Great news on the bugfix release for beta firmware. That sounds exactly whats going on with my Floodlight cam.
As for the beta program on iphone, I’m an Apple developer and use Testflight daily for beta testing my own apps so no sweat getting the beta app… 
Big thanks for the info and will be checking out the beta today! 
2 Likes
Maybe being an Apple developer will help? I don’t have any familiarity with that. My understanding is that Wyze has limited seats on the iOS side, and that’s why I indicated that getting into their beta track might be more challenging there than it is with Android.
1 Like
Installed the beta firmware and it seems to be fixed now. Haven’t received any false detections / notifications. This is great!
thank you!
2 Likes
You’re welcome. I can’t take credit for the fix, but I’m glad to try to point in a helpful direction.
1 Like