Yesterday I noticed things weren’t trigger. After a little digging I quickly noticed that location modes weren’t actually firing. Digging into the logs I saw this template.
I haven’t changed anything in weeks… Anyone else having this issue?
It appears to mostly be in the Groovy SmartApps. Like WebCore, I can see what the $locationMode is, but the Triggers don’t fire. The same goes for any other Groovy apps. Is this their not so subtle way to push us off of those to their automations and rules api?
Same issue with location mode not changing here. I have a simple good morning scene that changes my location mode to “home” and a good night scene that changes the mode to “night”. Running these scenes has no effect on location mode but can control other things (e.g., switches). Only way to change is manually via actiontiles.
This is all within the SmartThings app so no groovy, webcore pistons, etc. involved.
Worked fine before but randomly stopped working 3-4 days ago.
This had happened a month or two back for me and then resolved after a couple of days. I noticed it with Webcore, so I posted on their forum and others had noted the same. Never knew why it happened, but I wasn’t alone. It is now happening to me again too.
Same issue here for several days now, and this is affecting any SmartApp (WebCore, ActionTiles, BlueIris, etc…) that is using LocationMode.
I’ve migrated the mode change logic to HA (Home Assistant) and I’m calling SmartThings Scenes from HA to update ST.
Hey Steve, several months back I’ve created the same logic for location modes in HA (Home Assistant) and both systems (HA and ST) have they own Modes and Automations. I’ve decided this way so if I had an issue with one System it would affect the other.
I’m just using HA Automations to replace WebCore and calling ST Scenes to change the modes in ST.
Likewise - the mode change is being recognized by Smart Lighting. Support claims that my logs submitted last week show that the automation was being triggered but clearly there were issues as I know they weren’t.
I had the same issue today and few other times in the last 2-3 weeks. I seems to be working at the moment but clearly this mechanism isn’t as reliable as it should be. I am just using the ST automation to call a scene that changes the mode.
Is there a better way to control location mode? Anything simpler and 100% reliable?