I’m going to detail the problems enabling Snapshot Capture caused on 2 of my 5 cameras in case others have this issue. This will be a long post to get my points and details across.
To start, I have 5 Ring cameras, all wired. The RSSI rating is typically around 35 - 50. I’ve confirmed with Ring tier 2 support my firmware is up to date on all devices. My (Android) app version is also up to date–3.21.1 as of this writing. My Doorbell Pro power is excellent (almost always over 4,000mV ). My WiFi is quite strong and fast, and nothing has recently changed in my network. Finally, my motions zones of all my cameras have not been adjusted, nor were the sensitivty settings touched. The below problem has nothing to do with motion notifications, or the Ring app (wife and I both have the same version of the app installed, using the same account).
Let me also preface this writing by saying all of my recorded video lengths, since I’ve had these cameras has always consistently been between 1:04 to 1:08 seconds in length. For example, if I leave my house to walk down my driveway and get my mail: the recorded video begins just before you see me open my front door. It gets me walking out of my front door, and the whole way down my driveway.
On New Years Eve I noticed I now had the Snapshot Capture feature available on all my cameras. I was thrilled to finally enable this, so I did so on all 5 cameras.
**The Problems: ** 2 days after enabling Snapshot, I noticed my Doorbell Pro no longer correctly captured motion events. It was missing the start of the motion that caused the motion event; that of which that caused the camera to record. I was no longer getting people approaching my door, or our cars pulling into the driveway. The recorded video would begin AFTER the cars were already parked or as a person was already at my door, rather than approaching.
I let this go for a few days with no improvment, then called into support on Sat 1-4-20. Prior to calling support I rebooted my router and modem, just because it’s something that should always be attempted first. While on hold, awaiting to speak with tier 2 support, I decided I’d try rebooting the DB Pro by holding in the reset button for 30 seconds, BUT, I intentionally never went back into setup mode to re-add the DB Pro. I only allowed it to fully reboot. Rebooting the Pro temporarily fixed the issue. The Pro was again capturing the FULL motion event, start to finish like it always had worked for months prior. I conveyed this info to the tier 2 support analyst, and we called it a night, and it’s fixed.
2 days later, again, on Mon 1-6-20 the exact problem returned on the DB Pro after working fine since the last reboot. Without calling into support, I again rebooted the DB Pro using the above method. This again fixed the problem.
The next day on 1-7-20, my Wired Gen 2 Stickup Cam started doing the exact same thing: Chopping off the first several seconds of the motion event. UPS delivered a package that day (ironically another Ring product) and the recorded video didn’t start until he was walking away, back to his truck. I rebooted the Stickup Cam, and again, this fixed the problem until the next day.
On 1-8 the same problem returned on the Stickup Cam. After almost a year of it working perfectly, I now have the EXACT problem on 2 of my 5 cameras. The only thing that had changed recently was enabling Snapshot Capture.
Finally, that same day on 1-8 I decided to disable Snapshot Capture on all 5 cameras since that was the only recent change, then reboot my Stickup Cam again. The problem has not returned on any of my Ring cameras since disabling Snapshot last week.
As I was having these problems, I was ‘starring’ the events to show Ring support should I call back in again. It wasn’t until I reviewed them on my Windows 10 PC app that I noticed the difference in the recorded video lengths: When my DB Pro or Stickup Cam had the issue, **the recorded video lengths were only 55 to 58 seconds long instead of the aforementioned 1:04 to 1:08 seconds. ** I cross-checked the time lengths recorded as shown in the Windows PC app against the Ring Android app and the times matched perfectly.
In the end, I have no doubt enabling Snapshot Capture, after about 2 or so days caused 2 of my 5 cameras to record shorter videos, therefore missing the beginning of the motion event that caused it to record in the first place. I don’t believe any motion events were missed during this time, they just were not correctly recorded. After months to almost a year of everything working perfect, with nothing having changed on my end, except enabling Snapshot Capture, 2 cameras expereienced the exact problem withinn less than a week after enabling that feature, and continue to work fine after disabling Snapshot. Coincidence?
Snapshot worked fine while I had it enabled, and it’s a cool feature for sure. However, provided my cameras are correctly working, I don’t ever see myself watching time-lapse images to see what happened between recorded motion events. Having my cameras work right is my top priority, which, they do as long as that feature is disabled.
If anyone else has this problem, disable Snapshot Capture and reboot your camera.