HSM Issues

[bravenel]

@jeremy.akers

When doing "Arm Home", there is still an entry delay even though the entry delay is explicitly labeled "Delay Armed-Away". Typically you don't want an entry delay when "Armed Home".

These are two different things. Delay Armed-Away is an exit delay. The other option is Intrusion Delay, an entry delay, which is for any intrusion, either Away or Home (there are valid use cases for both). Perhaps there should be separate delays that can be specified for Away and Home.

@jeremy.akers

And I realized I only get this message and only see this "one siren" issue if I select the siren that's internal to the Iris Keypad. If I de-select that siren, my other two siren's both sound off just fine (and turn off when the alarm is disarmed fine also.) Sure enough if you look at the Keypad it has a "siren" command but no "on" command.

@jeremy.akers

I think for point #2 it's important that if Hubitat / HSM should first try "siren" instead of "on" and only try "on" if siren fails.

HSM sends the "siren" command unless you select both strobe and siren, in which case it sends "on" command. That should be changed so that if both selected, it sends "siren" and "strobe" commands, not "on".

@jeremy.akers

If I have Iris keypad's internal siren selected and I allow the entry delay to expire and the alarm to go off, whichever siren it sets off is never disabled when the alarm is disarmed. Somehow the bug I found in point #2 above prevents HSM from shutting off any of the alarms that ended up sounding off before it failed with the above error message. I end up having to go to the "Devices" list and manually click the "Off" button for that siren.

Yes, that error blows the running instance out of the water, so it doesn't finish running.