I recently purchased the D210 and have seen many reports of the incorrect behaviour regarding vehicle detection. 

When 'vehicle detection' is activated, and an activity zone is set, the camera still detects motion outside of that zone - for example, a vehicle passing by on the road, out of my declared activity zones. Then, if my own vehicle happens to be parked on my driveway, stationary, but in the activity zone, the camera's 'AI' incorrectly attributes the motion to the stationary vehicle and wakes up/sends notifications.

Steps to recreate: position the camera pointing to an area with a parked vehicle and a road beyond it. Then, activate vehicle detection, and set an activity zone that includes the area of the parked vehicle but NOT the road beyond. Wake sensitivity should be set to a reasonable value (mine is set to 8 - I haven't tested it at different values as the issue is not related to sensitivity inside the zones, but to the zones themselves). Once the zone is set, await a vehicle passing by outside of the activity zone and note that a 'vehicle detected' event is triggered, with associated notification/actions. 

Tapo support have told me that this is 'normal' behaviour as my vehicle is in the activity zone. However, I don't believe this is what most users would expect - a stationary vehicle does not trigger an 'event', it is the motion outside of the zone that is triggering the event, which the AI is then incorrectly attributing to the stationary vehicle because it's the only one it can see.

To resolve this, I would suggest that the camera's detection software is amended to simply consider activity zones BEFORE activating any further AI algorithms or detection code. If the camera were to just disregard any activity it sees that is beyond a user's declared zones, I believe this errant behaviour would be resolved.

As it is, vehicle detection is useless for monitoring whether my car is being moved (for example, if it were being stolen!), or whether another vehicle is arriving, as events are triggered even when it is stationary due to the motion outside my declared zone.

If that is indeed the 'normal' behaviour, then what is the purpose of 'activity zones' if they are ignored when the camera is looking for activity? It should only look for activity (I.e. Events or motion - a stationary vehicle is neither an 'event' nor 'motion'!) within the declared zone.