Mode Manager has become unreliable

Mode Manager has become unreliable in the most recent couple of HE releases, I've even switched to the new integrated Mode Manager (and deleted the old app) and had the same issue as on the legacy app.

Sometimes it just doesn't change modes, sometimes it does, despite the presence sensors working perfectly according to my logs.

If I manually change the mode via Apple HomeKit (HE integration), it works as it should.

My Home / Away config is dead simple.

eg yesterday arvo my wife came home and the house stayed in Away mode:

I ended up manually turning on Home mode remotely for her (Why do wives never listen to instructions!). You can see that it did automatically go into away mode when she went out at 09:37 without issue.

@support_team Any ideas what is going on?

Checking.

I am still running the original Mode Manager here. No problems that I have seen with any of the recent updates. Still keeps chugging along changing modes as expected.

How do you have it set up?

Honestly, Mode: Away " Return" has been hit or miss for me for a long time, regardless of which version I've used.

IF you have an arrival rule, which most of us do, add the mode to the arrival rule.

Edit: Based on today i checked logs on all three. (Away never triggered)
Its normally the return that does not.

1- I left at 6:15AM
2- Johnny Three left at 8:08AM
3- Wynter Left at 2:14PM
None were present when all three were away.



Last Location event:

How its set up in New Integrated Mode manager:

@gopher.ny - Anything else we can provide to help possibly track down the culprit?

I only moved to the new one to see if that fixed the problem I was having.

As per my first post.

Until a couple of weeks ago it was rock solid for me - it was only when we went out one night as a family that I noticed the house was still in home mode, despite all presence sensors showing away. I manually put it in away mode and when we got home, it did change to Home by itself. There's been a couple of other instances since where it's failed to change modes, but there's been no consistency to it.

Btw, Victor from the Hubitat team has enabled a dev mode on my Prod hub to capture detailed logs, and I'll be keeping an eye on it over the next few days.

I wrote an advanced Mode Manager 2 years ago - Modes are not just periods, they are also states (home/away or awake/sleeping). I define modes but don't give them any periods. I removed mode manager completely, and set my own Mode Manager Advanced to handle it - that has worked best for me now for 2 years - and it integrates better with my manual overrides, the ability to trigger a 'mode check' when I'm playing and allows more periods to flow but still be overriden by sleeping regardless. I had to, since mode manager has no 'trigger' function except the 'trick' of coming back from away (ie; set a trigger to switch off away causes modes to re-check.) it was just to confused and hit or miss! Owntracks for Presence with my own App allows me to manage HSM, Alexa home/away and some virtual switches which let me manually override and set a mode for testing - works way better!

I don't use periods, except for Night Mode which is when we've gone to bed and the house locks the doors and arms the perimeter sensors - other than that it's all presence based.

I've now added a couple of RM rules with a 60 second delay to act as a safety net - mainly because I'd like to help the Hubitat team figure out what went wrong but without inconveniencing my family.

I’ve now replaced the built in mode manager with my RM rules and everything is now working as it should.

After the latest tweaks to mode manager, It makes more sense to me now - thanks @gopher.ny for putting up with my stupid questions.