I've tested this exact scenario along a side path of the house. It works excellent. One thing to keep in mind... If your doing this in a general area, then you must take into account how movement would travel thru the area. Bound to miss some movements as persons walk thru.
In my scenario, along the side on my house, there is only 1 path thru, and then to either side in the front and back. So, I setup 2 zones (A & B) in the front, 2 along the path (C & D), and 2 in the back E & F). The edges of the zone are bordered by buildings, so unless they fly, there is no other way thru. Then I placed hotzones along the edges under the windows & doors. See attached sketch (It's crude, but get should get the point across).
Then I set then 'Object crosses zones' field to: A-B, A-C, B-C, C-D, D-E, D-F, E-F
I tested it by walking around in all different directions. It works.
Problem is, if someone walks from E to D (motion triggered), then walks to the lower side - that is not caught until they walk either thru the hotzone, or back to E or to F or D. So they could pretty much spend a while rolling around naked (or something) in zone D until they get tired and either fly off, or, walk thru another zone.
That's why I have the 2 hotzones. That's where windows & doors are (and my diamond cache).
That took care of 90% of the tree swag triggers. In early morning and late evening, when the shadows are the longest, the tree shadows are very long and therefore the normal movement of the shadow is also larger, and a large gust of wind will trigger motion. I could schedule a profile to turn this off during those times, but, I'd rather get false triggers than none.
Also, when doing this each zone must overlap the other.
The hotzones are excluded from the 'object crosses zones' and will trigger motion of the regardless of the other zones.
Pretty bizarre, ehh! Yaa, fur sure. lol
I stopped using it. It was just too much.
