Mode change at specific time

#1

1) Give a description of the problem
ST mode is not changing when the specified time is reached. Tonight (Saturday 11/24), the mode should change to night at 11:59pm. Piston quick facts say it will happen at 11pm??

2) What is the expected behavior?
When a specific time is reached, the mode changes to night around the time all family members are typically asleep on a weekday/weekend.

3) What is happening/not happening?
The first part of the piston isn’t working (mode change at specific time), but the 2nd part is just fine (routine to mode change and other things);

4) Post a Green Snapshot of the pistonimage

image
image.png1178×853 47.3 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
N/A

#2

Can you post logs from your piston at 11:00 or 11:59 so we can see what’s happening. I have a theory you might be seeing the same thing I am here:

#3

Sure i just don’t know how to do that. Webcore says my logs are empty. Please share. Skimming through your post, it looks like there is a webcore bug, is that right?

Thanks!

#4

Is this what you need?

11/24/2018, 11:58:59 PM +91ms
+1ms ╔Received event [Gates Homestead].time = 1543121940000 with a delay of -910ms
+168ms ║RunTime Analysis CS > 22ms > PS > 125ms > PE > 22ms > CE
+171ms ║Runtime (40210 bytes) successfully initialized in 125ms (v0.3.108.20180906) (168ms)
+172ms ║╔Execution stage started
+182ms ║║Comparison (time) 86339270 happens_daily_at (time) 82800000 = false (1ms)
+184ms ║║Condition #2 evaluated false (5ms)
+188ms ║║Cancelling statement #2’s schedules…
+192ms ║║Requesting time schedule wake up at Sun, Nov 25 2018 @ 11:00:00 PM EST
+198ms ║║Comparison (time) 86339286 happens_daily_at (time) 86340000 = true (1ms)
+200ms ║║Time restriction check passed
+202ms ║║Cancelling condition #3’s schedules…
+203ms ║║Condition #3 evaluated true (7ms)
+212ms ║║Cancelling statement #3’s schedules…
+216ms ║║Requesting time schedule wake up at Sun, Nov 25 2018 @ 11:59:00 PM EST
+219ms ║║Cancelling condition #1’s schedules…
+220ms ║║Condition group #1 evaluated true (state changed) (41ms)
+223ms ║║Cancelling statement #4’s schedules…
+227ms ║║Skipping task 5 because of mode restrictions
+236ms ║║Comparison (string) null executes (string) :45ac4cb9a0906dbc1f84fc001310c002: = false (2ms)
+237ms ║║Condition #7 evaluated false (6ms)
+239ms ║║Condition group #6 evaluated false (state did not change) (7ms)
+242ms ║╚Execution stage complete. (71ms)
+244ms ║Setting up scheduled job for Sun, Nov 25 2018 @ 11:00:00 PM EST (in 82860.665s), with 1 more job pending
+253ms ╚Event processed successfully (252ms)
11/24/2018, 10:59:59 PM +146ms
+1ms ╔Received event [Gates Homestead].time = 1543118400000 with a delay of -855ms
+131ms ║RunTime Analysis CS > 24ms > PS > 80ms > PE > 27ms > CE
+133ms ║Runtime (40233 bytes) successfully initialized in 80ms (v0.3.108.20180906) (131ms)
+134ms ║╔Execution stage started
+145ms ║║Comparison (time) 82799288 happens_daily_at (time) 82800000 = true (1ms)
+147ms ║║Time restriction check failed
+149ms ║║Condition #2 evaluated false (6ms)
+150ms ║║Cancelling statement #2’s schedules…
+155ms ║║Requesting time schedule wake up at Sun, Nov 25 2018 @ 11:00:00 PM EST
+165ms ║║Comparison (time) 82799306 happens_daily_at (time) 86340000 = false (0ms)
+167ms ║║Condition #3 evaluated false (7ms)
+179ms ║║Cancelling statement #3’s schedules…
+185ms ║║Requesting time schedule wake up at Sat, Nov 24 2018 @ 11:59:00 PM EST
+189ms ║║Condition group #1 evaluated false (state did not change) (47ms)
+200ms ║║Comparison (string) null executes (string) :45ac4cb9a0906dbc1f84fc001310c002: = false (3ms)
+203ms ║║Cancelling condition #7’s schedules…
+204ms ║║Condition #7 evaluated false (10ms)
+206ms ║║Cancelling condition #6’s schedules…
+208ms ║║Condition group #6 evaluated false (state changed) (14ms)
+214ms ║╚Execution stage complete. (79ms)
+216ms ║Setting up scheduled job for Sat, Nov 24 2018 @ 11:59:00 PM EST (in 3540.639s), with 1 more job pending
+232ms ╚Event processed successfully (231ms)
11/24/2018, 9:11:06 PM +293ms
+1ms ╔Received event [Gates Homestead].time = 1543111867278 with a delay of -986ms
+103ms ║RunTime Analysis CS > 26ms > PS > 57ms > PE > 21ms > CE
+106ms ║Runtime (40233 bytes) successfully initialized in 57ms (v0.3.108.20180906) (104ms)
+107ms ║╔Execution stage started
+164ms ║║Executed physical command [Kitchen Wood Wall Downlights].off() (19ms)
+165ms ║║Executed [Kitchen Wood Wall Downlights].off (22ms)
+186ms ║║Executed physical command [Living Room Sconces].off() (18ms)
+188ms ║║Executed [Living Room Sconces].off (20ms)
+192ms ║╚Execution stage complete. (84ms)
+194ms ║Setting up scheduled job for Sat, Nov 24 2018 @ 11:00:00 PM EST (in 6533.514s), with 1 more job pending
+204ms ╚Event processed successfully (204ms

#5

Your time triggers are working correctly (or at least did during that pass), and “time restriction passed” means webCoRE recognized it was Saturday. But your “only while home” restriction is what prevented the mode change (see bold line above). Your hub must have been in some other mode at the time the piston ran, so it didn’t change to Night.