It sounds like you are using a Pan Cam with the Track Motion on. Since the headlights produce a change in the pixelation shading within your DZ, the cam will turn to track that motion. When it does this, your set home position, for which the DZ is set, is no longer useful as it is now blocking out the same pixels but on a moving FOV. Since the cam continues to move to track that motion, it will invariably maintain that object within the Included DZ and tag the object.
Videos aren’t necessary. What is helpful is a screenshot of the actual object that shows the green Motion Tracking box within your DZ.
That is correct. As I explained in another thread, the actual physical object being fully inside the Excluded DZ is not the factor determining if it is tagged. It is the size of the rectangle that is being superimposed over that object by the cam. If any part of the rectangle overlaps the Included DZ, everything within that box is considered included and will be tagged. If, on your screenshot of the object within the DZ, there is any green Motion Tracking box placed by the cam caused by the object, the AI Engine is evaluating the object for tagging. The cam only allows you to see the the portion of the box that is within the Included DZ. The AI Engine evaluates the entire box.
Even though you may have your Event Recording settings restricted to Smart Detection Events, this is not restricting the cam from uploading all motion events. The cam has no way of knowing if the event is an AI event or not. It has no onboard AI. It uploads every motion event to the server. If there is a pixelation change meeting your sensitivity threshold, it uploads regardless of what is in the FOV. The server AI then evaluates every frame. If it positively identifies a Smart Detection object and tags it, it saves the video to your Events List. If it doesn’t, it deletes it. Since you have the Track Motion enabled, the cam will follow any motion, not just AI motion, and continue to upload throughout that process.