I UNDERSTAND YOUR PAIN! I do!
Unfortunately this is what wyze’s AI brain see…
The AI will detect the car, draw a big honking green box around it… IF ANY PART OF THIS MAGIC GREEN BOX CROSSES INTO A DZ! WOOTO RED ALERT!
See my very very CRUDE GREEN “art” 
It crosses the DZ border with out permission and WOOT ! WOOT! Alert.
I feel your pain… Same BS here. The AI logic is flawed here, they have dug their heels i in and don’t see it that way… I am not sure what my plan is … yet…
As I explained above, it isn’t where the actual physical boundaries of the object are. What determines if it is “IN” the Included DZ is where the bounding box is that is superimposed over the object. That bounding box only shows the user the small portion of the box that is within the DZ (green Motion Tracking Box). However, the AI sees the entire bounding box, even the undrawn portion in the Excluded DZ. I added a yellow approximation box to demonstrate.
Should that bounding box overlap even slightly into the Included DZ, everything within that bounding box is fair game to be tagged by the AI Engine. This is their Overlap Logic.
This is why the vehicle is being tagged.
And this is the point I and CEConti is trying to explain without getting through.
Basically to ACCOMMODATE this FLAW… the DZ would have to be SEVERELY, SEVERELY LIMITED.
To my new art work the purple box… DaVinci I ain’t and I hope the original poster doesn’t mind my use…
That PURPLE BOX is ABSOLUTELY PATHETIC! 
NO! I should be able to set it to something closer to the road. Similar to what CEConti has…
The POINT I and CEConti want is to DETECT POSSIBLE THREATS/ISSUES as they cross the boundary… and that boundary as you are showing it is way way to close.
What is generating this MAGIC HIDDEN BOUNDING BOX??? Your yellow box. HINT: Do NOT REPLY “proprietary” software. I don’t want to hear it. Nor does any one else… I am sure this is some AI proprietary logic… So lets ACCEPT THE FEEDBACK. ITS TOO BIG! What ever generates that needs to GENERATE A SMALLER BOUNDING BOX. Period. End.
We are TRYING TO PROVIDE CONSTRUCTIVE FEEDBACK, and getting STICK HEAD IN SAND RESPONSES…
Accept: Its is flawed, it needs attention, and lets get it fixed!
I will post this again, I designed some software with a UI… Got feedback from the USERS and the feedback I did not like… You know what happened?? THE BOSS SAID MAKE IT LIKE THE USERS ARE TELLING YOU! Period.
That is what should happen here. Listen to this feedback, and fix it.
I honestly don’t think you fully understand. I don’t work for Wyze. I am not a Wyze Employee. I am a Wyze customer. A user of Wyze cams just like you. I don’t design the cams. I don’t design the software. I just know how it works and how to effectively work with it. And I really don’t think you are getting my point throughout any of these many exchanges.
I am not suggesting to you or to anyone else that this is better than it was. I am explaining to you the way it is. How it works now. I didn’t program it nor do I have any ability to change it.
You have a choice. Work with it the way it is or move on. Ranting at other users who are explaining how it works doesn’t help in any way but to alienate them from responding to your posts in the future.
That’s because that is a cropped and enlarged clip. It is not the entire FOV as posted above. What FOV has only 24 boxes?
Yellow Box Answer had you read above:
True logic software answer: Who knows? Ask Wyze. It’s Proprietary Software They Developed. You have already read in my other posts that I too believe the use of a rectangular bounding box introduces too much non-object area into the Included DZ. Did you forget that post replying directly to you?
Then you are doing it in the wrong place. The definition of insanity is doing the same thing over and over again and expecting different results.
Wyze doesn’t monitor open forum threads for feedback. The forum is for user to user discussion, exchanging of ideas and information, and to help each other deal with issues. The forum is Moderated by User Volunteers. This is primarily a User to User Forum. There are only very select few topics and categories that Wyze does actively monitor for user feedback or participate in. Those are the only hopes that you will have that Wyze might read and consider your feedback for future software development. This thread or any of the others you have been posting in aren’t one of those threads.
That is likely becoming the direction … 20 alerts a night, or other times ( Nope, I am not turning off notifications, whats the point of that!!! ) 
for crap that is not an alert! I don’t give a whip about the neighbors or them coming and going. Thats why the DZ is set to exclude that…
No, I understand quite well at how it works… as I suggested at the start…. It was my guess and correctly that something in the backend was looking wider than the green box that it shows.
I was correct. This is flawed… The math which generates this generates it too big. Either shirnk that math, or look at the DZ and go? Hmm… only trips 10% DZ… Nope… Or DZ edge detection and how far into the DZ , but if the majority of the MAGIC YELLOW BOX that we can’t see is OUTSIDE THE DZ then its not an alert/trigger.
As for the forums… well… if you are a “Forum Maven” who appointed you that? Wyze. So you have some means to give them the feedback, thus help to get it fixed, from here I would surmise. And honestly WYZE ITSELF should HAVE SUPPORT STAFF PAID TO HAVE THEIR FINGERS AND EYEBALLS HERE! Nope… I don’t do twitdiot or dorqbook etc… FORUMS is what I use… ML’s, UseNet, dig, gopher…
I’ve tried to convey that your “work with it” suggestion is not a solution. Its a HUGE HUGE COMPROMISE to the purpose and use of the cameras. Thats what the point of that purple box was/is… extreme hyperbole… Basically to work with it… I and the other user would have to so diminish the DZ’s that it would be basically that purple box. Whats the point of that? It would NOW MISS 80% of stuff I WANT DETECTED!
That is not a solution.
Thanks for the reply. I’m wishing you the best of luck in resolving your issues.
