Modes Changes in Routines are not Working!

I haven’t even touched my thermostats yet. That’s funny, because it was what got me into HA in the first place, with web connected thermostats. My lifestyle used to entail a lot of travel, so being able to cool down a condo in Arizona before arriving was great. But now, I’m not traveling much so I rarely touch my thermostats.

@smart, Yes, I know there are mode problems, I’ve experienced failed mode changes a few times. Every time I’ve tracked it down in the logs, written support, and they always say the same thing. That’s a pretty transient problem. If someone is having a routine always fail to do something, like change modes, then that would be a different case.

It is always intermittent for me… And the reason I have kept the sirens off the SHM. A pi##ed missus is bad for HA or a HAHAHA. @bravenel

Ya, my siren sits in a cabinet for now… And, HA is not worth jeopardizing HAHAHA :grinning:

1 Like

I too am not experiencing mode changes, even though the smartapp triggers

Known issue but please please report it to support.@Jason_Gray_Buchanan

I thought that they fixed it on Thursday but I see that the issue is back.

Ok… I’m starting to get pissed. Modes worked yesterday and not today.

Can someone please tell me what the hell is on line 459 of whatever code? It’s been the same exact 459 error and line number since the beginning. Modes are part of the core logic for this platforms apps and they are not working because my home thinks its Morning all day long so other apps will not fire because the mode is wrong.

I’m trying to be patient but once something is fixed I don’t expect it to be broken 2 days later.

02fbc785-6317-4552-8226-ff610e94bb07 4:20:03 PM: error java.lang.NumberFormatException @ line 459
02fbc785-6317-4552-8226-ff610e94bb07 4:20:03 PM: trace getSuffix(), index: 1
02fbc785-6317-4552-8226-ff610e94bb07 4:20:03 PM: trace prefix(unlocked'): And I unlocked
02fbc785-6317-4552-8226-ff610e94bb07 4:20:02 PM: trace prefix(turned'): I also turned
02fbc785-6317-4552-8226-ff610e94bb07 4:20:02 PM: trace getSuffix(), index: 0
02fbc785-6317-4552-8226-ff610e94bb07 4:20:02 PM: trace prefix(changed'): I changed
02fbc785-6317-4552-8226-ff610e94bb07 4:20:01 PM: debug HH autoExecute(), newMode: Home - Graces Home
02fbc785-6317-4552-8226-ff610e94bb07 4:20:01 PM: debug HH auto execute Grace's Home Someone Arrives
02fbc785-6317-4552-8226-ff610e94bb07 4:20:01 PM: trace recentNotPresent: null
02fbc785-6317-4552-8226-ff610e94bb07 4:20:01 PM: trace presenceStates: [[date:Tue Sep 15 13:20:01 PDT 2015, value:present]]
02fbc785-6317-4552-8226-ff610e94bb07 4:20:01 PM: trace t0: Tue Sep 15 13:10:01 PDT 2015, now: Tue Sep 15 13:20:01 PDT 2015
02fbc785-6317-4552-8226-ff610e94bb07 4:20:01 PM: trace daysOk = true
02fbc785-6317-4552-8226-ff610e94bb07 4:20:01 PM: debug evt.name: present
…

Modes are a disaster here too. SHM never has its arming/disarm happen because home and away modes are not being set via presence changes. Apps that rely on presence operate, but modes don’t change.

1 Like

Well that’s going to be a show stopper in some method some place…
It also shouldn’t take F O R E V E R to find…

Well support replied today saying that they have been tracking this issue for awhile and they still don’t have a fix. So it not looking like a quick fix.

Does SHM behave correctly if you manually change modes? If yes, then this is a presence issue. If no, then this is a mode change issue. It would be good to know which.

Have you uninstalled and reinstalled the Goodbye routine? If not, try that. It seems that something is corrupted in the data representing your apps (and routines). That might be why you get the 459 error.

Presence is working, as the apps that respond to presence fire. (open garage door, unlock door)

What method are you using to cause presence to change mode?

I’d pretty much given up on ST but with the new ios app figured i’d give it a try. Most of my mode changes are working but the simple one. The ‘Good Morning’ routine is supposed to fire at 5:15am and change to home mode from night but the mode change isn’t happening and no sign of Good Morning having run in the messages tab under notifications. Other, more complex triggers like ‘everyone leaves’ and ‘things quiet down’ work ok but the simple time based schedule isn’t happening.

I’ve tried re-saving it today to see what happens but so far the new ST seems a lot like the old ST in terms of reliability.

1 Like

Hey, it’s the same convoluted drama queen of backends it’s always been. The new mobile app didn’t really change any of that. There are, of course, always changes being made to the backend, some improvements, some introducing new bugs. They have made some progress, but they still have a long way to go. That’s a steady state situation!!

2 Likes

I’ve been having this issue for months now. I’ve reported it to support over and over again, with all kinds of “suggestions” for fixing the problem, so far nothing has. The particular problem I have is with my bedroom lights turning on for a motion sensor that’s only supposed to turn them on when in “Home” mode. Even in “Night” mode they go off. INCREDIBLY frustrating and really pisses off the wife…

This is the exact same problem that I submitted a ticket on a few days ago.
This issue started when I cut over to the V2 hub two weeks ago.

1 Like

At least for me the mode was not changing when running manually.

You have to look in the IDE logs to be sure, the app doesn’t update the mode changes very well.