RING DOORBELL 3 HARDWARE IS INCAPABLE OF DOING 2 THINGS AT ONCE!!

My Ring Doorbell 3 experiences a FATAL FLAW in the product design and sofware implementation. DO NOT LET THEM TELL YOU IT’S A WIFI CONNECTION ISSUE.

HERE IS THE PROBLEM:

  • When the Ring Doorbell 3 detects a motion event (or person detected when ringing the bell) the recording and processing of those events take priority and BLOCKS THE USER REQUEST TO ACTIVATE LIVE VIEW.

  • I can go into the app 100 times in a row and activate live view in less than 3-5 seconds BUT … the moment I receive “MOTION DETECTED” or “THERE IS A PERSON AT YOUR DOOR” …forget it - the product is USELESS for LIVE VIEW.

  • It appears that the RING DOORBELL 3 is only capable of recording and processing the event OR OR OR allowing the USER to view the doorbell live. (Both are impossible).

  • Apparently the folks at RING did not think to allow the homeowner to DECIDE if it’s more important to VIEW the live event and abandon the 20 second recording cycle.

  • In this case, If there is a person detected in your front yard in the middle of the night, you must wait for the Ring Doorbell 3 to finish the event before the “ACTIVATING LIVE VIEW” is UNBLOCKED. (After that the LIVE VIEW will activate right away… you know… when you’re now in danger).

The reason I am SO UPSET over it is because they continue to mislead people with their ridiculous claims that there is a wifi issue when people complain that they are staring at a “ACTIVATING DEVICE” screen in the app.

I’m also upset because I purchased a device which was marketed not only as allowing me to view HISTORICAL events but to view LIVE EVENTS. This is truly a known issue which RING is failing to disclose.

  • I have not read anything about the RING DOORBELL 3 where there is honesty about LIVE VIEW not activating, and being blocked when the user requests LIVE VIEW during a motion event. THIS is what they do not want you to know.

And NO… using the RAPID RING app does not speed things up. It appears that it is the HARDWARE with the limitation and not the SOFTWARE. Apparently the HARDWARE (the doorbell itself) can only do ONE THING at a time - either RECORDING and PROCESSING the event, OR relinquishing control to the homeowner to VIEW the LIVE EVENT.

The product absolutely, unequivically is incapable of LIVE VIEW at the same time of a MOTION EVENT. I have tested this use case 100 times and it is just not true that the product can do both at the same time.

IN fact, I would guess the RAPID RING app was created not to solve the issue, but hopefully to shorten the block-out time so customers don’t complain. They probably figure that most of the events will be viewed after the fact. BUT WHAT ABOUT A MOTION EVENT IN THE MIDDLE OF THE NIGHT? I HAVE TO WAIT 35-45 SECONDS UNTIL THE DUMB PRODUCT FINISHES PROCESSING THE EVENT?

SOLUTION: For the geniuses at RING, here’s a solution. Provide an OPTION in the software settings that allows the USER REQUEST FOR LIVE VIEW to be of the highest priority.

You can add a disclaimer that “Requesting LIVE VIEW during a motion event will end the recording of the motion event and you will not have the full 20 second history of the event”

How about that? Because that’s really the issue isn’t it? You are trying to finish up the recording of the 20 second motion event and thus BLOCKING the REQUEST for LIVE VIEW.

It’s 100 pct. true what you are doing and you KNOW this.

1 Like

Hey at least you actually get notifications that there’s motion. I just have an incredibly expensive brick drilled into our wall. At the VERY LEAST I’d expect it to still ring if someone pressed the doorbell. Especially since I, naively, purchased the Chime Pro. But here I am 3 weeks in with missed packages and missed knocks because people expect a MF doorbell to ring when the button is pressed. I’m about ready to start filing complaints and have already made sure to tell every person I encounter even contemplating Ring to run the other way. Not sure if there’s any sort of solution, but I hope you find a sufficient resolution.

Hey neighbors! I’m happy to step in here and offer some guidance on this concern. To clarify, a Live View can be performed during an ongoing motion event. However, if the motion event just finished, and you try to access the Live View, it could be delayed because the camera has to upload the recording after the motion event ends. You may experience more of a delay depending on your Ring’s connection, your internet speeds, and the strength of the connection your phone has.

We recommend that you have at least 2 Mbps download and upload speeds for the Video Doorbell 3. With that said, it is also important to keep in mind that other devices in your home will be connected to your wifi and utilizing the speeds as well. You may also want to check your RSSI and ensure it is within a sufficient range. You can learn more about RSSI in our Community post here.

@holhartz If your Doorbell is not notifying you of any events, there could be a few different causes for that. Do you see any events in the Event History, or is it not registering any events in addition to not notifying you? I’d suggest verifying your RSSI and internet speeds as recommended above, as well as trying to reset the device. You can reset your Doorbell by holding down the setup button for 30 seconds. Once that’s done, walk through a new setup in the Ring App by following the steps under Set Up a Device.

Should these concerns persist, please give our support team a call at one of the numbers availablehere. They’ll be able to take a deeper look at your device and narrow down what may be going on. We’re taking additional steps to protect our team and help reduce the spread of COVID-19, so this has resulted in longer than normal wait times. If you are outside of the US, please read our response to COVID-19here to see how to contact support. Feel free to let us know what support recommends if you contact them, or what you’re able to fix and diagnose yourself, as it may help other neighbors! I’m also here for you both, and happy to follow up accordingly. :slight_smile: