I seem to have found a couple of bugs in HSM that I want to make sure were on your radar.
First, when an alert is canceled, that does not seem to be publishing to other apps as was intended. I built a RM rule to turn on a switch based on the trigger of HSM alerts canceling. After canceling the alerts, they cancel correctly, however the switch never turns on. So, is the resetting of HSM supposed to be published? If so, I don't believe it is.
Second and third bugs, lighting alerts. I don't believe that the set level with the lighting alerts is working correctly. When the alert occurs, switches turn on but dimmers do not automatically get set to the level set in HSM.
Now, here's the weirdest one I've found. At first I thought that resetting or disarming the alarm was not setting lights back to their pre-alert levels. However, after moving all of the control for the lights themselves into a RM rule and leaving only 1 virtual switch in HSM, it DOES work correctly. So, it appears that if you have a bunch of lights (combination of switches and dimmers) in HSM, it will not reset those devices after the alert is cleared or the system disarmed. However, if it is just a single switch, it works perfectly. Yeah, I thought I was going crazy at first when I found that it worked all of a sudden. But after putting several switches and dimmers into the HSM, it stopped working again. So, it definitely appears to be a bug in HSM.
Lastly, text & audio notifications. When configuring an audio notification which repeats every x seconds, it appears that the repeat setting also carries over to the text notification settings, even if the text notification is not set to repeat. I had a one time text notification set up but an audio notification that repeated every 5 seconds. Instead of getting one notification, I got one every 5 seconds, just like the audio notifications.
(FYI, the HSM Notifications device is a Join API device. I am getting the notification, just too many of them.)
Fixed the lights part. Lifted capture/restore code from Scene-1.2. Works great now. It essentially captures the previous lights state completely, then just restores it to whatever it was. Which is what it should have done in the first place.
Repetition bug fixed. Next release for all three of these.
Since this is an active thread, I'd like to make a request. Today it appears the system does not arm either home or away if some of the contacts are open. This is too strict. Simplisafe for example ignores open contacts until they are closed (IE closing once armed will then include them in the armed zones, but ignore while it stays open).
As is, is fine for now in the cold weather, but we come and go for short trips around the neighborhood all the time in the good weather and leave some contacts open for simple convenience. As it is now, I will be required to close everything every time.
I am also not getting the alert of this condition as a text. It shows in the HSM app, but I can not get the push nor the sonos to work.
Yeah, also, why is it checking for the contact to be closed at the beginning of the arm delay? So, all contacts have to be closed when you hit arm, then you can open/close until the arm delay is over? That is also way too strict. It should allow all sensor to be open or closed and change freely until the timeout is reached.
Yet to come in this regard is the concept of bypassing a contact sensor that is open -- in a future release. In the meantime, the functions afforded by Arm Failure alerts can be done by Rule Machine when it is desirable to have this functionality of arming with a contact sensor open, but still being notified if other sensors are wrong.
And that is exactly what I did.
However, if the Arm Delay even were published, then I would be able to know about the contacts being "wrong" before the system was completely armed. Another reason that the arm delay and intrusion delay would be great to be seen.
For anyone looking for them, at some point since this was originally posted, Delayed Intrusion is now available to RM to use as triggers. I now have my lights changing to alert status and an alert paying over my speakers during the delay and the siren only going off after the delay.
Hi Experts,
Need a little help with understanding of HSM- Cancel Alerts.
I have been using HSM since last few years but yesterday I noticed something which doesn't seem right to me.
In my Armed Home mode, there were some alerts generated by contact sensors. I went ahead and cancelled the alerts. After cancelling the alerts, the HSM stopped generating any future alerts by same or other contact sensors that were supposed to generate alerts.
Only after I disarmed and then changed the mode back to Armed Home, did the HSM started generating alerts.
Is this how HSM is supposed to work, or am I missing something?
Thanks