I seen this too, HSM is not restoring the previous state of the lights after click cancel, and when I click cancel to a water alert it turns on the lights I have selected for intrusion instead for water, but nobody pays attention to me...
I am paying attention. I found an issue with HSM with respect to how it was capturing lights before the light alert, and that is fixed in the next release. This would have caused issues with some color lights. I intend to continue to push on these issues.
Sorry to bump an old thread, I just had a leak sensor detect water and HSM did its job and turned off the water main valve and turned on a handful of lights. But upon clearing, a few of the lights were restored to off and the water valve remained closed (which I suspect is by design and preferred).
I checked the log around the time I cleared HSM and it shows no activity for those few lights that should have been restored to off.
HSM grabs the then current state of the lights just before the "lights" alert. That is what gets restored later. It is possible that those states had not been correctly updated, depending on what type of lights these are.
The lights that didn't restore is a Lutron Caseta switch, three Peanut Zigbee switches in the same room as the hub, and a cheapo generic zigbee dimmer the floor above the hub. The other Caseta and Zigbee devices were restored properly. The Caseta switch that failed to restore is a light that we essentially never use, so was likely last controlled by Hubitat - though probably some time ago.
I had this same issue tonight. Since this was a year and a half ago, I imagine this old issue has since been addressed but now resurfaced. I am running 184.108.40.206. I had a water leak event. The lights were supposed to flash blue. They instead turned solid blue. But that was sufficient notice. Canceled the alerts, but the lights are staying blue. Any ideas?