Pistons have stopped working! [daylight savings time issues]

fixed
#21

Some more reports here:

And numerous reports of General ST instability going on:

#22

Yeah, same here, no subscriptions work whatsoever. Time to contact ST

#23

Suprise! Was end of DST in the USA, related I wonder?

#24

Yes. ST placed a rate limit on webCoRE because some pistons started executing like crazy because of the DST. I donā€™t know what the rate limit is, looks like 0, as none of my pistons execute at all. But will try to get this fixed. Not sure how quick I can get someone to react, itā€™s still early morning on the west coast.

#25

No errors in the error log.

#26

Hey, at least the time change worked fine this year, unlike last year, ST got something right

To the question posted a bit above, do I recall that you are working with ST to get this app officially supported?

Thanks Adrian for all you do

Rick

Issue with daylight savings possibly?
#27

Quick dirty fix. Please update to 0fc to get it back working. Thank you and sorry for the trouble.

#28

You absolutely rock!

#29

Thanks a bunch for the early morning fix!

#30

Top man. Thanks.

#31

Now thatā€™s service!!

#32

Iā€™m new to webCoRE and it looks like I picked a bad day to start transitioning from basic ST automations. Can someone provide a little more details behind how to ā€œupdate 0fcā€? I havenā€™t a clue what that is. Otherwise, Iā€™ll wait a couple days to implement. :wink:

#33

So hereā€™s what I think happened. I am using UTC time throughout webCoRE (a common approach in the telecom industry) to avoid any DST issues. So when youā€™re piston runs at 9pm on Saturday before the DST and it is scheduled to run at 9pm on Sunday after the DST, I will work in UTC times, meaning the delta time between the two time points will be 25 hours. So I do a runIn in 25 hours (the request is already DST adjusted) - SmartThings was not ā€œadjustingā€ it to DST before, it seems that they added a fix this year that will adjust that runIn time with DST. This is most likely because some programmers and most DYI users would not be aware of what DST entails and would just send the unadjusted runIn time. Which now may explain why some apps worked fine this time around. But it seems that broke webCoRE :smiley: Iā€™ll see with ST what exactly happens and Iā€™ll do some experiments simulating DST to see what exactly happens. Until then, ST will most likely remove the rate limit at some point - it affects certain versions of webCoRE - when they start their working schedule - itā€™s Sunday early morning there, so I would not expect anyone to be available to really dig in and fix the issue. This seems to have been an emergency fix last night and ST was kind enough to let me know - I did have a message explaining the problem and the fix.

#34

Update the app in the IDE. He made a change to fix the issue.

#35

I just finished updating and everything is working better. BUT. I have logging on for one of my pistons and it looks like itā€™s displaying 1 hour behind. I.E. If I want it to sent an email at 4am it is showing the wake up time for 3am. Anyone else seeing this?

ā•”Starting pistonā€¦ (v0.2.0fc.20171105)
+671ms ā•‘ā•”Subscribing to devicesā€¦
+927ms ā•‘ā•šFinished subscribing (261ms)
+969ms ā•‘Comparison (time) 33318752 happens_daily_at (time) 0 = false (3ms)
+984ms ā•‘Cancelling statement #12ā€™s schedulesā€¦
+993ms ā•‘Requesting time schedule wake up at Sun, Nov 5 2017 @ 11:00:00 PM EST
+1029ms ā•‘Comparison (time) 33318816 happens_daily_at (time) 14400000 = false (1ms)
+1032ms ā•‘Cancelling condition #4ā€™s schedulesā€¦
+1034ms ā•‘Cancelling statement #4ā€™s schedulesā€¦
+1036ms ā•‘Requesting time schedule wake up at Mon, Nov 6 2017 @ 3:00:00 AM EST
+1038ms ā•‘Cancelling condition #1ā€™s schedulesā€¦
+1080ms ā•‘Setting up scheduled job for Sun, Nov 5 2017 @ 11:00:00 PM EST (in 49481.132s), with 1 more job pending
+1105ms ā•šPiston successfully started (1102ms)

#36

My piston is set for 12am and 4am.

#37

My next scheduled piston is for 25 minutes to sunset and it is scheduled to run at 5:07:00 PM which is correct. However, Iā€™m in AZ and our time doesnā€™t change for DST so that may be why my piston times are correct.

#38

Nice work on quick resolution! Thanks!

#39

Thanks Boxfanā€¦ I have a piston that runs 1 hours before sunset and itā€™s next scheduled time is also correct. (4:06pm and sunset is 5:05pm) . It looks like itā€™s a issue with my ā€œhappens daily atā€ .

I checked my morning routine and itā€™s Next scheduled is 5am where the piston is set to 6am.

#40

On the road here. Just updated on my phone. Some 1/2 hr later i got a email i should have seen some 6 hrs ago. Not able to debug here. CET