That is definitely frustrating when detection settings aren’t working as we intend.
I watched the video on a monitor, so I may have seen motion a little more easily than when viewing on a phone, but in the video there was some movement in the detection zone in the following areas:
The arrows are the ones with fairly significant motion. I don’t know what sensitivity level is set on the camera, but I do know that this much movement would trigger most of my cams unless maybe I turned the sensitivity level pretty low. But there are things we can probably do to help.
It is also worth mentioning that it seems that sometimes the detection grid we see in the app is actually slightly off from what we view in the visual User interface We have seen that when some people view it in iOS vs Android or portrait vs landscape view the detection zone borders seem to change. Lots of examples of inconsistent detection zone boundaries are illustrated throughout this thread:
So, I always recommend to people who aren’t using the AI to detect things that they don’t just black out to the EXACT area they want blocked out to the line, but if avoiding false motion detection is extremely important then you should black out an extra area around it to give it a buffer, then add sensitivity adjustments in and it will resolve the majority of false motion detections.
In this particular case, I would definitely black out the tree above the roof that I circled in the upper right. I can understand being hesitant about blocking out some of the other zones with circles in them since they are important for detection areas…maybe sensitivity changes can help with that a little bit. It might require some testing.
I highly recommend reading through the following thread that outlines a very similar problem as what is being reported here. There is a lot of helpful information in there about how to test for what the cause is and figure out the best solution between the zone and sensitivity:
I hope that helps in the end.
I do think these reports/posts from users are helpful. Someone from Wyze should at least look into making the detection zone grid match up 100% of the time and be reflective of the actual detection zone implementation (see the beta thread linked to above…last I checked, there was still a slight discrepancy when viewing the grid between different platforms, indicating it’s not showing us correctly on at least one of them)