Thanks @bamarayne. I tried this also, uninstalling SmartAlarm and setting delay with “Send Status” set in ULM, but the delay still does not have any indication on the keypad. Is there a chance my keypad or its firmware is not correct for this DTH? The back of the keypad says Centralite 3400 (not 3400-X).
This is the firmware in the API Device Page:
…and preferences in API:
Ahhhhh, mine are model 3504-L. They are the iris keypads.
The centralite 3400 should work just as well as the Lowe’s 3405, they’re
really the same keypad in a different housing.
Make sure you have the keypad selected under Arming/Disarming options in
smart alarm, so it actually sends the delay notices to the keypad.
i am using the iris keypad and getting the same problem. i cant get the entry or exit delay to work at all on smart alarm no matter how i set it up.
Thanks all,
I ended up removing all components of this setup including the device handler and both App Codes in my API and restart from scratch (again). This time I was able to get the Exit delay beeps from the keypad when set up for ULM and SHM, but not when I configured everything as stated for the SmartAlarm app.
However, I am happy with this setup considering the SHM integration works this way and the alarm status is reflected on the keypad.
I managed to create an entry delay using a Piston in CoRE Opening a Simulated Contact sensor activated 30 Seconds after my actual contact sensor(s) are triggered Open and Closing after another 10 Seconds. I also used the piston to make the Centralite Keypad Beep every 2 seconds during the delay. Will update with the CoRE setup once I have tested it for excessive lagging, etc (currently having unrelated connectivity issues).
You should be able use the entry delay directly on the keypad in Core by setting a custom action on the keypad, and call the “setEntryDelay()” method.
That’s probably easier and more reliable than triggering a beep every 2 seconds via a Piston.
–Zack
This is an interesting idea and I’m not sure I understand.
I’m doing something similar to @pmgauthier to get the keypad to beep when motion is detected in parts of the house but the system is armed… with out triggering an event it the SHM.
Scott
Thanks @zcorneli,
I tried setting up a piston to do so, but it is still not working. I may have my parameters wrong?
I am still able to activate a single beep instead, so I don’t think it is conflicting with the virtual contact sensor piston I have triggered by the same Front Door Contact Sensor.
Afternoon all,
This may have been answered in this thread somewhere, but it so large it is hard to navigate.
I have installed this and I have some really odd behavior happening.
I can arm the system from the keypad fine but when I touch it to try to disarm it instantly goes off. Also it will just randomly set the alarm off.
“2017-01-22 12:56:13.337 AM CST - 4 days ago APP Garage keypad intrusion detected.”
Has anyone had this trouble? I have the Smart Home Monitoring app installed as I use Scout to actually monitor my home so not sure if that has something to do with this.
Cheers,
-Stephen
It sounds like you probably have “All motion sensors” or “All intrusion sensors” selected in SHM for monitoring.
Since the keypad reports motion events when you wake it up, and intrusion events if you press the panic button, it would immediately trigger SHM as soon as you wake up the keypad.
You can fix this by selecting individual sensors to monitor in SHM, instead of selecting all the sensors.
That looks right to me, I wonder if Comcast has changed anything in their firmware which would break the functionality or undocumented commands we’re using for this.
Hrmmm so I see what you are saying I do not see how you can select the individual sensors in SHM. When I open Security under SHM I only see a toggle to turn on/off use all but nothing else.
Am I missing something here?
Cheers,
-Stephen
If you uncheck the “Use every open/close and motion sensor” box, it should then pop up selects for open/closed sensors and Motion sensors.
–Zack
Hrmm yeah I see nothing like that.
This is the correct place yes?
-Stephen
Yep. That should be the right place. You may have to hit the next button (I’m not familiar with the iPhone interface here, I think there are some differences to the Android one)
–Zack
Yeah it never gets me to a point where I can choose what to alert with. Odd one for sure.
Seems I have hit a bug of sorts. ST support is looking into it now.
Cheers,
-Stephen
Hi all.
I’ve managed to get an audible Entry Delay to work without Smart Alarm, (using Smart Home Monitoring, ULM, and CoRE). Here’s how:
Set up the keypad using mitchpond’s DTH at the top of the forum. Likewise with ethayer’s ULM smartapp, using the methods outlined at the top (including Entry Delay set at 30).
Create a virtual door contact by “Adding a Thing” and link it to Smart Home Monitoring instead of the actual door sensor.
In CoRE (Install Instructions: http://thingsthataresmart.wiki/index.php?title=CoRE#CoRE_SmartApp_Installation), create 2 pistons:
#1: If [real contact sensor] changes to "Open";
Then Using [Virtual Door Contact Sensor] Wait 30 seconds,
Set to "Open, Wait 10 seconds, Set to "Closed"
Piston Restrictions: Only execute during these alarm states:
"Armed/Stay, Armed/Away"
#2: If [real contact sensor] changes to "Open";
Then Using [Keypad] (select from under "Tone Generators")
setEntryDelay(..)
Parameter #1 Type: "number"
Parameter #1 Value: "30"
Piston Restrictions: Only execute during these alarm states:
"Armed/Stay, Armed/Away"
Optional: Set up a third CoRE piston to make the Keypad Chime (“Beep”) if [Real Contact Sensor] changes to “Open” (only during “Unarmed” alarm state).
Hope this helps those who want both Entry Delay and Exit Delay with audible countdowns on the keypad, current alarm status glowing on the keypad, and continued use of SHM from the SmartThings app for security control from your phone, rather than just keypad(s).
Looks like you only included 1 screenshot, but in that screenshot, it looks like the branch name might have a semicolon in the middle, and is using a lowercase ‘keypad’ (SmartAl;arm-keypad, instead of SmartAlarm-Keypad)
–Zack
