SmartThings Community

[Release] SHM Delay Version 2.0

Currently no date / time parameters. It’s possible but would have to be associated with each State/mode combination showing in Mode Fix.

There is an option in the Konnected buzzer’s device settings in ST to set alarm duration and time between beeps and maybe you can reduce that time to zero? I personally just use it as a momentary device and sound it repeatedly by turning it on via Webcore.

I successfully set up an entry delay in Webcore but I haven’t tested it much yet. I have it beep once per second for the same duration as the SHM Delay and it stops when the alarm is disarmed. If you need the Webcore for this, let me know, it works great so far. I don’t have a real need for an exit delay beep because 99% of the time I use presence sensors and the exit delay of 60 seconds is more than enough time for me to get out of the door anyway.

Attempting to have ST blink a bulb, or quickly turn a device on and off that does not have this function built into the hardware, is generally not suggested due to delays with the internet and cloud processing. It may work now, or most of the time, but the odds are high it will fail at some point in the future. So for example if it’s possible to set your buzzer to beep 15 times for one second with a 1 second delay then issue a single command to create this effect, great.

Yes, I experienced this problem. I was using webcore to turn the buzzer on/off with delays and that just did not work. I had cloud delays as you describe.

There is also an ongoing issue with commands with delay timers. For example in an SHM Delay delay profile there’s an option to beep a siren or alarm 2 seconds after the contact sensor opens. When I first set this up about 16 months ago, it worked fairly well, now the siren almost always chirps between 8 to 12 seconds late.

I know what you mean, I’ve had the same issue with lights especially, and I am seeing it with the buzzer. It doesn’t matter for me as long as it does manage to beep multiple times within the 20 second delay to remind me to disarm the alarm, although It would be nice to have a slicker solution. If it doesn’t respond once in 20 seconds, then I have bigger issues because the rest of the system is doing to be of little use.

The Konnected buzzer settings only allow it to have one “version” of the beep, I think, so you can set the duration to fire each time, but I think it would be the same for every call to the buzzer.

All is working great now. Completely my fault. I failed to read a few of the settings in the Modefix function. It was spelled out very clearly but I was being dumb. I needed to enable the entry delay for that function. May be worth defaulting the function to “on” since this is the purpose of the app. Thanks for the support and great work with what you have done. Sending a donation over shortly.

1 Like

@arnb I picked up an Iris v3 keypad for cheap and can’t for the life of me get it to arm the system. Its currently setup exactly the same as my Iris v2 (which is working perfectly), but whenever I use “on” or “partial” the light changes, but it doesn’t change smartthings in anyway. I’m not sure if its an issue with SHM Delay or @RBoy DTH I’m using. Both are completely updated. Any insight?

I assume you’re using the on and partial key without a PIN. That would require in the V2 at least a pin user profile code of 0000. In shm delay the 0000 code is programmed not to function for OFF.

Should this not cure the problem kindly contact rboy apps support @maddie @rboy

Arn, the v3 Keypad does not allow the user to enter a pin when arming, only for disarming as I had indicated earlier. So the DTH doesn’t have anything to report (ie blank). Do you want the DTH to report 0000 for this scenario? This may be misleading since the user can press any 4 numbers before arming and the keypad will just ignore the numbers. Maybe a special case in SHM Delay to allow arming without a pin may be needed.

@arnb correct no code when using on or partial. Same with v2 of the iris.

Log Snippet:
a5481831-8b4e-47ff-a375-bc57e9d66b7c 9:35:04 PM: trace Alarm Keypad locked by user via keypad

a5481831-8b4e-47ff-a375-bc57e9d66b7c 9:35:04 PM: trace Processing Alarm Keypad lock event: [name:lock, value:locked, displayName:Alarm Keypad, descriptionText:Locked, data:{“method”:“keypad”,“armMode”:“armedAway”,“microDeviceTile”:{“type”:“standard”,“icon”:“st.locks.lock.locked”,“backgroundColor”:"#00a0dc"}}, lockId:9c0b38ee-6ef3-47d4-a211-6620d6a1d559]

a5481831-8b4e-47ff-a375-bc57e9d66b7c 9:35:04 PM: trace Lock event name lock, value locked, device Alarm Keypad, description Locked, data {“method”:“keypad”,“armMode”:“armedAway”,“microDeviceTile”:{“type”:“standard”,“icon”:“st.locks.lock.locked”,“backgroundColor”:"#00a0dc"}}

