I replied to my ticket email response from ST this morning, as my “Good Morning” routine only turned on my cabinet lights. Didnt change from night to home, or disarm SHM.
WTFO?
@jody.albritton it’s NOT fixed, see below, it missed the 7:30EST schedule AGAIN. Everyday it’s missing the 7:30 schedule. How do you want to debug this?
Handler Scheduled Time Actual Time Delay (msec) Execution (msec)
initialize 2016-04-27 4:30:00 PM EDT 2016-04-27 4:30:00.308 PM EDT 308 6234
initialize 2016-04-27 12:30:00 PM EDT 2016-04-27 12:30:00.274 PM EDT 274 7482
@jody.albritton see the below: until the 25th of April all 4 schedules in the 4 day were executed on time. Since the 26th the 7:30PM isn’t executing:
Handler Scheduled Time Actual Time Delay (msec) Execution (msec)
initialize 2016-04-27 4:30:00 PM EDT 2016-04-27 4:30:00.308 PM EDT 308 6234
initialize 2016-04-27 12:30:00 PM EDT 2016-04-27 12:30:00.274 PM EDT 274 7482
initialize 2016-04-27 7:30:00 AM EDT 2016-04-27 7:30:00.376 AM EDT 376 8602
initialize 2016-04-26 4:30:00 PM EDT 2016-04-26 4:30:00.264 PM EDT 264 6023
initialize 2016-04-26 12:30:00 PM EDT 2016-04-26 12:30:00.492 PM EDT 492 4579
initialize 2016-04-26 7:30:00 AM EDT 2016-04-26 7:30:01.964 AM EDT 1964 7082
initialize 2016-04-25 7:30:00 PM EDT 2016-04-25 7:30:03.384 PM EDT 3384 192857
initialize 2016-04-25 4:30:00 PM EDT 2016-04-25 4:30:01.583 PM EDT 1583 46028
initialize 2016-04-25 12:30:00 PM EDT 2016-04-25 12:30:00.453 PM EDT 453 8379
initialize 2016-04-24 7:30:00 PM EDT 2016-04-24 7:30:00.300 PM EDT 300 31837
initialize 2016-04-24 4:30:00 PM EDT 2016-04-24 4:30:01.303 PM EDT 1303 6502
initialize 2016-04-24 1:00:00 PM EDT 2016-04-24 1:00:00.461 PM EDT 461 1759
initialize 2016-04-23 7:30:00 PM EDT 2016-04-23 7:30:01.189 PM EDT 1189 188109
initialize 2016-04-23 4:30:00 PM EDT 2016-04-23 4:30:01.143 PM EDT 1143 6036
Come on @jody.albritton lets see a light at the end the tunnel somewhere. Ticker’s broken and until you guys see it you won’t fix it!.
Again it missed the 7:30 PM schedule today and nothing’s scheduled. What does it take to get attention something around here. I’ve sent you so many logs over the past 2 weeks with no response. This is just a simple thermostat scheduled with 4 schedules in a day. How much more basic can it get.
Application State
Name Value
schedule 4
Scheduled Jobs
None
Developer Options
Enable local child app discovery: What’s this?
Job History
Handler Scheduled Time Actual Time Delay (msec) Execution (msec)
initialize 2016-05-17 4:30:00 PM EDT 2016-05-17 4:30:00.240 PM EDT 240 2426
initialize 2016-05-17 12:30:00 PM EDT 2016-05-17 12:30:00.171 PM EDT 171 3167
initialize 2016-05-17 7:30:00 AM EDT 2016-05-17 7:30:00.374 AM EDT 374 4462
initialize 2016-05-16 7:30:00 PM EDT 2016-05-16 7:30:00.360 PM EDT 360 12171
initialize 2016-05-16 4:30:00 PM EDT 2016-05-16 4:30:00.261 PM EDT 261 3962
2 Likes
I’ve missed 2 Sunset schedules in the last couple of weeks and when I contact support, they look around, then tell me, well it timed out (104 and 120 seconds). Then they say, did it work last night, yes, ok let us know if it happens again
They don’t have a clue or at least it doesn’t seem like it
Rick
1 Like
Can you PM me the app ID for that section of logs? I will dig into the internal data and escalate with engineering.
1 Like
PM me your app id for the app that missed schedules, and the time and date where it missed.
1 Like
@RBoy Looks like you have a null value for target
{“logs”:[{“time”:1463538598065,“level”:“INFO”,“msg”:“HVAC OFF, Thermostat Cool: 90, Thermostat Heat: 50”}],“exception”:null,“target”:
1 Like
Jody can you elaborate a bit more so I can track it down. If this is an app issue I’m actually happy
1 Like
From the code this is the line:
log.info “HVAC OFF, Thermostat Cool: ${maxTemp}, Thermostat Heat: ${minTemp}”
not sure what can be null here? Is it before or after?
Is this SmartApp part of a parent child set up?
No it’s just a simple SmartApp.
I’m wondering if the app is timing out which is causing it not to schedule the next timer.
1 Like
Okay @jody.albritton thanks for your help, looks like maybe the platform was timing out the app while setting the thermostat setpoint (which is VERY surprising) and causing the chain to break. I guess one needs to use schedule instead of runOnce. Will post back once I see what’s going on now.
2 Likes
No worries. Message me on slack if you need to troubleshoot more.
1 Like
Still a thought if the thermostat setpoint is timing out, it still won’t set the setpoint so then also it’s moot in sorts since the temp won’t change and leaves me with the same issue. Thoughts on how to tackle it.
So guys, what do the metrics on Ticker say… is it working still or is it starting to fail like the previous one? More and more reports of time-based automation are starting to fail and of course it’s fruitless to email support when they find out that the app in question is not an official app.
7 Likes
I’m betting ticker is fine and now it’s just plain old platform overload.
Isn’t it strange how ST folks hide under the rocks when things go south? I wonder if it’s because they don’t want to admit there are issues or they have no idea what’s causing them.
2 Likes
While it may be caused by platform overload, ticker is at least starting to fail, if not failing outright.