Pistons have stopped working! [daylight savings time issues]

fixed
#121

Initial test seems to have worked - but what are 3 blue carrots in the trace meaning?

32 PM
Screen Shot 2017-11-05 at 3.36.32 PM.png774Ɨ282 24.7 KB

#122

Iā€™m sorry, it would REALLY be more helpful if you explain - I am pressured to leave home by wife, have NO time to read through logs and realize what exactly youā€™re expecting it to do. Whatā€™s wrong?

#123

My scheduled pistons, which had been off by an hour, are correct now.

#124

Sorry, found out.
Since the house was in Armed and Night modus when things shut down.
When i disarmed, shut of camera and such, there was no trigger changing Night to Home.
So therefore the light triggers did not fire the turn on lights.
My bad, but lots of things happened here at the same time.
So everything seems ok here now.
!!! Great work !!!
And there was no error in the logs, since there was no error.
Just chain reaction from lost status then.
Well well.

#125

Might be just me, but I have a piston firing daily at 5:20 AM (time happens daily at) and even though I paused and resumed multiple time, itā€™s still scheduled to run an hour early tomorrow, at 4:20 AM

Edit: Iā€™m on 0fd

@Einars are all your pistons correctly scheduled?

#126

After updating to the very latest version as of a few minutes ago, my pistons are now working again. However the Dashboard in Chrome 61 keeps giving me this error: ā€œA newer UI version (v0.2.0fd.20171105) is available, please hard reload this web page to get the newest version.ā€

Iā€™ve tried a hard reload several times and it does not resolve the issue (F12, right click the reload icon, choose Hard Reload).

Ideas?

#127

Initial testing of triggers and timers seem to be working. Will try some more.

#128

Yeah, many things may be a result of pistons being forcefully killed by ST

#129

Oh I have not changed the JSā€¦

#130

@ady624 either Iā€™m stupid or bearer of bad news but I thought you might want to have a look at my earlier post.

#131

I updated everything, but Iā€™m getting this in the loggingā€¦

WARNING: Results may be unreliable because the parent appā€™s version (v0.2.0fd.20171105) is newer than the child appā€™s version (v0.2.0fc.20171105). Please consider updating both apps to the same version.

#132

Fixed now, please reload the dashboard to get the latest child app code.

#133

Canā€™t get anything to workā€¦the fix earlier did the trick, but this one isnā€™tā€¦:frowning:

#134

Can you please edit the piston, maybe even that time, then save and see? Thank u

#135

Edited without change: stayed scheduled 1h too soon.

Edited and changed time: still scheduled 1h too soon, now scheduled at 4:21 instead of 5:21.

#136

Are you sure you also published? Both parent and child apps?

#137

All 4 published here.

#138

Affirmative, triple checked

#139

What timezone are you in?

#140

Same as you I think, EST.