Sadly friends, given the complete lack of response from Ring I don't think we are going to get much help from this forum post anymore. Primarily because the moderator for this post marked it as solved when the issue clearly persists, and we have all seen how much attention "Jennifer" actualy pays to our issues. I suggest that when any of you have a chance to make a call into the support line and go through the obligatory troubleshooting steps and have a ticket escalated to tier 2 support. I've called them twice already and apparently they are unaware of any issue with the Ring pros, but they are shipping me a new one as a possible remedy. So please call in and have an actual ticket created, at least that way we know the info is getting to where it needs to go and not buried by some bogus "solution" from an inattentive and indifferent moderator.
I have received a replacement, and so far, it is sensitive, but it is much better than before. (The defective one is being returned to them at their expense.)
As Kaimos said, contact support and ask for level 2 or a supervisor.
Don't take no for an answer.
The ring software has an algorhythm, which is supposed to learn specific types of repetitive motions, on a customer by customer basis. How do we know this algorhythm is working, since so many Ring doorbells including our own, is very sensitive, even after adjusting the distance parameters?
I'm having this same issue, not sure what has happened but it seems to be a problem for a lot of folks, if there is an answer please share with us. Thanks
I see that everyone else in the forum is having the same issue that I'm having . . . which I'd reported to Ring about the same time (19-OCT). I soooo loved (not) being awoken at 7:30am on a Saturday morning by someone jogging down the street, and then again at 7:45am, and then again at 8:10am. It has NEVER reacted to people on the sidewalk or the street. I've always use the lowest sensitivity level (which they'd used to indicate was for 'people detection only') and it worked near-flawlessly, only detecting motion by people on my porch and lawn, but not out at/past the sidewalk. Now they seem to have a special "people mode", which detects people EVERYWHERE in the field of view.
So, I've dinked-around with "Motion Zones" and the various sensitivity settings. I've had to draw my zones to exclude the street and sidewalk, so, now it'll essentially only see "feet" coming-up on my porch. If I use the new "People" mode, then it tends not to trigger, since all it's seeing is feet. When I turn-off "People" mode and set it to the lowest sensitivity level, then it mostly works OK, except now (as discovered at 4:42am and 5:39am, again on a SATURDAY morning!) it's picking-up headlights shining on my grass (which IS in the motion zone, so that I can try to capture feet on my porch and steps). Jeeesh, what a joke! I've submitted another complaint to them via e-mail . . . I'm sure I'll get no good resolution.
Guess I'll have to disable motion alerts during the night so I can get a good night's sleep . . . and then risk some doing evil on my porch (like breaking-in or vandalizing me).
I'm losing satisfaction with Ring . . . I'm going to start looking for somebody elses' video doorbell, and perhaps relegate this one to the back patio, which faces a woods (no foot traffic, no headlights...no false triggers) . . . and stop paying $100/year for the video archive service.
Oh yeah . . . did anyone else also notice the LACK of notifications on Halloween night? Of the 5 groups of kids that actually came that night, I was only alerted twice by the Ring Pro . . . and 1 of those times the alert came-in 10 minutes after the kid had gotten his candy and left! I think their system got over-loaded by all the doorbell activity that night (across the country). I can tolerate that happening . . . I understand that their system isn't 'scaled' properly to handle that 8 hour overload of activity. What I can't tolerate is being awoken at 5am on a Saturday morning (when I'm trying to sleep-in) due to someone's headlights on my lawn . . . when it NEVER used to happen at all!