1) Give a description of the problem
I have a piston design to trigger at a time of day. Since daylight savings ended last night, it is triggering an hour early but I’m not sure why.
2) What is the expected behavior?
The piston would trigger at 4pm and then show that it is scheduled to run at 8am.
3) What is happening/not happening?
The piston just triggered at 3pm and it is showing that is scheduled to run next at 7am.
4) Post a Green Snapshot of the piston
5) Attach any logs (From ST IDE and by turning logging level to Full)
I there wasn’t anything in the SmartThings IDE logs from 3pm, but here’s the logs from webCoRE
11/5/2017, 2:59:59 PM +82ms
+1ms ╔Received event [Home].time = 1509912000000 with a delay of -918ms
+184ms ║Runtime (43413 bytes) successfully initialized in 47ms (v0.2.0fc.20171105) (182ms)
+186ms ║╔Execution stage started
+274ms ║║EcobeeAway:
+276ms ║║Executed virtual command log (10ms)
+283ms ║║false
+284ms ║║Executed virtual command log (1ms)
+292ms ║║SmartThingsAway:
+293ms ║║Executed virtual command log (1ms)
+301ms ║║false
+302ms ║║Executed virtual command log (1ms)
+306ms ║╚Execution stage complete. (121ms)
+308ms ║Setting up scheduled job for Mon, Nov 6 2017 @ 7:00:00 AM EST (in 57600.611s), with 1 more job pending
+325ms ╚Event processed successfully (325ms)