I have seen this issue crop up occasionally here but it appears a little sporadic. and apologies for the long post - trying to explain this isn’t easy!
I have routines set in order to change the location mode to either Home, Away or Night. Away is triggered by all location devices (phones) leaving the site, Home is simply triggered by a device coming home, night set based on time and disabled again by time (both if a location device is on site) I then have automations that trigger based on that location status.
Recently I noticed that for (reasons unknown) the night automation was triggering but security wasn’t arming (armed (stay) ) lights etc still turned off as expected. Tinkering got this all working again (pretty sure I deleted and started again).
Doing this then seemed to break the ‘Away’ status (assuming this is the cause not an ST thing as reported back in 2019?). Now when everyone leaves the site, the location Away does not trigger so automations relying on that also don’t trigger (i.e. security still shows as disarmed). What is really confusing, is if i am physically away at work and manually set the location mode to away, the automations trigger as you would expect (Security arms). When I return home, the location mode changes as it should back to Home (thus disarming security and so on). So why on earth is the away status not triggering when returning does as this means the geolocation is working??? All was working well previously until now so really not sure how tinkering with a different automation would affect this. Any help greatly appreciated