Well not sure where you read that, Waypoint #1 has never been an “auto return” point. If your cam is facing there when it starts tracking motion, yes, it will return to that point. Just like any other point you may face the cam to, once motion stops, it returns to the point it was facing when it started tracking.
Not any sort of programming error, it specifically gives you a message when manually moving the camera that “because you have a detection zone set, the camera will automatically return to that position after 15 seconds”. It was clearly an intentional design.
I’m assuming the reason they’ve added this new restriction is that it was confusing people since the DZ really doesn’t work as expected when track motion is on. They were probably getting a lot of support calls and complaints about it. But unfortunately they’ve also removed a useful feature in the process.
So if they are keeping it this way, they should implement a feature like you describe where it will return to waypoint #1 15 seconds after the camera is manually moved (or have that option).
I didn’t explicitly say that it exists, it was just a word choice to differentiate.
Lets, say I want to move the pan cam to position #1, then after 2 minutes, I want to move to position #2. I’d be pissed if if it moved away to another, unintended position before I moved it to position #2. That’s what I refer to as, “manual” mode.
So you mean “track motion” and “pan/scan” disabled. In which case nothing we’re discussing here comes into play. We’re only discussing the behavior of “track motion” and the ability to have it automatically reset after someone manually moves it, which the DZ has always provided as a feature, creating a permanent “home” position.
If you want the camera to only move where and when you want it to, then obviously you disable those two features. That’s irrelevant.
Well then I have no idea why you’d be pissed if the cam moved on its own. If you have track motion enabled, it will move on its own, you’ve asked it to.
The only “manual mode” I can think of in reference to these cams would be both of those features disabled. Then the cam will always be where you tell it to be.
Anyway, it seems the only way to get this behavior back is either temporarily or permanently install an older version of the app. If temporarily, then you can re-enable DZ and track motion, and then after going back to the latest version, never disable either one. That’s assuming this was an intentional, permanent change and won’t be changed back.
The only other workaround is to set a single waypoint and enable pan/scan. That way it will return to that waypoint every 10 seconds. One issue is that could be annoying if you’re 8 seconds into the cycle and trying to manually move the cam. The other issue is I’m not sure how pan/scan interacts with motion tracking, but I believe the priority goes to the motion tracking, and when that stops it returns to the normal pan/scan (which with only one waypoint set, is just moving back to “home”). And of course you can’t set any other waypoints for convenience use unless you want it to scan them all the time.
Unfortunately it looks like the latest app version now enforces this no matter what. If I enable both on my old phone, then view the cam with my new phone, it pops up and forces me to disable either Detection Zone or Track Motion.
Additionally tapping the waypoint no longer moves the camera to that waypoint. No idea what they’re doing over there. I’m tempted to just downgrade back to 2.5 on my newer phone too. That app has been rock solid and stable.
EDIT - deleting the waypoint and re-adding it fixed that, it now goes there when tapped. Still annoying that they’re forcing the removal of the DZ. I want it to return “home” after I manually move it if I forget to tap the way point…
EDIT 2 - Apparently there is now some difference between Waypoints with the 2.5 app and 3.x app. If I set a waypoint on my old phone, tapping it on my new phone does nothing. If I set one with my new phone, tapping it on the old phone does nothing. People with the 3.x app are going to wonder why they’re no longer working…