Can anyone suggest a creative idea to combat a V3 pan cam being triggered to motion track vehicle headlight shadows at night?
Since detection zones can no longer coexist with motion tracking, this scenario seems impossible to solve, having to choose one operational mode or the other.
The shadows are cast on a neighboring home as vehicles pass on the street.
Unfortunately other than aiming the cam differently so it doesn’t pick them up, there is no solution for that.
The Panv4 has some onboard “smart tracking”, not sure how well it works or if it would be suitable for your needs. Basically it will only track when it sees a person or vehicle (if you set it that way).
You can try reducing the sensitivity but I think if you reduced it enough to ignore headlights, you’d miss other stuff.
Thanks for the reply!
I already reduced the sensitivity and so yes, it seems like a losing situation.
I guess the pan tilt motor is built for the scan feature so it should hold up, but I have to imagine the constant movement every night is going to wear something out… Not to mention the unnecessary use of storage.
This actually came up in another thread recently. I have a panv3 overlooking a fairly busy street with track motion enabled for 3 years now. The thing is constantly moving and no signs of motor issues yet.
Neighbors say it looks like it is watching a tennis game, constantly going back and forth.
Mine is on continuous recording so it uses the same storage either way.
Some will use 2 or 3 static cameras like v4s rather than the pan cam. That way you can cover the same area, but use detection zones to block out stuff you don’t want to trigger alerts. You also never miss anything because the cam panned away to track something else. So there is that option too.
Yea there is that option . But because I upgraded to the v3 pan & it’s at my other property in a remote location, it’s not convenient to get back to it to completely change configuration.
If I’m not mistaken, this restriction was not always there. sigh
So here is what the official Wyze support bot said when asked about it. Seems pretty contrary to how it works unless I misunderstand.
==================
Cannot set detection zone and enable motion tracking.
You’re absolutely right! Here’s how it works with Wyze Cam Pan v3:
Detection Zone lets you define a specific area for motion detection.
Motion Tracking makes the camera rotate and follow moving objects.
When Motion Tracking is enabled, the camera may move away from your Detection Zone. After 15 seconds of no motion, the camera will automatically return to the Detection Zone position and reinstate it.
So, you can set a Detection Zone and enable Motion Tracking, but the camera will temporarily leave the Detection Zone to follow motion, then return when motion stops.
If you turn on the Pan Scan feature, your Detection Zone will be disabled and set to fullscreen. You can re-enable the Detection Zone after turning off Pan Scan.
Let us know if you need more details or help with setup! 
Actually it was. It used to be that you could set a detection zone but it basically had 0 effect if you had pan/scan or track motion enabled. So they made it so you can’t have those features and a detection zone enabled at the same time because it was confusing people (not working).
The one nice thing about the way it used to be, it acted as a forced “return to home” after you manually moved the cam. I believe DZ still does this on the Panv3 but since it gets disabled when you turn on those features, I have to be a bit more mindful to tap my home waypoint after moving it manually. Was nice to have it forced to go back there after a bit.
In reality it would be great to have a “tracking zone” - where you can tell it to ignore/not track stuff in certain areas. I suppose the DZ at the home waypoint could act as that. But the logic to implement that would probably be pretty complex, like should it stop tracking something in the zone when it goes out of the zone, or continue - and if it continues and something new moves, should it track that even though technically it is outsize the zone. Etc.
Yeah that’s old info (thanks AI). Fact is the DZ had absolutely no effect when you were allowed to set it up that way. It would track motion from anywhere in the field of view, which would then put the motion inside of the detection zone, totally defeating the purpose. I’ve had mine long enough to remember the old way and I remember being very confused as to why it was tracking and recording stuff outside of the DZ, but then gradually figured out that the DZ had nothing to do with motion tracking. Would have been nice if they could have implemented it so stuff outside the DZ wouldn’t “initiate” tracking either. But due to all the confusion (and I’m guessing support calls) they simply made it so you can’t have both and added the warning.
In reality, like I mentioned in the previous post, the only thing DZ did when you had track motion enabled was ensure the cam always returned to “home” even if you manually moved it. That still holds true for DZ, you just can’t use that “hack” with track motion anymore.