HSM strange behavior

Hi @bravenel
I've noticed two strange behaviors in HSM:

  • If I set a siren alert, it always execute both() device function, instead it should be
    Siren flagged => siren()
    Strobe flagged => strobe()
    Both flagged => both()

  • If I arm Home and triggers an alert, after cancel alert it goes to armed Night instead of rever to armed Home:

Do you have lights for alerts? If yes, after canceling an alert, is HSM restoring the lights to the settings they had before the alert? Not working for me, I don't know why. Thanks

I did a test with this and I believe the execution is related to the device and the driver, I have a siren, no strobe included, so when I use any for the siren alert(siren, strobe or both) the execution is siren. Now, if I had a siren with strobe and I just want to use one, the siren or strobe, it should allow that, apparently not in your case, because it looks like your siren has strobe in the driver and you can't choose only one.

I've wrote myself the driver and has all functions: strobe, siren and both.

No lights so should not be related.

Thanks, I know is not related, just trying to confirm if I'm the only one seeing the issue.

That function works for me. How are you clearing the alert?

I opened a thread to not hijack this one, sorry Gabriele

Known issue, fixed in upcoming release.

1 Like

what exactly is being fixed? Lighting alerts restoring was fixed in a previous release.

I will investigate this. Could you look at the device events for the siren (Events link at top of device page), and see what events the device is receiving from HSM.

It was indiscriminate about restoring lights. For example, if water alert went off, it would restore lights that had not been on before the alert, but that had been previously captured by an intrusion alert. The fix is to totally separate and distinguish before-alert lights setting by alert type.

Ohh, so that means this is why I had water alerts turning on lights when I don't have lights selected for water, yes, I remember you said there will be a fix in next release. Thanks.

I've put three debug log in device driver functions siren(), both(), strobe() and it always trigger both().

Yep, I'm able to reproduce this bug. Will look to getting a fix in.

Is it the second issue related or are two different things?

Found and fixed the bug wrt siren. No, the second issue is not related. Looking into that one.

Update: I'm not able to reproduce the Armed Night issue. Nothing about Cancel of an alert touches the arm setting.

1 Like