This piston was working perfectly until two days ago


#1

1) Give a description of the problem
The piston was humming along perfectly until two days ago

2) What is the expected behavior?
It turns on the lights at 4:50 am a gradually comes to 80%.

3) What is happening/not happening?
The light isn’t turning on at all in the morning now.

4) Post a Green Snapshot of the pistonimage

5) Attach any logs (From ST IDE and by turning logging level to Full)
4/4/2018, 5:59:59 AM +148ms
+1ms ╔Received event [Home].time = 1522836000000 with a delay of -852ms
+189ms ║RunTime Analysis CS > 24ms > PS > 57ms > PE > 108ms > CE
+192ms ║Runtime (43643 bytes) successfully initialized in 57ms (v0.3.000.20180224) (190ms)
+193ms ║╔Execution stage started
+202ms ║║Comparison (time) 21599348 happens_daily_at (time) 17400000 = false (0ms)
+204ms ║║Cancelling condition #12’s schedules…
+204ms ║║Condition #12 evaluated false (4ms)
+209ms ║║Cancelling statement #12’s schedules…
+212ms ║║Requesting time schedule wake up at Thu, Apr 5 2018 @ 4:50:00 AM EDT
+215ms ║║Condition group #1 evaluated false (state did not change) (16ms)
+226ms ║║Comparison (integer) 0 is_inside_of_range (integer) 1 … (integer) 80 = false (4ms)
+228ms ║║Condition #46 evaluated false (10ms)
+229ms ║║Condition group #41 evaluated false (state did not change) (12ms)
+234ms ║║Comparison (time) 21599380 happens_daily_at (time) 21600000 = true (1ms)
+237ms ║║Time restriction check passed
+238ms ║║Cancelling condition #40’s schedules…
+239ms ║║Condition #40 evaluated true (7ms)
+240ms ║║Cancelling statement #40’s schedules…
+244ms ║║Requesting time schedule wake up at Thu, Apr 5 2018 @ 6:00:00 AM EDT
+251ms ║║Comparison (string) :cd00529a49d38014a97f88a838fbc3b3: is_any_of (string) :0b4c38241cd3f9d5bc3e816c32944d25:,:062a023dd7333a8b86feb07f041dfd0c: = false (3ms)
+252ms ║║Condition #37 evaluated false (6ms)
+253ms ║║Condition group #39 evaluated false (state did not change) (22ms)
+256ms ║╚Execution stage complete. (63ms)
+258ms ║Setting up scheduled job for Thu, Apr 5 2018 @ 4:50:00 AM EDT (in 82200.595s), with 1 more job pending
+264ms ╚Event processed successfully (264ms)
4/4/2018, 4:49:59 AM +164ms
+1ms ╔Received event [Home].time = 1522831800000 with a delay of -836ms
+206ms ║RunTime Analysis CS > 32ms > PS > 57ms > PE > 117ms > CE
+209ms ║Runtime (43644 bytes) successfully initialized in 57ms (v0.3.000.20180224) (208ms)
+210ms ║╔Execution stage started
+218ms ║║Comparison (time) 17399380 happens_daily_at (time) 17400000 = true (0ms)
+221ms ║║Time restriction check passed
+222ms ║║Cancelling condition #12’s schedules…
+223ms ║║Condition #12 evaluated true (7ms)
+224ms ║║Cancelling statement #12’s schedules…
+227ms ║║Requesting time schedule wake up at Thu, Apr 5 2018 @ 4:50:00 AM EDT
+233ms ║║Comparison (string) :cd00529a49d38014a97f88a838fbc3b3: is_any_of (string) :0b4c38241cd3f9d5bc3e816c32944d25:,:062a023dd7333a8b86feb07f041dfd0c: = false (2ms)
+234ms ║║Condition #26 evaluated false (5ms)
+235ms ║║Condition group #1 evaluated false (state did not change) (19ms)
+244ms ║║Comparison (integer) 0 is_inside_of_range (integer) 1 … (integer) 80 = false (2ms)
+247ms ║║Condition #46 evaluated false (9ms)
+249ms ║║Condition group #41 evaluated false (state did not change) (12ms)
+254ms ║║Comparison (time) 17399416 happens_daily_at (time) 21600000 = false (1ms)
+255ms ║║Condition #40 evaluated false (3ms)
+256ms ║║Cancelling statement #40’s schedules…
+259ms ║║Requesting time schedule wake up at Wed, Apr 4 2018 @ 6:00:00 AM EDT
+261ms ║║Condition group #39 evaluated false (state did not change) (10ms)
+264ms ║╚Execution stage complete. (55ms)
+265ms ║Setting up scheduled job for Wed, Apr 4 2018 @ 6:00:00 AM EDT (in 4200.571s), with 1 more job pending
+273ms ╚Event processed successfully (273ms)
REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.


#2

Can you still control the light bulb through ST?


#3

Yes, I have it setup also using Room Manager for the rest of the day and that is working.


#4

Enable Trace on the piston so we can see the trace condition #s


#5

Well, I think that I figured it out! The last two nights my hubbie was up past when the house goes to sleep and the Mode is changed to Night. So when he said “Good Night” to Alexa, it changed the Mode to Tom’s Bedtime. Normally this happens that he goes to bed before the house and the Mode is eventually set to Night. In the piston, it is set to run if the Mode is Night or Home and in the morning the Mode was still set to Tom’s Bedtime so it wasn’t firing. I have added Tom’s Bedtime to the Modes to run. I will see what happens tomorrow.


#6

We need to reprogram Tom!


#7

Ha! That would be good!