Oh good! This happened to me last week when my cat peed on one of my leak sensors
I couldn’t turn off the Hazard remediation beeping, and it froze up my hub so that other contact and motion sensors wouldn’t execute rules. I had to manually reboot the hub to get everything to work again. Glad to hear this was a known bug that is fixed now, and in less than a week from when I first noticed it! Impressive.
Does anyone know what is meant in the Pan V3 firmware about fixing motor gaps? What was happening? Is this talking about how the Pan V3 wasn’t returning back to the Home location after motion tracking, or something different?
Update appears to have significantly improved the Return to Home bug. After setting waypoints and a Detection Zone, Live Streaming through extensive motion tracking events, and manually manipulating the PT FOV, the cam appears to be returning to the set Home point with a near undetectable variance. Currently testing in IRNV, will have better results in daylight.
EDIT: The bug is not gone. After a day of normal usage tracking objects with waypoints and DZ position set to an identical FOV, the cam has shifted up by nearly 2 DZ Blocks. Waypoints and DZ had to be reset for another day of normal use testing. Still not ready for prime time.
When Live Streaming with no motion, stream is fluid. However, when motion activation occurs and the cam Motion Tracks, the live stream consistently locks up for up to 10 seconds before it recovers. It seems that the faster the object moves, the longer the stream lockup. This live stream lockup can be duplicated when manually PT manipulating the cam thru the app. Cam movement is degrading stream quality and capability.
Pan V3 still lacks the granular “Device Notifications” for individual Smart AI toggles present in the iOS app and on the PanV1, PanV2, V2, and V3 updated firmware. It is still just all AI or nothing.
30s FF \ RW buttons on SD Playback are still not functioning. The first press of the 30s FF took me 6 minutes forward. Subsequent presses did nothing at all.
Hub firmware worked great! My cat peed on my leak sensor again TODAY! (I have a better solution to stop this in the works) And the hub allowed me to stop the hazard remediation reminder this time, and it didn’t lock anything up, so the Hub firmware is doing well so far.
My Pan V3 apparently didn’t update when I told it to a few days ago, so I’ll tell it to update again right now. and check again.
Hub firmware is doing great! The Pan V3 is staying connected a lot better vs error 90 every day. Updating the Pan V3 resets the event recording settings though. So instead of staying on “record all motion” it is changing back to “Smart Detection events.”
The Beta FW for the Pan V3, corrected the Privacy Mode Issue I reported.
When the camera is in Motion Tracking mode and then you put the Camera in Privacy mode, it shifts to facing down and then in about 15 seconds it will reposition itself to facing up in a default position. The Camera remained in Privacy Mode, just the position changed.
BETA UPDATE RESULTS
After Applying the Beta Update, the camera will remain facing down when in Privacy Mode regardless of the Motion Tracking.
Ok been on the new beta firmware since its release. Was doing good returning to the home position untill this afternoon, now it appears to be off again. Right to left seams ok, but up and down are off. Mine is mounted upside down, i have reset the home position 2 times and it is off again. It is now returning higher than the home position. Before the update it would return lower. I just have motion tracking on. Not having it scan waypoints yet. Will update when i find more
Connectivity on the PanV3 during heavy SD Playback footage scrubbing has been vastly improved. I manipulated the SD playback timeline fast and hard trying to get it to disconnect like it was doing before and I couldn’t break it in any of the cams, even the most distant.
I have also been testing the Return to Home Position issue and see that it is noticably better, but still not where it should be. Documentation reported back to @WyzeXiZhere.
As noted above in my last post, there are still outstanding issues.