Updated the ST version of the Fully Kiosk Browser Controller documentation, documenting use of SSML with TTS messages
Also, please take a look at this Hubitat thread regarding use of embedded SSML with TTS text files.
Updated the ST version of the Fully Kiosk Browser Controller documentation, documenting use of SSML with TTS messages
Also, please take a look at this Hubitat thread regarding use of embedded SSML with TTS text files.
Here is the response from ST in regards to the siren not being stopped when the system is disarmed. I did let them know that the behavior of SHM, and I believe STHM initially, was to stop the siren when the system is disarmed.
Hey there,
Thank you for your patience and efforts.
We looked into your query and I would like to inform you that the Smart Home Monitor will only stop the siren when the intrusion is Dismissed. Disarming cannot stop the siren because disarming the system does not dismiss the active intrusion. SHM will also continue sending intrusion notifications until the intrusion is dismissed, so itās good to dismiss the intrusion instead of just disarming the system.
I see you want to have the siren stop when disarming the STHM instead of dismissing the intrusion. Unfortunately, there is no feature currently available within the SmartThings app.
I have considered it a feature request and Iāll be making sure to reach out to our development team with that feature request. I donāt know the timeline for the feature update, but the bit of good news I can give you is that the majority of these features are on our radar and we on the support team are looking out for every request to make sure this feedback is heard.
I hope this feature will be added at the earliest.
Hey everyone,
I know this is probably in here somewhere but I couldnāt find it (this threat is so dang long!)
All I am trying to do is setup a time of day that there is a delay and a time of day that the alarm goes off instantly. (basically I know that in the late evenings nobody should be in my office, so I want it to go off right away) but I am confused on how to get that set, looking at the options on here.
Thank for any help, Im sure this isnāt hard and I am just missing it. The rest of it I got all setup great!
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ā
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.
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.
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.
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!
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.
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.