[OBSOLETE] SHM Delay Version 2.0

I couldn’t figure it out from within webCoRE, so I guess I’ll be hitting the wiki and/or the webCoRE community forum.

This is a bug in the logic when there are multiple delay profiles. I consider this high priority and It will be corrected ASAP. Thank you for finding and reporting this issue.

Updated: Unable to reproduce. see next post. Reviewing code at 2AM is not generally advised.

2 Likes

I am unable to reproduce this issue.
Please review your delay profiles and be sure they all have active push/sms message settings.
Should you continue to have this issue after reviewing and adjusting any settings, please send a PM or post on this thread.

Here’s what I did.

  1. removed Back Door contact sensor from all SHM monitoring
  2. Created “Back Door” Delay profile, with push messages to (deprecated but forced active) Contact - me with a 1 minute warning time.
  3. Armed system in Stay / Night, and Away modes with both doors open
  4. After 1 minute received a notification on my phone about both doors open, disarmed system
  5. Armed system from Keypad associated with “Front Door” with back door open
  6. After 1 minute received a notification on my phone about "Back Door open"
    (Ignore that night mode on screen it is a blue light filter I keep on 24/7)

I’ll try again tonight. I was using the phone to arm SHM, and now I wonder if the Back Door delay profile had simulated exit delay on.

Pin message routing is now available in the beta release. Pins may be logged to phone notification log, Contact Book, push messages, or via SMS with telephone numbers

1 Like

Is it possible for SHM Delay app to allow instant notification when a monitored contact sensor is open at the time that SHM is armed? Currently, one minute is the shortest delay allowed in this field. Instant notification would afford me the opportunity to go back and check the physical door/window while I’m still in the house or driveway, rather than having to turn the car around.

I didn’t realize that this setting delayed the initial notification. I assumed that the initial notification was instantaneous, and that the setting controlled the delay until the subsequent notification.

Perhaps, but I have to look at the logic. The following idea may solve this issue and be easier for me to implement.

Many systems force all doors and windows to be closed before arming. I understand why, but my front door is usually open when I am arming my system. Not wishing to enforce my thinking upon the community, this is probably something that could be a global option: “All contacts (doors) defined in Delay Profiles must be closed prior to Arming the system” with a default of True. When this option is On/True and all doors are not closed, the system would not Arm, a message would be sent to the Global valid pin destination log settings, and an optional TTS/Sonos Talker message issued.

Your thoughts?
.

Personally, I still want the system to arm when a door or window is open; I’d just like to be notified ASAP about it. But if someone else finds the idea useful, I’m okay with having it as an option.

Done!
The open door reports are now done immediately upon arming. This does not include the time in Exit Delay prior to setting Away/On mode when setting alarm from a keypad.

Change to module SHM Delay Child v2.0.7 in Version2 and beta repos.
Installation
SHM Delay Child: Save but don’t install module

Regarding Window contact sensors: I assume most if not all windows would be monitored by Smart Home Monitor and not handled by SHM Delay

Wow, you’re awesome…and fast!

You’re right about the windows all being monitored by SHM, not SHM Delay. Unless you’re the Dukes of Hazzard; those guys welded the doors and went through windows.

Thank you for your positive comments… After reviewing the code it was a one line change :grin: and some quick and simple testing. It’s not often it is that easy and fast, but it’s nice when it happens.

Should you try the updated version, please let me know your results.

Never watched that show, but it sure is an interesting approach to home security.

Well it was actually more complex than I first imagined, requiring additional coding changes. SHMDelay is now at V2.0.8 (July 19, 2017 22:35 EDT)

If you installed 2.0.7 please update ASAP!

1 Like

A note to the SHM Delay User community.

I need your help and feedback with testing and verifiying the latest SHM Delay beta release.

If you wanted or asked for control over good and bad pin related messages, executing routines and pistions based upon the mode entered on the keypad, or a wanted a single pin that will arm the system, execute a routine, then execute a piston, please give this a try and post your results so can get this verified and moved into live status.

Thank You
Arn

1 Like

I had requested notification when my son uses the keypad to arm & unarm SHM. It works flawlessly for me in the beta.

1 Like

[Beta Release] SHM Delay Version 2.0, July 21, 2018 20:40EDT

