@Ham wrote:
This is a serious problem. Unfortunately, Ring is unable to fix it. I reported it about 6 months ago and nothing was done to fix this very bad issue. A big stigma on Ring for this unprofessional business!
@Ham and @Ruuny ,
This original old post was started over a year ago by @SoriceConsulting , while utilizing the Generation1 Motion-Detection sensors. The Gen1 sensors do have a “Dwell-Time” of 3-minutes (the period that they ‘wait’ before they can transmit another Z-Wave signal to the Alarm Base Station). After the initial ‘triggered’ motion event (“motion detected”), the sensor will NOT send another Z-Wave signal to the Base Station until the Dwell-Time has expired (and “stopped detecting motion”). Also, Dwell-Time is not 4 or 5 minutes, that I’ve seen in some incorrect posts. Periods over 3-minutes are the result of continued motion being detected after the Dwell-Time and motion has not ceased. For Gen1, this is interpreted as a continuation of the same initial trigger event (but only for a little while longer). This prevents the sensor from sending out multiple alerts for the same motion.
https://support.ring.com/hc/en-gb/articles/360001133103-Re-setting-Your-Motion-Detector-After-it-Triggers
First, some posts in this online Ring Community website mistakenly state that if the Alarm is set to HOME or AWAY alarm Modes during the Dwell-Time, that FALSE idea that the Motion-Detector will be ‘bypassed’ and never activate the Alarm system ever! Once the Dwell-Time is completed without movement , the Motion-sensor will send a Z-Wave status signal to the Base Station that it _ _ clear & ready (“stopped detecting motion” ) , and will instantly trigger the alarm if it detects motion. Motion-Sensor Dwell-Time is set this way for multiple reasons, and incorporated “on-purpose.” It is constructed this way and Dwell-Time cannot be changed or adjusted by software.
Now, the newer Motion-Detector Sensors ( Gen2 ) only have a maximum “Dwell-Time” of 30-seconds , not 3-minutes for the Gen1. Also, unlike the Gen1, as soon as the 30-second Dwell-Time is finished, if it ‘sees’ ANY motion, it WILL send another Z-Wave “motion-detected” signal.
The likelihood that you exiting, triggering that Gen2 motion-detector to start the 30-second Dwell-Time ‘timer’, then exiting before the Exit-delay expiration, and then having a thief immediately break-in and start stealing stuff in the remaining Dwell-Time, is practically impossible.
To illustrate this better, let’s suppose you have the newer Gen2 motion-sensors and your Alarm Mode Exit Delay is set at 30-seconds, and you have mounted a Motion-sensor and Keypad both right at your doorway. Now in this example, as you go to the Keypad to arm the alarm system, your movement triggers the motion-sensor which commences the 30-second Dwell-Time timer. But let’s say that you are super-duper blazing fast and can then type your 4 digital code into the keypad, press an arming mode button, open your door, exit, shut the door, and deadbolt lock it, all in only 1-second. You gave yourself 30-seconds to get out, but the Dwell-Time ‘timer’ had already started a moment prior to you reaching the keypad. As the Alarm Exit-Delay counts down to arm at 30-seconds, the motion-detector will have already finished it’s entire Dwell-Time before the Alarm countdown!
For another extreme example, let’s suppose your Keypad is nowhere near your exit door, and a Gen1 Motion-Sensor is monitoring this door. You press the arm button and the 30-second Exit-delay countdown starts, and then you reach the door and exit with only 1-second remaining to arm-time . . . and suppose it’s at that very last 1-second instant that the Motion-sensor first ‘sees’ you and starts it’s 30-second Dwell-Time. In this unrealistic example, in 29-seconds your Motion-sensor will finish it’s Dwell-Time. Remember you are still walking away from the door during this 29-second period, so the thief is most likely gonna wait a few, for you to depart. But suppose you are super-duper fast and somehow manage to walk to your car, get inside, start it, and then speed-off in only 1-second. So now, a thief needs to instantly break-in and start stealing in the remaining 28-seconds before the siren sounds! As you can see, this example is an extreme impossibility, and that realistically the Dwell-Time will be finished before you even have reached your car. This example is totally unrealistic, unless this thief is magically even more super-duper faster than you!
Even if you own the older Gen1 motion-sensors (Dwell-Time of 3-minutes), and you set an exit-delay at it’s maximum of 180-seconds (3-minutes), in this case, the Motion-sensors will already be ready by arm time. And if you use a Gen1 sensor with a 30-second exit-delay, the absolute maximum time a thief could possibly have is 150-seconds, and that’s if the thief breaks-in instantly after you did your super-duper departure. If this short 150-second time still concerns you, then just hang out for a few at your door. Or invest in the newer Gen2 sensors (not available in all countries, but will be soon). But realistically in 150-seconds you are just starting your car (still at your house).
So, I disagree with you @Ham . This is NOT a serious issue at all.
OK, you might ask, _“How do you know the Gen2 Dwell-Time is only 30-seconds Max? I cannot find that Dwell number anywhere.” _ It is explained here:
https://community.ring.com/t5/Ring-Alarm/Things-you-DIDN-T-WANT-TO-KNOW-about-Motion-Detectors/m-p/49013#M4879
I hope this information is helpful to you and alleviates any major concerns you have about Motion-Sensor “Dwell-Time.”
@TechGuy42 ,
@Jennifer_Ring
, @jonnyd91 ,
@LSchaub
,
@uscpsycho
,
@DMossEsq
,
@Marley_Ring
,
@Ruuny
, @davefrombostons , @CrazyCat , @TimInTN , @Kris , @Finz