One of my fully updated Wyze Cam V2 cameras is getting tons of false positives by triggering on motion far outside the detection zone I defined.
The camera is aimed through a window at my driveway with the driveway marked as the detection zone and with the street beyond it “unmarked” so it is not part of the detection zone. Unfortunately it doesn’t trigger on motion in the driveway and always triggers on motion in the street. I’ve played around with various sensitivity settings with exactly the same results.
My understanding is that the green boxes indicate the detection Zone and that the grayed out ones are outside the zone. This is how all of my other cameras operate. Except one which seems to either be ignoring the defined detection zone and triggering on motion exclusively outside the zone, or is inverted (i.e. triggering only on things outside the zone.). (I haven’t tested the latter theory, but it seems to be what it is doing!)
Anyone else experiencing this? Is it a bug? User error? Some obscure setting I may have accidentally triggered? I tried searching the forums but couldn’t locate anything similar.
I’ve also included 3 screenshots clearly showing the triggered detection areas that are outside of my predefined zones… (even if they do overlap slightly (by a fraction of a box here and there), it seems to never trigger WITHIN the zone regardless of the sensitivity…)
Agree that you seem to have detection setup as you wanted. Lower numbers on the sensitivity settings should reduce false positives but in theory at least you shouldn’t be getting any triggers from outside the defined zone. It is possible that something else is actually triggering motion like a reflection in the window, but nothing is obvious from the screenshots. Do you have any way to test this by moving a different camera to this location and configuring it to do as you want? That would at least help determine if it is the camera or something else.
The green outlines indicate where the motion was detected, right? That gives me confidence that it is detecting it in the zones that are supposed to be off.
Regardless, depending on how much free time I have (hah!), I may do your experiment…
It just dawned on me that in a prior application this camera may have been rotated 180 degrees. I’ve since done a factory reset, but I wonder if somehow the old setting is still somehow not reset and somewhere behind the scenes the camera (or software) “thinks” it is upside down which may be confusing the detection zone. Total long shot, but, I’m grasping at straws here…
Probably since they sell window mounts for the V3. Others have come up with home-grown window solutions such as 3-M velcro type products. Biggest issue seems to be reflections from double-pane windows.
Why is it doing that? Cause the grid detection system is junk. It’s never worked correctly since day 1. I fight with it all the time. Just incredible that this can get passed out to the customer.
It doesn’t work overall. I have V3 and V2 cameras with this grid system and it does not work correctly. Not at all. Hasn’t in over a year. I still get multiple notifications inside the grey areas of tree movement for example. Just nuts, but then these aren’t meant to be anything more than toys.
Have you tried removing the camera from your account, doing a factory reset and adding it back? I know it’s a lot of effort. Also, what firmware version is on the camera? You might consider doing a direct firmware update from an SD card to see if maybe there was an issue in the update you ran.
Also just noticed that a tiny portion of the trees and bushes are included in the detection zone which may be activating the motion detection.
I know this seems a bit foolish, but I would first try swapping that camera out to another location. I would bring a different camera to that spot at the front of his house and see if its the same behavior. If not the same, then I would follow WildBill’s advice to refresh firmware or remove from account and factory reset.
