ZD is Zone Door, ZM is Zone Motion, ZW is Zone Window. Since it Smartthings auto sorts based on alphabet, I wanted to have all my motion and contacts at the bottom since they’re really just there for alerts and not useful devices.
Type: DSC Zone Contact
Network ID : dsczone13
I used these device handlers: https://github.com/LXXero/DSCAlarm/tree/master/devicetypes/dsc
Based upon the info in the name field of the contact DTH enter
DSC Zone
into the “Contact Name” field and it should accept the device. This should be the same data found in the Type field in the IDE, My Devices.
Thanks Arn - appreciate the support. I pulled the latest Delay Child from the beta repository (checked code to make sure changes were getting captured) and I still don’t get intrusion detection from my motion sensors at all. I’ll keep fiddling around with it, I’ll let you know if I figure anything out.
Kindly do the following to insure there are no unknown errors being encountered.
@glog Go into the IDE and click/tap on live logging
Clear any active alarm states in phone app dashboard, set the Alarm State to Away with the phone app dash board. Wait for any exit delay time to expire, wait for motion sensor to become inactive, activate the shm delay defined motion sensor. Then review your logs for any “error” messages. Also review the phone app on the motion sensor “recently” to insure it is actually being triggered. Forward any SHM and SHM delay messages
One issue with some motion sensors is they only change states every 5 minutes or so. My Ecolink motion sensor works this way, it’s not great for my testing, but works fine in real life. It also has a jumper to make it change states more often, but they claim it substantially reduces battery life due to the higher number of transmissions.
Hi - I just setup SHM delay Version 2.0 today. I have installed a small piezo speaker onto channel 1 of my Konnected board, and set it up as a Beep/Blink switch. It makes a sound when I manually test it in the My Home tab of the Smartthings app.
Within a profile for SHM Delay, I want to use is as a “beep these devices on entry delay”, but for some reason it’s not included in the list of items that I can select.
It is listed in “Beep these devices when real contact sensor opens and alarm state is off”
?Any ideas
Yes i know why this is occurring.
Go to the IDE SmartApps and click on module SHM Delay Child. Scroll down to line # 412
Temp quick fix for now
Change
input “thesiren”, “capability.alarm”
to
input “thesiren”, “capability.beep”
Then click “Save” on top menu. You should see the device.
Edit: This was originally written for beeping sirens. The issue is some Sirens don’t have a Beep command and would be excluded from a selection with capability beep. However, I have code in the module that attempts to create a beep to sirens that don’t have the Beep option. ST does not allow multiple capabilities to be specified in the Input type field, so I may have to add an additional input field as the permanent way of correcting this issue, but that brings up the fact that most devices would show in both input beep and alarm. Perhaps I will create my own device selection logic.
Thanks
input “thesiren”, “capability.beep”
didn’t work, but I changed it to …
input “thesiren”, “capability.tone”
which did.
My next question is how can I make it repeat the cycle and beep until the alarm is disarmed or the sirens are activated ? Currently it just beeps x3 times then stops.
I tried editing the beeper settings itself which lengthened the cycle, but by doing that is just continues to beep until the set time is up, even after the alarm is disarmed!
WebCore is my suggestion for personalized device actions.
Thanks - haven’t used that , but will look into it.
Just to update - used WebCore for the first time and wrote a very basic script to control the beeper. It works perfectly. The beeper activates as soon as the door is opened, and beeps in a loop with a 2 second delay until the system is disarmed or the alarm sirens sounds. What a great program, thanks for the heads up !!
Happy to post the script if anyone else might find that useful
0ad955bb-3fe3-47e1-b8b9-27dfed4d9e21 9:16:50 PM: info ||| NST Manager | API Device Data HAS Changed (POLL(ASYNC))
0ad955bb-3fe3-47e1-b8b9-27dfed4d9e21 9:16:50 PM: info ||| NST Manager | Updating Structure Data (Last Updated: 360 seconds ago) | Updating Device Data (Last Updated: 179 seconds ago) (async)
b483bac3-2c91-4280-9058-1c610b7318f9 9:16:35 PM: error java.lang.IllegalArgumentException: Property ‘c’ is not supported for devices @line 736 (motionActiveHandler)
b483bac3-2c91-4280-9058-1c610b7318f9 9:16:35 PM: debug value: open now: 1522372595715 startTime: 1522361589274 seconds 11006
f801b417-2a1c-4d0b-85f8-5b3586009080 9:16:35 PM: debug — Motion Detected
f801b417-2a1c-4d0b-85f8-5b3586009080 9:16:35 PM: debug Parsing 'catchall: 0104 0501 01 01 0140 00 2A0D 01 00 0000 07 00 ’
f801b417-2a1c-4d0b-85f8-5b3586009080 9:16:35 PM: debug — Motion Detected
f801b417-2a1c-4d0b-85f8-5b3586009080 9:16:35 PM: debug Parsing 'catchall: 0104 0501 01 01 0140 00 2A0D 01 00 0000 07 00 ’
9:16:34 PM: info Waiting on events…
Good news - changed line 736 back to what you had before and now it works for whatever reason:
def aMap = [data: [lastupdt: lastupdt, shmtruedelay: false, motion: triggerDevice.displayName]]
Will keep you posted as I continue testing. - I’m not aware that you changed anything else, but the same code now works.
@glog good work! You found the code regression that occurred in what was supposed to be a text only change to the setup screens that quickly followed the correction to the motion sensor error.
I retested the motion sensor logic issue and it is now operating as expected. Please update module SHM Delay Child from the Github Arnbme SHMDelay beta repository.
Why this causes a code crash. triggerDevice points to an event map that raised the alarm. triggerDevice.displayName has the name of the device and it is used for the SHM Delay intrusion message. triggerDevice.c does not exist causing a Groovy abnormal execution error. I suspect the c was introduced when I did a Ctrl/C to copy the displayName data for something, but instead of copying it changed the highlighted data to c.
… Page 1 Table of Contents
15. Initial Testing
16. Fix Motion Sensor Intrusion During Entry Delay
17. Fix Motion Sensor Intrusion During Exit Delay
18. Using Sounds and Text to Speach
19. Fix Siren Alarm During Entry delay
20. Using True Entry Delay
21. TrueNight Option, Keypads, and Exit/ Entry Delays
22. Way Beyond the Basics, User created SHM Modes
23. Using Simulated Keypad
24. Known Issues
25. Update History
26. Background
27. Source Code
28. Switching between “beta” and “Version2”
29. Help and Support
30. Addon Module - SHM Delay TrueExit
31. Addon Module - SHM Delay BuzzerSwitch
32. Converting from Version 1
There is a bug in SHM. When an intrusion alert is not cleared in the phone app, the next intrusion will send a notification, but will not execute any Security automations such as sirens or lighting. This is generally only an issue during system testing.
Work Around: clear intrusion alerts as they occur.
Test the simulated sensor
No Alarm: Verify SHM Security is monitoring the simulated contact sensor.
Test Exit Delay
Alarm issued at Step 5:
No Alarm: Verify the contact’s SHM_Delay sensor profile info; save it, then save again on main page, retry
Test Entry Delay
Alarm issued at Step 5:
No Alarm in Step 6: Verify the contact SHM_Delay sensor profile info; save it then, save again on main page, retry
Test Completed
In the contact sensor Delay Profile, select the triggering motion sensor, update the profile, then remove the motion sensor from the SHM Security: Armed Away Motion sensors. The motion sensor is 'followed", meaning it is ignored when the contact sensor is ‘open’ during entry delay and during exit delay, otherwise it is monitored during alarm state “away”.
Multiple motion sensors may be set in a profile, by setting Global option “Allow Multiple Motion Sensors” to On/True.
When a motion sensor is defined in multiple delay profiles, set Global option “Check other Delay Profiles” to On/True.
If paragraph 1 thru 3 above does not correct the issue, set global option True Entry Delay to On/True.
In the contact sensor Delay Profile, select the triggering motion sensor, update the profile, then remove the motion sensor from the SHM Security: Armed Away Motion sensors. The motion sensor is 'followed", meaning it is ignored when the associated contact sensor is ‘open’ during entry delay and ignored during exit delay, otherwise it is monitored during alarm state “away”.
Multiple motion sensors may be defined in a profile by setting Global option “Allow Multiple Motion Sensors” to On/True.
When a motion sensor is defined in multiple delay profiles, set Global option “Check other Delay Profiles” to On/True.
If paragraph 1 thru 3 above does not correct the issue, install **SHM Delay TrueExit then follow setup instructions
Set AlarmState by using SHM Delay TrueExit monitored SHM Routine
In this the SHM_Delay Profile: Set ExitDelay to 0
To use an Android phone or tablet as a Speech or Alarm Device install Lannouncer. Should you be running on a device with the Fully Kiosk Browser is always in the foreground: for example running ActionTiles, I strongly recommend using the Fully Kiosk Contoller DTH for TTS. It requires no additional apps be installed on your device.
Most sounds and TTS announcements can be performed with Big Talker, RemindR, or your favorite app, with two major exceptions: Exit Delay and Entry Delay.
For an announcements during Exit and Entry Delays:
If you installed smartapp Keypad_ExitDelay_Talker, remove from phone app and IDE
if you installed smartapp SHM_Delay_TrueExit disable spoken messages
For custom sounds and options during exit and entry delay, use the WebCore smartapp.
In WebCore trigger the TTS, tone or action based upon a custom location attribute created by SHM Delay. In Groovy: subscribe(location, “shmdelaytalk”, routinetoexecute)
After being triggered, the event’s value data must be tested for the following
Your siren does not support the beep() command and is not working with the beep simulation commands. Remove the siren from the Delay Profile. It does not impact its use with SHM.
Back to top
This is a last resort when an intrusion alert continues after setting an optional followed motion sensor in a Delay Profile. How it functions:
Note: this may cause confusion when viewing the system alarm state with phone app Dashboard, and unexpected SmartApp or Piston reactions.
Back to top
Settings shown below are the defaults that can be individually controlled by turning on Modefix in globals, then setting delays for the various alarm state / mode combinations in the Modefix profile
TrueNight (Default: Off / False) applies only to Iris 3405-L keypads and determines if the Partial Key creates an Instant or Delayed intrusion alert when a monitored contact sensor is triggered
Arm / Disarm: enter four(4) digit pin, followed by Off, On, or Partial
| True | Exit | Entry | Armed | |
|---|---|---|---|---|
| Key | Night | Delay | Delay | State |
| On | N/A | Delay | Delay | Away |
| Partial | Off | Delay | Delay | Night |
| Partial | On | None | Instant | Night |
When using a Centralite / Xfinity keypad in SmartThings Armed State: Night, the smartapp follows the ST Alarm state and lit Icon key
Arm: Press Stay, Away or Night icon; enter four(4) digit pin
Disarm: enter four(4) digit pin
| Exit | Entry | Armed | |
|---|---|---|---|
| Key | Delay | Delay | State |
| Away | Delay | Delay | Away |
| Stay | Delay | Delay | Night |
| Night | None | Instant | Night |
Motion Sensor operation in Armed State:
Away: SHM Delay monitors all motion sensors defined in Delay Profiles, plus SHM monitors all motion sensors defined in “home is unoccupied”-> Motions sensors
Night: SHM monitors all sensors defined in “home is occupied”-> Motions sensors
User Defined Modes. Example: Create “Stay” mode for use with Centralite / Xfinity keypad
The result:
The Simulated Keypad creates an Iris or Xfinity/Centralite image in a browser or Android app that functions as a keypad with Smarthings using the SHM Delay smartapp. Should you want to try it in test mode without installing any code, the link is at https://www.arnb.org/keypad/www
Should you prefer running the keypad from an Android app, it may be downloaded at https://www.arnb.org/keypad/keypad.apk You must allow Andoid to install apps from “Unknown Sources”. The app was generated using Phonegap. An IOS app is likely not going to be released due to the need to spend at minimum $100 to simply create the app.
What could this be used for?
Giving access to your Smarthings system to a spouse, friend, child, dog walker, neighbor, sitter, etc without having to install the Smarthings App or any other software on their phone, Each user has a unique pin, that may include date and time restrictions.
Try out and setup your system with a “Simulated Keypad” before making the decision to purchase and install a real keypad.
How to Install assuming you are already using SHM Delay.
Install all SHM Delay modules from the Github ARNBME SHMdelay Version2 branch. You may do this with the IDE or manually by going to https://github.com/arnbme/SHMDelay/tree/Version2/smartapps/arnbme then copy the modules and install 'from code". Install the new module SHM Delay Simkypd Child, Save do not publish, then authorize this module for Oauth in the IDE.
In the IDE, 'My Device Handlers", add device “Internet Keypad” Install using “Update From Repo” from the Github ARNBME SHMdelay Version2 branch. You may do this with the IDE or manually by going to https://github.com/arnbme/SHMDelay/tree/Version2/devicetypes/arnbme/internet-keypad.src then copy the Raw module, then paste using “Create a New Device Handler” and installing “from code”.
Create one or more virtual keypad devices. In the IDE go to “My Devices”, click “New Device” set the parameterrs, and set the type to “Internet Keypad”
On your phoneapp, go to Automation->Smartapps, then tap SHM Delay. Scroll down and tap “Global Settings” Set “Activate Total Keypad Control” to ON/True. Save the profile
On your phoneapp, go to Automation->Smartapps, then tap SHM Delay. Scroll down and tap “Create A New Sim Keypad Profile” Set a simulated keypad device, then save the profile. Go back and tap on the newly created profile, it displays an 8 character ID, copy it, then go to https://www.arnb.org/keypad/www enter and save the ID. The simulated keypad is now live including the panic key on the Iris image.
There are two cookies used to store information that have a 1 year expiration. When using the browser keypad page, set your browser to allow and not erase cookies from https://www.arnb.org
Notes:
When switching into page 2 of the documentation from page 1, browser does not go directly to desired html anchor point.
Occasional strange system operation when creating a user profile. Ignores all input data or forces reentry of a field.
Jul 23, 2018
Jul 02, 2018:
Jun 15, 2018 current Beta logic installed into Version2, including:
Jun 05, 2018 Documented Simulated Keypad (Beta)
Apr 30, 2018 Updated modules SHM Delay(2.0.4), SHM Delay Child(2.0.1), SHM Delay Modefix(0.1.2), SHM Delay Users(0.0.1)
Apr 04, 2018 Beta Version 2.0.1 Released, Updated module SHM Delay
Mar 14, 2018
I developed this app after I was presented with a steep learning opportunity created by installing Smartthings, an Xfinity keypad and GoControl siren. I purchased the keypad because ST phone presence proved unreliable as a SHM control method.
After installing the Xfinity 3400-X keypad and GoControl siren I made the decision to continue using SHM instead of SmartAlarm (no longer supported) because in theory, SHM is supposed to run on the local hub. I thought that would give me more reliability during an internet outage. That is likley not true but anyhow I’m using SHM. SHM lacks an: EntryDelay time, ExitDelay time, keypad support, and Zones.
This app does not support Zones, but does have a unique profile for each monitored sensor, allowing for unique entry and delay times, which keypards sound tones, and which sirens to beep.
Before writing this app I developed the logic using multiple Core and WebCore pistons for EntryDelay, and Open Door Monitoring. I’m a (PHP, Javascript, IBM Assembler, Cobol, Database) programmer, and wanted finer control over the processing. I taught myself Groovy and created some apps for personal use, then added editing, and released it to the ST Community. I found Java/Groovy similar to PHP and Javascript, but bumped into many frustrating differences. That said I hope someone, especially Noobs, find this app useful.
If you are running “beta” or “Version2” and you want to swap versions.
Go the the IDE–>Login–>My Smartapps–>Settings–>change Github respository
Owner: arnbme (in upper case that is ARNBME)
Name: SHMDelay
Branch: (beta / Version2) --> when “beta”, enter “Version2”; when “Version2” enter “beta”
Click ‘Save’
In “My SmartApps”
In ‘My SmartApps’ click 'Update from Repo". Follows steps 5 and 6 when modules are out of sync.
Select the SHMDelay repository you just changed, then install and publish SHM_Delay (must be first)
Install do not publish SHM_Delay Child, SHM_Delay ModeFix, SHM Delay User, SHM Delay Talker Child, SHM Delay Simkypd Child
(If not previously done) In the ST Phone APP install the SHM_Delay app
Manually install Version2 by going to https://github.com/arnbme/SHMDelay/tree/Version2/smartapps/arnbme then copy the modules and install 'from code"
Manually install beta by going to https://github.com/arnbme/SHMDelay/tree/beta/smartapps/arnbme then copy the modules and install 'from code"
Prior to posting a help request on this thread or as a private message, please verify the following:
You are using the Classic phone app, the Connect app is not supported
You are running the lastest version of any installed SHM Delay Version 2 modules.
You have read and followed all instructions in the documentation.
When using a keypad, the suggested DTH is installed, published and is being used, and global setting “Activate Total Keypad Control” is on/true .
All prior intrusion alerts have been cleared from the phone app.
Use this module along with SHM settings when the simulated non-keypad exit delay is not sufficient for your needs.
This stand alone module creates a real SmartHome(SHM) Exit Delay by monitoring for the execution of a “do nothing” SHM Routine, then in a user specified number of seconds executing a second SHM routine that actually sets the Alarm. Normally this should be used when setting Away with SHM Routine “Goodbye”. The initial routine may be executed by tapping on the routine name in SmartThings, or executed by a smartapp or WebCore piston.
There is one module associated with the app:
There is one module associated with the app:
Please post all installation and usage results, both positive and negative, along with any questions, issues, or comments on this thread. Thank You
Back to top
As part of transitioning Version 2 to live status the application documention in this thread now includes a “Table of Contents”. Due to size limitations with the community forum, the documentation is currently split into two postings that work with each other. In the future the documentation may move to another site.
All documentation was removed from the SmartApp, and an external link was added pointing to the community forum docmentation.
Please update module SHM Delay to Version 2.0.1
Changes:
I have not seen a way. Is there a way to set a longer delay for a specific contact. I have the delay set up on the back door but we have a garage that is away from the house. I think it will take longer then 90 seconds from when I set the alarm go out the back door, into the garage, open the garage door and back out of the garage then close the garage.
Paul
In the IDE Smartapps
Using a keypad change SHM Delay line 171 from
0..90 to 0..120
or however many seconds you need
In SHM Delay Child same on lined
392 396 402
Thank you will give that a try.
Thank you to everyone who participated and assisted with the SHM Delay beta testing.
If SHM Delay is installed from Github arnbme SHMDelay beta, you should change to the newly created Version2 branch which will always have the latest stable release of SHM Delay.
Instructions for changing the Github branch are at this link.
As of April 8, 2018, Version2 was an exact copy of the beta branch.
I am not sure if I have something set up incorrectly. Everything seems to be working as I understand it to be working with the following exception. I currently had the routine “I’m Back” to switch on when one of the presence sensors arrives home. I thought this would then deactivate the alarm but it does not seem to be changing it to disarmed or changing the keypad to disarmed.
I am running version 2.0.1 and using Life360 as a presence sensor. I can see the person change to present.
Paul
I have no experience with Life360, but can suggest a few things to help track this down.
Should this not help, please get back to me with your normal method of arming and disarming the ST system.
Edit: If Modefix is not set on/true in the globals, set it on/true then set the Modefix profile settings