I’ve just changed to SHM to Away whilst the active mode Night.
This did not force a Mode to change (to Away) so a couple of routines I have in CoRE failed. Its been a while since I changed SHM to Away (from Home). Has anyone else seen anything similar?
I’ve logged a ticket with ST support (UK). I’ll feedback any updates here.
Seems like they’ve had issues with that. One user saw something similar (although on disarm, with the alarm actively sounding, ouch):
Sorry, I’m confused. What do you have set up to change mode to away?
The SHM alarm states (arm away, arm Home, and disarm) are completely independent of modes ( initially home, away, and night, but you can add more and change them to whatever you want).
Just changing the alarm state won’t automatically change the mode.
Modes can be changed with a switch which triggers a routine, with a routine, or with some smart apps.
Alarm states can be changed manually through the mobile app, with a routine, or unofficially with some smart apps.
https://support.smartthings.com/hc/en-us/articles/205380154-Smart-Home-Monitor
So if you want changing the SHM alarm state to trigger a mode change, you have to have something set up to do that. Core could, but only if you set it up to do that.
There has been a recent bug reported where changing the mode would not then trigger the things that were supposed to trigger from that mode change. But that sounds like the opposite of the problem that you’re describing.
Thanks for clarifying. Makes sense now. For some reason I was sure this had worked previously, obviously not! Thanks again.