Typical - this morning, neither of my time-based events fired.
If this is a server load issue, it just got worse, because people like myself will now create a backup event, to raise the odds that this actually happen, increasing the load because of their already poor performance.
btk
January 11, 2016, 4:21pm
2
Yup. We’ve got a few long-standing threads on this already.
@slagle Lools like routine with sunset offset is failing for me at least with the new app update today. I have opened a ticket. Even putting the routine at a specific time failed.
I have a SmartApp that brightens lights in a zone when there is motion or a door opens. It dims the lights after a given timeout period.
I have 6 instances of the app on one hub, (6 different lighting zones), and 8 on another hub, in another building.
When the app initializes, it starts the scheduler to run a scheduleCheck() function every minute, to turn off lights, when appropriate.
It was working for months. Then it stopped dimming reliably.
I have determined that the scheduleCheck() function stops running as scheduled.
I have also noticed that it now usually schedules at the top of the minute, i.e., the seconds are zero. This did not used to be the case. And the time between scheduled calls can be 1, 2, or 3 minutes.
I have just installed a workaround, in which I re-initializ…
ryandetzel
January 11, 2016, 4:22pm
3
Embarrassing for ST. As a developer I’m lost as to how this happening and why they have not fixed it.
1 Like
slagle
January 11, 2016, 5:03pm
6
Please continue to use the current threads dedicated to this topic