1) Give a description of the problem
This piston worked until sometime last night (maybe DST messed it up?)
2) What is the expected behavior?
Lights should go on/off based on motion sensors and timers.
3) What is happening/not happening?
Lights do not go on when motion is detected. I was able to pause/start the piston and it worked for a few hours - but has stopped working again.
Strangely, there are times next to the Wait statements that make no sense:
4) Post a Green Snapshot of the piston
(UPLOAD YOUR IMAGE HERE)
5) Attach any logs (From ST IDE and by turning logging level to Full)
`I did not have logging on - but turned it on and ran Test and here are the results:
11/5/2017, 2:47:38 PM +817ms
+4ms ╔Received event [Home].test = 1509922058796 with a delay of 11ms
+237ms ║RunTime Analysis CS > 34ms > PS > 118ms > PE > 90ms > CE
+256ms ║Runtime (41350 bytes) successfully initialized in 118ms (v0.2.0fc.20171105) (247ms)
+261ms ║╔Execution stage started
+359ms ║║Comparison (enum) inactive is (string) active = false (9ms)
+362ms ║║Comparison (enum) inactive is (string) active = false (2ms)
+369ms ║║Condition #2 evaluated false (67ms)
+371ms ║║Condition group #1 evaluated false (state did not change) (73ms)
+387ms ║║Cancelling statement #7’s schedules…
+424ms ║║Executed virtual command [Light - Garage].wait (6ms)
+430ms ║║Requesting a wake up for Sun, Nov 5 2017 @ 2:52:39 PM PST (in 300.0s)
+460ms ║║Comparison (enum) inactive is (string) active = false (3ms)
+462ms ║║Condition #16 evaluated false (11ms)
+463ms ║║Condition group #10 evaluated false (state did not change) (13ms)
+465ms ║║Cancelling statement #11’s schedules…
+470ms ║║Executed virtual command [Light - Half Bath].wait (1ms)
+471ms ║║Requesting a wake up for Sun, Nov 5 2017 @ 2:49:39 PM PST (in 120.0s)
+486ms ║║Comparison (enum) inactive is (string) active = false (1ms)
+488ms ║║Condition #23 evaluated false (9ms)
+489ms ║║Condition group #17 evaluated false (state did not change) (11ms)
+493ms ║║Cancelling statement #18’s schedules…
+499ms ║║Executed virtual command [Light - Master Closet].wait (0ms)
+501ms ║║Requesting a wake up for Sun, Nov 5 2017 @ 2:49:39 PM PST (in 120.0s)
+515ms ║║Comparison (enum) inactive is (string) active = false (2ms)
+518ms ║║Condition #30 evaluated false (11ms)
+521ms ║║Condition group #24 evaluated false (state did not change) (15ms)
+524ms ║║Cancelling statement #25’s schedules…
+529ms ║║Executed virtual command [Light - Master Toilet].wait (1ms)
+531ms ║║Requesting a wake up for Sun, Nov 5 2017 @ 2:49:39 PM PST (in 120.0s)
+1599ms ║║Comparison (enum) inactive is (string) active = false (3ms)
+1603ms ║║Condition #37 evaluated false (1065ms)
+1604ms ║║Condition group #31 evaluated false (state did not change) (1068ms)
+1608ms ║║Cancelling statement #32’s schedules…
+1615ms ║║Executed virtual command [Light - Pantry].wait (1ms)
+1617ms ║║Requesting a wake up for Sun, Nov 5 2017 @ 2:48:40 PM PST (in 60.0s)
+1722ms ║╚Execution stage complete. (1464ms)
+1758ms ║Setting up scheduled job for Sun, Nov 5 2017 @ 2:48:40 PM PST (in 59.867s), with 4 more jobs pending
+1781ms ╚Event processed successfully (1783ms)`
Strangely - running test also reset all the timers - they are all now pending their timeouts and will turn off all the lights and I believe it will work again for a time.
What changed? I have been running this piston with little/no problems for months - but now it is choking 