It’s Aliiiive!
Updated to new version and all is working again.
Thanks!
Same here. All next scheduled pistons are an hour early for me, after updating webcore and re-saving all time-based pistons.
None of my pistons were firing this morning when I got up - checked this thread, updated Webcore smart app - all working now
1 Like
Against my better judgement I deleted webCoRE and did a re-install and I’m still in the same boat. Now I have to re-write all my Pistons 
Gives me something to do on Sunday I guess but I’ll wait until I get confirmation that the DST bug is fixed.
It is not a webCoRE servers issue - there is a bug in webCoRE that happens as a result of the DST changes. It appears that calculating the time of day has some problems leading to the wrong time of the day. This caused some pistons to go into a crazy loop where they would think they need to run because the next run was in the past (one hour off). This prompted ST to restrict all the piston activity (safety measure - they did the right thing). They have informed me this morning about it and I have been trying to figure out what happened. So far I think the problem lies in the time calculation logic, as adding 7 hours to “midnight” causes that result to be 6pm (midnight is still in EDT). I will get to the bottom of this and make sure this won’t happen again, the old version should become steady again past midnight of Nov 5-6. Will try to push out a fix before that. Sorry for the trouble, I will get this sorted out. Alternatively, don’t do anything and things should come back to normal by tomorrow morning (that is what I expect).
Thank you
11 Likes
Thanks Ady, Appreciated!
Many people are now depending on WebCore these days as it’s the best, and only, way to automate things in ST.
IMHO this should become part of standard ST.
1 Like
Looks like it’s happening again, but I guess we wait until the clock has gone around tomorrow for it all to settle?
I think Ady is looking at the issue again to try and give a permanent issue. Things have gone awry again.
I would keep checking back for an update to webCoRE.
I thought I was losing my mind. All of my ‘things’ work but none of my automation does. Too bad. 
. Totally makes sense why it would go buggy, hard to test for something like that before.
Good luck with trying to find a fix.
Yes, I noted on anther similar threat that my system is dead in the water again even after this mornings fix.
No problem, it’s nice and sunny. I should be outside anyway 
Same here, no automatic lighting etc (uk) . I’ll just keep badgering Alexa 
to do it. Good luck with the fix, and I appreciate all the good work as I’m sure many others using webcore do as well. 
We’re Baaaack! Thanks !
Version 0fd should fix the problems, please update.
2 Likes
I’ve updated but it keeps saying in the Web GUI “A newer UI version (v0.2.0fd.20171105) is available, please hard reload this web page to get the newest version.”
How do I “hard reload” the webpage. I’ve closed everything out. I’ve signed out. Signed back in. And I keep getting this message. When I go to create a new Piston it says I’m using version 0.2.0cd. When I go to the SmartApp it says I’m using 0.2.0fd
Try to hold down control and hit F5, that cleared the hard reload message for me
Thanks! That worked on the hard reload. Now going to test the updated webCoRE version.
1 Like
@matthewsfamily0914 do another update from the IDE? There were two today.
Update looks good on my end. It is now reporting the proper “Next scheduled”. Great job @ady624
This is much appreciated!
1 Like
I’m on 2fd and nextscheduleddate still shows invalid…