Yes.
The cam detects a change in pixelation within the Included DZ. In your case due to the perceived movement of the headlights reflecting off of the ground as indicated by the green Motion Tracking box that it overlays prior to the upload. The cam Firmware is restricted by the DZ in overlaying that box. That is why the green box only shows being overlayed within your Included DZ. This is the motion trigger that starts the upload.
The AI Engine, however, ignores the green Motion Tracking box. That is simply a part of each frame once it gets it. The AI Engine then overlays its own invisible Cartesian Rectangle over every single object it detects within the entire frame. I drew a yellow rectangle around the car to demonstrate.
If any single object within that frame is identified as one of your selected AI objects, the AI Engine then checks if it is within the Included DZ. But, it doesn’t check that by the shape of the actual physical object. It checks that by the invisible box that it put around the object.
Wyze uses Overlap Logic within their AI Engine. If any single part of the imaginary Cartesian Rectangle is overlapping into the Included DZ, every object within that rectangle is considered included as well.
As you can see below, the box that I drew overlaps into the Included DZ and would therefore be subject to tagging as if it were also in the Included DZ.
Also… The faster an object moves, the bigger the box around it appears.
The solution, add more blocks to your DZ.