Webcore Pistons not firing (November 5, 2017)

Known issue with ST as a result of the time change. Adrian is working on it

Also, WebCore has a new forum, would be best to visit/post there where all the WebCore expertise hangs out


Rick

1 Like

Awesome job, all working here.

I’ve update and mine still isn’t working. The next scheduled run time is an hour off because of DST.
image

This is probably because the time was scheduled before DST change hence it will be 1 hour out.
You can leave it alone and all subsequent schedules will be OK.
If you edit then save it should change. Maybe a test will sort it out.
Give it a try.

All my sensors in the house are dead right now, nothing is firing. I can manually execute a piston but that’s it.
Nothing it time based either.

Update WebCORE in IDE.

Doesn’t work. I just made a new Piston and it also showed the wrong next schedule run time. I’ve updated webCoRE in IDE. I’ve tried to edit the Piston and still developing the issue of the wrong next run schedule.

Moved the time up an hour. So if I want my Piston to run @ 6:50AM, I move the time to 7:50AM and it runs as schedule.

You hope. :wink:

Interestingly, whilst everything looks fine from the app, most of my ZigBee (Lightify 4x) switches are still nothing kicking anything off. Any ideas?

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 :frowning: 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. :frowning:. Totally makes sense why it would go buggy, hard to test for something like that before.

Good luck with trying to find a fix.