5cf5861b-be79-4363-8855-615d43b93058 9:35:04 PM: debug Event Type: Enhanced ZigBee Keypad Lock

9c0b38ee-6ef3-47d4-a211-6620d6a1d559 9:35:04 PM: trace [[name:codeEntered, value:, data:3, isStateChange:true, displayed:false, linkText:Alarm Keypad, descriptionText:Alarm Keypad code entered is ], [name:lock, value:locked, isStateChange:true, displayed:true, descriptionText:Locked, data:[method:keypad, armMode:armedAway], linkText:Alarm Keypad]]

9c0b38ee-6ef3-47d4-a211-6620d6a1d559 9:35:04 PM: trace Sending Status 0300 to device

9c0b38ee-6ef3-47d4-a211-6620d6a1d559 9:35:04 PM: debug Sending status to device, Arm mode: armedAway

9c0b38ee-6ef3-47d4-a211-6620d6a1d559 9:35:04 PM: trace Method setModeHelper mode: armedAway, delay: 0

9c0b38ee-6ef3-47d4-a211-6620d6a1d559 9:35:04 PM: debug Sending acknowledgeArmRequest(0)

9c0b38ee-6ef3-47d4-a211-6620d6a1d559 9:35:04 PM: info Keypad locked

9c0b38ee-6ef3-47d4-a211-6620d6a1d559 9:35:04 PM: debug Received command with keycode/armMode: ‘’/3

Ok this answers my (now deleted) question to @RBoy about what is sent for ON (away) 3 with a null value
making partial 1 with a null value.

In the Ide devices, what is the data manufacturer and model for the V3 keypad?_

@rboy @riccanet

Completed reviewing the SHM Delay logic and code, and in my opinion the best way to handle the Iris V3 is as follows:

  1. In the RBoy DTH. When there is no pin available on Partial(Stay) or On(Away) modes, set the pin to 0000 prior to creating the codeEntered event

  2. In SHM Delay. The User creates a user pin profile of 0000 with no restrictiions. The SHM Delay logic already rejects 0000 for Off. Set the User name to “Iris V3 Instant On” or whatever you want. Other pin profiles used for ‘Off’ must also be created. Note the 0000 pin is already needed to use the V2 Instant on feature.

Need the V3 model number to insure there are no other conflicts and possible code changes needed in SHM Delay

@RBoy Should adding the 0000 create an issue for your logic, let me know.

Not at all, this section is all part of the “non lock” code and shouldn’t impact the lock management flows in any way.

Can be done

Sounds good

We’ll make this update and release today to the DTH


@arnb we’re working on a bunch of new keypads with some manufacturers and so expect to see that some of these models may behave in a similar fashion (no pin for arming and pin for disarming)

1 Like

Sounds good. As long as I know the model number and the DTH commands match the 3400 or 3405-L it should work. Making some minor changes for the model and will put that into the beta versions now.

With the forthcoming changes model will be needed only if it works like a 3400, four modes: off, stay, night, away versus Iris, three modes off, (partial)stay, (On)away

[Beta Release] Support for Iris V3

Minor change adding support for Iris V3 keypad. Requires latest (to be released) version of RBoy Apps DTH with Iris V3 support

User Profile Requirements
Requires a user pin profile of 0000 with no restrictiions used for ON and Partial. The SHM Delay logic rejects 0000 for Off. Set the User name to “Iris V3 Instant On” or whatever you want. Other pin profiles used for ‘Off’ must be created.

Installation module changes
Update module SHM Delay (V2.2.4) from github arnbme / SHMDelay / beta Save, then publish for me
Update module SHM Delay Child (v2.1.2) from github arnbme / SHMDelay / beta Save do not publish

Please report any issues

@RBoy @riccanet

1 Like

The DTH has been updated to version 01.05.04 to support SHMD requirements @riccanet .

Arn sent you a PM on the github pull request for the panic button

Panic button logic was adjusted for RBoy Dth in the V2.2.4 SHM Delay module available in the arnbme/ SHMDelay/ beta repo @riccanet

1 Like

Loaded the beta SmartApp and the new DTH. So far partial worked great. I’ll let you know tomorrow if I have any issues with disarm or ON/away.

1 Like