Honestly, besides the energy meter that I don't use it a lot so I don't care right now, the HSM replacing SHM from ST will be my last step to get rid of the ST hub. This morning was a total dissaster, my wife opened the door(the porch light worked fine!!!!) and the alarm started to sound, turned on the lights, triggered the Alarm.com system, they wanted to call the police... Ok, I should test it first, I know, but after the hot fix last night, then I started to play with HSM, I was in bed doing keypad tests, then I went to sleep and I forgot to dissable the alarm, but it had 30 secs of delay and did not happen.
I know SHM doen't have some kinds of delays from factory, but using a custom app(SHM Delay) it does everything needed, like when you are in away mode then you open a door it will delay the alarm for the door and for the chosen motion sensors only when you open the door first, I will trigger 2 to 3 motion sensors in my way to the keypad after I open the door. I don't know just opening the door will not do the delay, it does the exit delay just fine when I activate away mode from the keypad.
I found this setting on HSM, but only has a delay for away and only doors, it should have more options, like delay for stay or to choose what device you want a delay, like just the front door and a motion if triggered after the door was open.
I believe I can do some of those delays with RM(I don't know how), but I need some advice from you guys, I need help, I want to unistall ST completelly, my first challege was eliminating all the webcore pistons and use RM instead.
I experienced the same issue setting up a new system for a family member yesterday. When I covered up or disabled the motion sensors the system honoured the intrusion delay when it was just the door contact that was tripped. As this is my first time playing with HSM (not using it on my own system), has this been a common occurrence or isolated to 1.1.2.121?
Another "problem", maybe it's me again, is when I use the delay for away I hear the keypad beeping when I open the door, I go to the keypad and put the code, it accepts the code, then a couple of seconds later the alarm will be triggered, the keypad is Green(dissabled)!, siren will sound, lights will turn on, I will receive the intrusion text, I have to go to the web HSM and dissable the intrusion, then the lights turn off then they turn on again. Crazy... and almost dead because my wife almost kill me this morning...
I don't know if this a new occurence since I been waiting for keypad integration an it started on version 1.1.3. I have all the motions dissabled right now and all the above is happening.
If you select "Delay arming Armed-Away..." it gives you an option of selecting one or more doors for which the delay applies (as opposed to all doors). There is a bug with respect to other alerts being triggered during the delay period -- to be fixed right away. A motion triggered after the selected door opens should not trigger an alert.
Could you explain why you want delays for stay? What is the scenario?
After multiple tests, it works normal now, I did not changed anything, it just works now, the only issue I see is there is no door delay for stay mode and away mode after you open a door the delay will start only for doors chosen but no delay for the motions so I will trigger 3 of them before reaching the keypad.
Any sugestion? RM? I don't know groovy
I holded my answer because I saw you replying, thanks always for the help, I know I'm a problem.
We always forget to disarm the alarms, I know we can use automation but my wife preffer to do it manually (and in some point me too), so every day we open one door, the stay mode will start beeping to dissable the alarm in 30 secs. (better than getting the full lights show and siren)
In my house it’s because we sometimes end up walking the dog late at night, after the house has gone into night mode and the intrusion alerts are armed.
The alternative is using some automations or buttons to disarm and rearm HSM when someone needs to open the door late at night, I suppose. But my wife likes to use the keypads, and that includes entry delays.
Good point, I go in the night too to feed my ducks and I have plans to arm the house automatically with some rules but probably if I open the back door the party lights will start
This is a bug. Now fixed and should be released today. If you have a delay set for a specific door, motion events during the delay period should not trip the alert. You should have a grace period while you go disarm.
But you're going to have to disarm the system before you go out, aren't you? How are you expecting this to work: she opens the door to walk the dog, and somehow has to remember the alarm has to be disarmed first? Suppose you put a 30 second delay on it. She opens the door, delay starts, goes out with the dog, closes the door. When the delay runs out the alarm is going to go off.
My wife will hear the beep of the keypads and inmediatelly will go to dissable it, or me, it's an alert for dumb people like me, nothing else, very usefull, ST has a custom app for that but I don't know how to port it.
Correct, the issue is we may forget to disarm with keypad before opening the door (it's late at night, this is the last thing one of us is doing before going to bed).
If there's a 10 second grace period, during which the keypad beeps, the system can still be disarmed before alerts are sent.
Edit: I haven't finished playing around with it yet, but it seems as though the keypad does sound an alert tone during the HSM entry delay. As @vjv mentioned, the SHM delay smartapp for ST also supports this feature of the iris keypads.
