Detection zone seems to be not working. I am picking up motion in areas that are grayed out. I’ve tried this with and without motion tagging.
Blub cam firmware is up to date as of this posting
Anybody else see this issue?
I haven’t seen that, but in troubleshooting Detection Zone issues I think it can be helpful to at least temporarily enable Motion Tagging (as you mentioned) as well as sharing images of how your Detection Zone is set along with a representative image of something that was detected when you did not expect a detection event to occur—if you’re comfortable sharing something like that (I understand if you’re not). Ideally, the unexpected detection would also show a Motion Tagging box for comparison to the Detection Zone image.
This is kind of tricky, especially when an update was released earlier today and announced only a short time ago. Being specific about the version can be more helpful to others trying to assist.
Thank you for responding so fast.
Current version -----------------------------------------
Options enabled----------------------------------------
Detection Area-----------------------------------------
Resulting detection in void area--------------------------
You’re welcome! Thanks for sharing some additional detail, especially the photos. Those are the key, I think. I hope this helps:
That’s what I saw when I added the Detection Zone image as a 50% transparent overlay to one of your events with Motion Tagging enabled, and you can see that the lower-left corner of the green box is extending outside the exclusion (greyed) area in the zone you set up on the left side of the image. Because reflections like that are tricky, I’d probably tweak that area and make the grey squares cover more (if not all) of the window. It looks like you’re as low as you can go with the sensitivity setting, but if you extend the exclusion area you might be able to raise the sensitivity and find a good balance. It’ll probably take some trial and error, but that’s where I’d start.
thanks for your sharp eyes and I will try that
1 Like
You’re welcome. I wouldn’t have been able to tell for certain just by eyeballing the images, but doing it as an overlay can help, I think. If you find that the squares you select to “grey out” are extending into areas that you don’t necessarily want to exclude from potential detection, then you can also shift the camera’s physical position a little until you get a workable view. Getting things tuned the way you want to find that right balance between too many and too few detections/events/notifications can take a little time and effort.
Thanks for the suggestions. I increased the non detection zones to add margins and the unwanted detections seem to be blocked,
In reviewing the playback video from the SD card I noticed that the motion tagging algorithm seems to tags the initial motion and then “grow” the tag area vertically beyond the initial motion area. So if I have a just a motion in a single non detection square at the bottom, the tagging algorithm seems to grow it vertically into my detection area giving me an unwanted detection.
I just increased my non detection zone to full “vertical” column and this seems to work.
This is only my best guess 
I think what you’re describing is pretty typical, and a lot of people have found that they need to add a margin or buffer zone to the exclusion area in order to reduce unwanted motion detection where the Motion Tagging box extends outside that area and into the Detection Zone.