Enhancements and Changes

  • (Added Jul 21) Support for quick arming on Iris keypad without entering a pin.
    Iris harware sends a 0000 code when single or double tapping the On or Partail key without entering a pin. The device firmware determines if it is single of double tapped.
    To implement: add User Profile with pin 0000, Type: User. The Iris does not send the 0000 when the Off key is pressed. For security reasons, suggest setting the User Profile flag to ignore an real 0000 pin entry with the Off button

  • Valid Pin message routing is now controllable on a global basis, and each User Profile may optionally override the global pin message settings. Pin Messages may log to phone Notification Log, Contact Book, push messages and SMS with phone numbers. Scroll to end of globals to set basic pin message settings, then optionally override the global pin settings in the User Profile.

  • Bad Pin messages, pins not in a User Profile, are now controllable on a global basis. This is separate from the valid pin setting.

  • New User (pin) Profile type: UserRoutinePiston. Sets armed mode; optionally runs Routines, optionaly runs Webcore Pistons

  • User (pin) Profile types “Routine”, “Piston”, and “UserUserRoutinePiston” include settings for keypad mode used in addition to All Modes. For example: Off: executes Routine-> Lights Off; On/Away: executes Routine-> Lights On

Pre Installation

  • Remove all existing “Routine” type User (pin) Profiles

How to Install
There are two (2) modules associated with this update. When updating from Github, in the IDE change for each module shown below, change the source repo to the beta repo shown below

  1. SHM Delay (v2.1.6). Module should be Saved, Published, then Installed with the Smarthings app (must be done first)
  2. SHM Delay User (v1.1.1) Should be Saved, do not publish or install.
  • Install via the repository (preferred), from the following repo.
    Owner: arnbme (in upper case that is ARNBME)
    Name: SHMDelay
    Branch: beta

  • Recreate any removed “Routine” User Profiles.

  • Set global pin message settings and optional User Profile overrides.

  • Set global Bad pin message settings.

1 Like

This is now fully supported in the updated beta version. You need to set up user pin code 0000. Quick arming is an Iris keypad hardware function that sends 0000 and the arm code when the Partial or On button is pressed without a pin.

I owe you a beer. :beer:

1 Like

[Update] SHM Delay Version 2.0, July 23, 2018 10:10EDT

Enhancements and Changes

  • Support for quick arming on Iris keypad without entering a pin.
    Iris harware sends a 0000 code when single or double tapping the On or Partail key without entering a pin. The device firmware determines if it is single of double tapped.
    To implement: add User Profile with pin 0000, Type: User. The Iris does not send the 0000 when the Off key is pressed. For security reasons, suggest setting the User Profile flag to ignore a real 0000 pin entry with the Off button

  • Valid Pin message routing is now controllable on a global basis, and each User Profile may optionally override the global pin message settings. Pin Messages may log to phone Notification Log, Contact Book, push messages, and SMS with phone numbers. Scroll to end of globals to set basic pin message settings, then optionally override the global pin message settings in the User Profile.

  • Bad Pin messages, pins not in a User Profile, are now controllable on a global basis. This is separate from the valid pin message setting.

  • New User (pin) Profile type: UserRoutinePiston. Sets armed mode; optionally runs Routines, optionaly runs Webcore Pistons

  • User (pin) Profile types “Routine”, “Piston”, and “UserUserRoutinePiston” include settings for keypad mode used in addition to All Modes. For example: Off: executes Routine-> Lights Off; On/Away: executes Routine-> Lights On

Pre Installation

  • Remove all existing “Routine” type User (pin) Profiles

How to Install
There are two (2) modules associated with this update.

  1. SHM Delay (v2.1.6). Module should be Saved, Published, then Installed with the Smarthings app (must be done first)
  2. SHM Delay User (v1.1.1) Should be Saved, do not publish or install.
  • Install via the repository (preferred), from the following repo.
    Owner: arnbme (in upper case that is ARNBME)
    Name: SHMDelay
    Branch: Version2

  • In the Classic phoneapp: save SHM Delay after installing to set default pin message routing variables

Post Installation

  • Recreate any removed “Routine” User Profiles.

  • When “One Touch” Iris keypad arming is wanted, setup User Profile for pin 0000

  • Set global pin message settings and optional User Profile overrides.

  • Set global Bad pin message settings.

ST Removal of Contact Book
On July 30, 2018, should you be using the Contact Book for push messages with the SHM Delay app: Contact Book will be disabled, and you must modify the all message routing settings to use push or SMS messaging.

I have a couple very basic questions about this:

My setup is an 18-zone Konnected panel driven by Kindle Fire tablets running ActionTiles via Full Kiosk Browser.

  1. Will this took work well with this sort of setup?

  2. Among the features are several items that mention things like chirping, beeps and sounds of various types (including voice if I read that right). Will these work with a Kindle Fire tablet or is this all limited to some specific hardware I don’t currently have? I would LOVE to be able to use the current system and have it act like the old Honeywell panel and keypads this upgrade replaced.

Thanks so much for all the hard work on this.