Cancelling HSM Alert Causes Hue Lights to go on

Hi.

So I've been having an issue. I've talked to support and they aren't able to reproduce it. However I am, even after completely removing HSM and reinstalling one rule at a time, testing between each rule addition. They suggested I post here to see if anyone else has seen this.

So what happens is that when I cancel HSM alerts, it turns on my hues. This only happens when I cancel HSM via the "cancel all alerts" or by changing to a mode that disarms HSM. If I cancel the alert by going into the child app the issue does not happen.

I've checked and there is no HE (or other hub) app turning the hues on. If you look at the timestamp below the hue turning on happens within milliseconds of cancelling HSM alerts. And, as I said, I can reproduce this every time I try.

So I'm curious if anyone else has had this happen. If not, does anyone have workarounds where I can cancel an alert for a custom HSM rule without using the cancel all, preferably something that can be used via a dashboard in case I'm not home. Lastly, is anyone aware if is possible to separate disarming HSM away/night and canceling alerts for custom HSM rules? Changing to a mode that disarms HSM night/away apparently also cancels alerts for all HSM custom apps.

I had this issue, could you post a screenshot of your HSM rule showing what lights it is turning on for alerts? Are they in a group?

Here are screen shots of all my HSM rules that have anything to do with hue lights (Bedroom lamp, bedroom mirror lights, family room lamp bulb 1, family room lamp bulb 3, fireplace lights). No lights are grouped in HE. They are in a room in the Hue app.

But to be clear - the lights are not turning on when the alerts are tripped. It only happens when All Alerts are Cleared. Not any individual Alert.

You had this issue? How did you resolve it?

It's been a couple of months I resolved that, if I remember correctly, it was something with the Water rule mixing with HSM, my suggestion is, remove lights from water alerts and the motions rule, test HSM and see if it does the same. Good luck.

Just to close the loop here. This behavior has stopped. I changed nothing on my end since rebuilding HSM (but still got the behavior)

But after being able to reproduce it on command 20+ times I can no longer reproduce it.