[Release] SHM Delay Version 2.0

Suggest using WebCore to change SHM mode or arm state at desired times.

Hello arnb,

I cant find a solution for my case here (excuse me if it mentioned but I cant find it).

At night when my SHM is in stay mode, and someone gets up i triggers accidentaly a specified 2-3 motion sensors I need delayed alarm and speaker message to remind the person to disarm the system?

I dont have contact sensors on my bedroom doors, and even if I had frequently they stay opened during the night, so I cant use simulated contact sensor and connected motion sensor in the usual case with delay profile.

Whats the configuration in that case?

One more question - is there a way to specify speaker profile in delay profile.

The idea is when specific delay profile is activated to activate only a specific speaker profile not all of them?

Thanks in advance

Normally, motion sensors trigger an immediate intrusion alert. SHM Delay profiles have an option to delay motion sensors for a few seconds when an entry delay is defined for the current mode, and a motion sensor reacts before a contact sensor opens.

The setting in SHM Delay Child is around line 436 input "themotiondelay". Adjust the upper number, save the program, then set the input setting in the app. Also adjust remove the motion sensors from SHM and define them in the SHM Delay profile. That should work as long as Stay mode has an entry delay despite the setting documentation saying Away mode only. However, it will not produce a warning message, and I have no plans to make messages speaker specific. You may always create your own messages for this condition using WebCore.

For the record: While I continue supporting this app, I no longer use SmartThings for any HA automations.

Hi

I am not able to find the"Activate Total Keypad Control" in global settings.

Am I doing somthing wrong.

everything is installed.

/Jan

Neither can I!

I did found that info in the old documentation for converting from Version 1 to Version 2. That’s been replaced by the globla setting “A real or simulated Keypad is used to arm and disarm Smart Home Monitor, SHM”

Warning to users: Smart Home Monitor removed from new installations of the Classic app.

According to the thread quoted below, Smart Home Monitor and the Life360 presence sensor were removed from the Classic phone app. It was already common knowledge that routines were removed.

Note: I am able to access SHM from Classic’s dashboard page.

1 Like

Thanks for the reply. i did not see the warning it was being removed. every 12-18 months i restart my pc,tablet and phones just to get rid of all the rubbish. i thought this time i would give smartthings a seperate e-mail, so that explains everything. i used the new app for a couple of days and the intergration for phillips hue is fab. but not everything is supported yet such as my z-wave sirens so i went back to the classic app, again thanks for your reply.

1 Like

As far as I know there was no warning.

There isn’t a warning @samboy. The only reason we know is when someone, like yourself, deletes something like routines or SHM and it disappears and then they post on the forums or someone from ST posts on the forums.

You MIGHT be able to get SHM and ROUTINES back if you contact support. Being that you didn’t get the banner in the classic app asking you to migrate, they should know that the new app does not have feature parity with classic for you. It’s worth a shot if you wish to stay on the classic platform.

1 Like

Looking for some help on 8. Settings: SmartThings Home Monitor-STHM New App -> Post Installation Setup with new STP app and STHM. The second to last instruction on this section is Enable SHM Delay Modefix -> Set global setting “Mode Fix when system armed from non keypad source” to ON/TRUE. I’m not seeing this setting on the new app under Global Settings. Can someone post a screenshot or something that would help identify where this is? Thanks!

The documentation has not kept up with the smart app. This is the current modefix global setting

Thanks! I’ll give that a shot. I had it working with SHM previously, after uninstall it, Samsung made it so I can’t install it and I’m trying it with the new app.

Unfortunately, I can’t get the delay profile to work. I did it in the classic app, but when I open the contact with the delay profile, it doesn’t trigger the simulated sensor to set off the alarm. I tested just the simulated sensor by itself and it does trigger the alarm.

Did you do anything at all in the new app with SHM Delay? What your describing is exactly what happened when I tried setting up in the new app. If not, maybe ST screwed something up in classic now too.

I didn’t do anything with SHM Delay in the new app. I just tried uninstalling SHM Delay and tried it over again with no luck. Thanks for the help.

@arnb

How do we check to see if the INCOMPLETE issue for child apps is now affecting the classic app?

If @Sun_D has everything set up correctly, it looks like classic may be exhibiting this behavior too.

The above was prior to New ST app’s latest updates.

Just created a new User profile (child app) in the New App an it appears in the Classic app. This did not occur in my original tests.

I did not test it because my setup needs a total recreation after moving all devices to Hubitat except for a single keypad.

@oldcomputerwiz Please give it a try on your system. Create a user pin profile in the new app, then try using the pin on the keypad.

I’ll give it a try and PM you the results.

I just tested creating the user profile and yes, when I created the user profile in the classic app, it also shows up in the new app.

Regardless, the profile worked and SHM Delay correctly acknowledged the pin. For fun, I then created a user profile in the new app. It didn’t work. The pin was acknowledged as invalid.

I then looked at my profiles in the classic app and noticed that the profile I created in the new app, did NOT have the vertical blue bar before it’s name like my profiles that work correctly. I then opened the non-functioning profile in the classic app, saved it, and then the blue bar appeared before it’s name. The profile was then acknowledged as a valid pin.

It looks like creating profiles in the classic app still works, and creating profiles in the new app doesn’t.

No comment