Recent Change to Light Pixelation / Detection Algorithms?

I have a Cam v3 Floodlight installed that has been working nearly flawlessly since it was first installed and I tuned sensitivity (30) and the detection zones. I noticed between Sunday 4/16 into Monday 4/17 a noticeable change in how my camera was working and detecting/notifying.

I live on a busy street with quite a bit of road traffic so I have the detection zone set accordingly. Looking at the number of events alone - I used to receive at most 10 event notifications a day (depending how much activity we had coming and going from our driveway). As of Monday I am getting 100s of notifications every day from cars passing on the road, headlights, etc. I’ll attach a few examples of with the motion tags.

I’m wondering if anyone with inside knowledge knows if a new version of their AI model was released over the weekend? It’s been so noisy that I’ll have to turn off notifications. Yet it has been working exactly as I expected for close to a year (installed 5/17/22)…

Because of the issues I decided to try upgrading from → but there was no improvement which leads me to speculate on back-end changes that may have been recently introduced. I’m debating downgrading back to 9.139 to try and eliminate variables.


I’m only allowed one image per post so the above was one example.

This is my current detection zone:

Welcome to the forum! @shark

I have the wyze floodlight camera as well and will try and be of some assistance here.

Okay so from reading your posts , you’re saying that you’re getting too many notifications ? Are they labeled “complete motion” or are they AI event notifications?

From this you’re saying that you’re getting notified of cars passing by , headlights , are they labeled complete motion or AI?

From your screenshot of the detection zone it looks like that should block off the road and not detect any motion in the blocked off area.

I believe Wyze does a monthly AI update if I’m not mistaken.

1 Like

Can you post that full event? Not just a screen shot? So we can see what happens before and after that screenshots moment in time.

Hey @Rulwiz, they are all labeled as “Motion” events. If I don’t have cam plus and not using AI detection is the detection logic self contained on the camera itself or does it still rely on a ML model hosted in the back-end?

@Omgitstony I’ll attach the video from the example above (apologies for the sound). Where I am really seeing a difference is at night which I know there can be issues with headlights casting shadows, etc. What I find odd is it seems like the sensitivity of the detection changed (I’ve had my sensitivity set to 30 for the last year). I’ll post examples of this in a subsequent post.

No detection or notification (April 16th) - working similar to the previous year, despite the shadows/light bouncing off the house.

Detection/notification (April 17th) -

Another example from (April 14th) - Motion wasn’t detected nor a notification sent which is what I expected. I have my SD card set to continuously record so I’m trying to pull some more examples before they are overwritten. I had things tuned well enough that events like this wouldn’t trigger an alert but starting early Monday morning and this whole week I’ll wake up to several dozen motion events/notifications.

Right , complete motion notifications will alert you of cars headlights , light changes , wind , rain , bugs , basically anything that the camera can’t identify by the AI.

These are know as motion events and you’ll be notified by motion notifications. I would turn off motion notifications and only have AI events toggled on so you won’t be alerted so much.

I don’t currently have cam plus so I believe AI events aren’t an option for me?

After a few more days of monitoring I can say that the largest change in events are overnight due to the headlights reflecting off the side of the house. This wasn’t the case prior to April 17th so that’s why I was curious about potential changes to the algorithm that may have been released.

Just to follow up here in case any one else stumbles upon this in the future.

I ended up changing the floodlight’s Event Recording setting to be only triggered by the PIR sensor on the floodlight. That stopped the detection events due to shadows/light bouncing.