This is our 2nd pan 3 after the first had reading and card issues was replaced.
We have ONE waypoint set. It will work for a short amount of time then decides it wants to make its own home waypoint, which is usually pointing halfway up to the house overhang and not to our driveway.
Apps are up to date. We turned off and on. Reset. Done all the things that I’ve done when having issues with my other cams
I’ve been with wyze since the beginning. I still have v1 cameras that work from when they first came in the market. I have v1 v2 v3 pan v3 sensors etc.
But this is getting frustrating with the issues we keep having.
Can you confirm you do not have track motion enabled and the cam has the latest firmware?
Try removing your waypoint(s) and rebooting the cam, then aim it where you want it and set the waypoint. If it is still drifting that badly I’d suspect the gears are slipping and it should be exchanged.
Mine tracks motion all day every day (busy street) and it only drifts a little bit, which is resolved by an automated weekly reboot.
What do you mean have track motion disabled? Why would I turn that off? Isn’t the whole point of this pan is to be able to pan to motion? Otherwise, I’d just use my old regular cam. I’m gonna be pissed if I have to turn off tracking, it’s the whole reason we switched to the pan in that location
It’s def not the gears, the other one that wyze replaced did this as well. This one has done it since we got it…maybe 6 months ago or so?
I asked because track motion will cause it to leave its waypoints, and then 10-15 seconds later return to them.
I think there may just be confusion here about how the various features work, especially considering you’ve seen this with two cams.
Pan/Scan will cycle through the waypoints. If track motion is disabled, it will never leave those waypoints (other than you moving it in the app).
Pan/San with track motion will cycle through the waypoints, but leave them to track motion. After the motion stops (5-10 seconds I think) it will go back to cycling through the waypoints.
Track motion by itself, after tracking motion, will return to the last position the camera was put in. So if someone moves the camera to look at something else, it will go back to that spot. There is no “home waypoint” when you’re only using track motion, waypoints do not get used with only motion tracking. In that mode, they’re basically there for convenience so you can tap them to go to a certain spot, which now becomes the “home position” until someone moves it again. But again, after it tracks motion, it moves back to wherever the camera was before that, regardless of what waypoints are set. Does anyone else have access to be able to move the cam, maybe they’re not putting it back where you want it after? Or could someone (yourself or otherwise) be accidentally swiping on the image when switching between apps causing the camera to move? Just some ideas on how it may have gotten moved to a new position.
I’ve had this happen with Android ever since they introduced the ability to interact with apps on the “app switcher” screen. Swiping up to try and close an app or swiping to the side can cause things to actually happen in the app without you realizing it. Since swiping on the image causes the Pan cam to move, that could explain what you’re seeing.
I haven’t experienced this, but it’s good to know, and I imagine it’s a source of a lot of frustration.
I think asking about Track Motion is a good question, too. Trying to discern what features or settings might be involved rather than making assumptions is a good start, so hopefully @summerm will share some details and/or screenshots illustrating some current settings that might be involved with this.
I haven’t seen it with the Wyze app only because when I close an app I swipe up from the very bottom so not an issue, but other apps this has been a problem if I don’t get it quite right. I’m not sure if it depends on the app (whether it supports this sort of interaction or not). I did just try with the Wyze app and my Panv3 and it didn’t seem to do it, but I didn’t test all possible combos (full screen, portrait/landscape, etc). But I think inadvertent moving of the cam is a likely explanation here. Perhaps trying to swipe down from the top to see a notification but swiping on the picture instead, etc.