1) Give a description of the problem
This piston works in that it controls thermostat as desired until I want it to stop controlling thermostat. The last IF statement is supposed to tell the thermostat to resume program. This has worked, but it works so well that the piston will not let manual interaction happen with the thermostat. It will not allow me to change the temp manually.
2) What is the expected behavior?
I need it to resume program after the early morning interaction, but completely release control of the thermostat until the next day.
3) What is happening/not happening?
See above
4) Post a Green Snapshot of the piston
5) Attach any logs (From ST IDE and by turning logging level to Full)
( 11/26/2018, 6:13:05 AM +141ms
+252ms ╔Stopping piston…
+385ms ╚Piston successfully stopped (134ms)
11/25/2018, 6:58:59 AM +119ms
+1ms ╔Received event [Home].time = 1543157940000 with a delay of -882ms
+161ms ║RunTime Analysis CS > 33ms > PS > 64ms > PE > 64ms > CE
+164ms ║Runtime (40971 bytes) successfully initialized in 64ms (v0.3.108.20180906) (162ms)
+165ms ║╔Execution stage started
+184ms ║║Comparison (time) 25139292 is_after (time) 21000000 = true (9ms)
+186ms ║║Time restriction check passed
+188ms ║║Cancelling condition #6’s schedules…
+189ms ║║Condition #6 evaluated true (16ms)
+198ms ║║Comparison (enum) present is (string) present = true (2ms)
+200ms ║║Condition #7 evaluated true (10ms)
+211ms ║║Comparison (enum) heat is (string) heat = true (2ms)
+213ms ║║Condition #8 evaluated true (12ms)
+255ms ║║Duration 5210307ms for was_less_than_or_equal_to >= 10000ms threshold = true
+256ms ║║Comparison (decimal) 29.0 was_less_than_or_equal_to (integer) 43 = true (35ms)
+258ms ║║Condition #9 evaluated true (44ms)
+267ms ║║Comparison (decimal) 67.0 is_less_than_or_equal_to (integer) 66 = false (2ms)
+269ms ║║Condition #17 evaluated false (10ms)
+271ms ║║Condition group #1 evaluated false (state did not change) (98ms)
+279ms ║║Comparison (time) 25139395 happens_daily_at (time) 25140000 = true (0ms)
+280ms ║║Time restriction check passed
+282ms ║║Cancelling condition #13’s schedules…
+283ms ║║Condition #13 evaluated true (8ms)
+288ms ║║Cancelling statement #13’s schedules…
+292ms ║║Requesting time schedule wake up at Mon, Nov 26 2018 @ 6:59:00 AM PST
+296ms ║║Cancelling condition #12’s schedules…
+297ms ║║Condition group #12 evaluated true (state changed) (22ms)
+299ms ║║Cancelling condition #11’s schedules…
+300ms ║║Condition group #11 evaluated true (state changed) (25ms)
+303ms ║║Cancelling statement #15’s schedules…
+1230ms ║║Executed physical command [THERMOSTAT].resumeProgram() (923ms)
+1232ms ║║Executed [THERMOSTAT].resumeProgram (925ms)
+1236ms ║╚Execution stage complete. (1070ms)
+1238ms ║Setting up scheduled job for Mon, Nov 26 2018 @ 6:59:00 AM PST (in 86399.644s)
+1246ms ╚Event processed successfully (1246ms)
11/24/2018, 6:58:59 AM +91ms
+1ms ╔Received event [Home].time = 1543071540000 with a delay of -909ms
+155ms ║RunTime Analysis CS > 29ms > PS > 62ms > PE > 63ms > CE
+158ms ║Runtime (40967 bytes) successfully initialized in 62ms (v0.3.108.20180906) (155ms)
+159ms ║╔Execution stage started
+176ms ║║Comparison (time) 25139257 is_after (time) 21000000 = true (7ms)
+177ms ║║Time restriction check failed
+179ms ║║Cancelling condition #6’s schedules…
+180ms ║║Condition #6 evaluated false (14ms)
+181ms ║║Condition group #1 evaluated false (state did not change) (16ms)
+189ms ║║Comparison (time) 25139277 happens_daily_at (time) 25140000 = true (1ms)
+191ms ║║Time restriction check failed
+192ms ║║Condition #13 evaluated false (6ms)
+194ms ║║Cancelling statement #13’s schedules…
+198ms ║║Requesting time schedule wake up at Sun, Nov 25 2018 @ 6:59:00 AM PST
+201ms ║║Condition group #12 evaluated false (state did not change) (16ms)
+202ms ║║Condition group #11 evaluated false (state did not change) (18ms)
+205ms ║╚Execution stage complete. (47ms)
+207ms ║Setting up scheduled job for Sun, Nov 25 2018 @ 6:59:00 AM PST (in 86400.703s)
+215ms ╚Event processed successfully (214ms))