Just got my v2 cam setup yesterday, firmware upgraded today, and now I get events for everything outside of my detection zone. My SD card is on order, so I can’t revert to old firmware. Not a good first impression, hopefully this isn’t a common occurrence.
I’m having the same issue, way to sensitive no matter what the settings are. Has anyone heard from Wyze regarding this?
Seems like a major F*** Up.
I cleared my detection zone, remapped it, and it seems to be working now. I’ll know for sure tomorrow since the lighting has changed significantly. I’ll report back tomorrow. Might be worth a try to see if this works for you.
No luck. Even with a restart after.
In this new firmware (ver. 4.x.6.218), we upgraded the vision algorithm for motion detection. Depending on the specific scenario, some movements (such as moving leaves and tree branches) may be more sensitive to the vision algorithm.
We recommend using the green rectangle that is generated by the motion tagging to identify the motion detection zones. The green rectangle indicates the largest rectangle of the moving objects.
The motion detection is triggered when there is an overlap between your active detection region and the green rectangle. We are not displaying the green rectangle if it doesn’t overlap with the active detection zones. However, if there is any overlap, even if it is very small, the vision algorithm considers that as a trigger of motion detection.
Thank you for the thorough explanation. How does the detection sensitivity play into this? How “much” overlap there must be before a motion event is triggered?
Thank you! Great question!. So, behind the scene, the sensitivity is translated into the size of moving object, which is the green box if you have motion tagging on.
A high sensitivity will trigger event if a smaller moving object is detected vs. a low sensitivity only trigger an event when a large green rectangle is generated.
Did I explain myself well?
That all makes sense. But why is it that moving grass in the wind is triggering motion. Even at a sensitivity value of 1. The last firmware revision had no issues with this.
Yes, you gave a good explanation, thank you. This is how I assumed the sensitivity setting worked before, but your statement, “if there is any overlap, even if it is very small, the vision algorithm considers that as a trigger of motion detection,” made me re-think this. So if I’m understanding you correctly, the vision algorithm is a two-step process: 1) There must be some overlap (any amount) within a detection zone, and 2) the bounding rectangle of motion must be of a certain minimum size, based on the sensitivity setting.
Did I get that right?
EDIT: I assume that the amount that the motion rectangle intersects with the detection zone is also taken into account? Otherwise you could have a large tree generating a large detection rectangle outside the detection zone, but if even one leaf happens to intersect the detection zone, an event is triggered (not good).
I’m having exactly the same problem since the upgrade. Will revert to the former firmware when I get home tonight. Some upgrade!!!
Thanks, I need to adjust my 3 cameras I have on the “Plus” program, or I will exceed my Comcast data threshold!
Thanks for this, but unfortunately everything does not always work with the box. when you place camera in areas many times you are limited on where you can put them. I have one that if I put the box were it gets no interference it would cut the head off of who ever was walking up. As I said in the original post I was not having this problem before the update and could capture faces.
Was getting a lot of events again today. Remapping the detection zone to be further away from my tree seems to have fixed the issue. I needed a buffer of about 3 squares to stop wind blowing the tree from registering as an event.
last update is a major disaster. Wyze needs to send out a firmware rollback.
Every outdoor facing camera (I have 9) alerts every five minutes rendering them useless.
Come on, Wyze. You can roll out a vacuum, sprinkler, watch, and assorted other products, but you can’t roll out an update that works.
Stop trying to fix this recent update. Give me back the previous update that worked and stop using Wyze camera users as your guinea pigs.
I agree with elcheapocooks ROLLBACK this update and stop using your customers as GUINEA PIGS!!
Don’t you have some beta users test this crap out before you make it public???
Someone posted on another thread. There are a bunch of complaints
“UPDATE 11/19/20: We are pausing the .218 firmware and have pulled the files from the Release Notes page as we investigate the increased motion detection sensitivity for Event videos. Thank you for your patience. Good morning, forum folks! iOS app 2.15.41 is launching today to improve Wyze Cam v3 connectivity now that we’re close to shipping! wink We also have 4.X.6.218 firmware for Wyze Cam v2 and Pan. It adds a custom detection zone, adjusts logic, and fixes bugs! Read our Release Notes: …”
Although I agree with @elcheapocooks and @bluu, maybe not as harshly put though
I am curious what the testing process is though. How was this not caught?
The new detection zone mapping is awesome, but the execution makes notifications and monitoring completely useless at the moment.
I doubt a rollback is feasible at this point, but someone needs to put their a** in gear and work some bugs out.
My biggest problem is the shimmers of light or the ripples in water from wind. I cant avoid water in my green box setting. Its in the background and i cant box it out. If that can be fixed it would solve most of my issues. minor water movement or sunlight reflecting in the water did not trip the camera before the update
Would you please post or PM me the video clip if you think that is a false motion detection or you think the .218 firmware is too much sensitive. Also, a log submitted with the false motion detection will be helpful. We think it is more sensitive too certain specific scenarios so we would like to analyze your specific scenario.