I have a new system and am seeing around a 20-30 second delay for sensors triggering an automation rule. Example, when I open a door in our laundry room which goes to outside, I turn the light on if it is dark. The panel displays the sensor being open immediately. I have Lutron lighting so understand that the rule gets executed by ADC and therefore will have a slight delay, but this seems too long. I know things can happen faster as when I arm our system, those commands (executing a Lutron scene) happen almost immediately. Also, if I use the ADC app, Lutron RA2 devices usually activate in around 3 seconds. Is there a delay to see if the sensor was open/closed before reporting to ADC or something? Can anything be done to speed this up? Thanks.
Example, when I open a door in our laundry room which goes to outside, I turn the light on if it is dark.
Does this delay occur with all Automation Rules involving Lutron or just the Automation Rule involving sensor activity and Lutron Automation (Laundry Outside Light)?
Is there a delay to see if the sensor was open/closed before reporting to ADC or something?
There is a delay in reporting on the same sensor after the first instance of activity.
As a test, open the sensor and note the time, then note the time when the light comes on and let us know. We can check in history when both items are being triggered.
I just did a test. Opened that door and immediately heard my panel indicate the door was open. At the same time, started a stopwatch. Took 25 seconds for the light to come on. Using the app to control devices is fast (within 3 sec). Also, executing scenes, etc when arming the system also happens really fast. I did try the same thing on another door and it also was just as slow. Seems to be sensor automation. Thanks.
To best assist, what we mean is to provide us the timestamp of when you open the door, then the timestamp of when the rule occurs.
We can use this info to check in ADC history to see if the delay is before or after the processing.
So for instance, I see in your history that the door lock was unlocked, then about 25 seconds later the sensor open report came in, then only 1 second later ADC processed this and sent the Lutron command.
It looks like the delay may be in when the sensor activity is logged in ADC, but to be sure we would need to confirm when the door was actually opened.
12:55 pm today
We would need the seconds mark to be accurate. A better question would be did you wait 25 seconds between unlocking and then opening the door, or did you open the door immediately after unlocking?
Can you try it again? Unlock the door, then use the stopwatch and open the door 60 seconds after unlocking.
I’m curious if we will see that same 25 second delay then.
Ok. Unlocked the door. Waited 60 seconds. Opened the door (panel immediately announced door opened from the sensor being opened which my automation rule is based upon). Took 34 seconds for the light to come on. Started all of this at 1:33 pm. Thanks.
Thank you, that tells me what I would need to know. The door shows in history in ADC as opening 93 seconds after the door is unlocked, not 60. The delay is prior to ADC recording the open status.
On my own system right now, I can see a sensor status change logged in my ADC account very quickly after the sensor opens. I just tested and it took just under 2 seconds. We have had a handful of people report additional latency to sensor open reports before though on a few different panel types.
Can you try one more test? On a hunch, can you first disable Two Way Voice within your System Manager here on the professional monitoring page. Wait about 5 minutes, then try to open the door again. Does the rule fire quicker?
Did that. Did the same test. Unlocked, waited 60 sec, opened the door. Light took 25 seconds to come on. Maybe off a little as I was resetting the timer….
Did a second test. Took 34 sec.
Alright, let me do some digging with Alarm.com to see what might be influencing this in these cases
I also tried turning off the auto bypass on sensors. No difference. When we set the panel to stay last night, the automation executed within a few seconds. So, really only related to sensors. I have several use cases for this in our home. Hope they can find the issue and/or setting that maybe I need to do. Thanks for your help.
Any update on this? In general is still taking at least 30 seconds for the automation to occur. I did a test, where I opened the door and also looked at the ADC app. About 30 seconds before ADC showed the sensor open and the automation occurred at almost the exact same time. There just seems to be a general delay from when a sensor is locally opened to ADC registering the event (and subsequently executing the automation). Almost like the delay is waiting to see if it is an Open/Close… Lighting commands from the ADC app are done within seconds. Also, automation associated with security events (eg Stay, Away) also execute within seconds.
Alarm.com is investigating the behavior. A couple of users reported similar behavior a while back but there was no indication to a cause. I reached out to ADC with what we tested and they were investigating what was causing the delay. There is a bug affecting your sensor activity monitoring event logging in ADC. It seems to be a very rare bug.
I’ve been having this exact same issue - panel acknowledges the open door, but there is a ~30 second delay between that and when the light turns on…
I gave up and handle the automation locally. Its just too slow and somewhat inconsistent at least for me…
Ensure your panel’s firmware is up to date.
Then, check your automation devices to ensure they are working independently from the rule as well. Local testing and remote control through Alarm.com.
If the device is working correctly, delete the automation rule, wait 5 minutes, then recreate the rule. Wait an additional 5 minutes then test for resolution.