1) Give a description of the problem
I want to power on lights and turn them off after 5min but for some reason they are not turned off after the turning on.
2) What is the expected behaviour?
Turn on lights and turn them off after 5min.
3) What is happening/not happening?
Is not turning off the lights after the turn on.
**4) Post a Green Snapshot of the piston![image|45x37]
Based on the door closing after you open it, the cancelling policy (TCP) for the timer would have to be changed to ‘Never’, I believe.
In addition, would you not need to change the piston to asynchronous, or the piston would hog the scheduling for the 5 minute window?
These are just my (totally!) uneducated guesses based on my limited knowledge thus far.
Nope is not working. Here is the log:
11/23/2020, 3:25:55 PM +88ms
+0ms ╔Received event [Mansion].time = 1606137956024 with a delay of -937ms
+118ms ║RunTime Analysis CS > 22ms > PS > 40ms > PE > 56ms > CE
+122ms ║Runtime (39274 bytes) successfully initialized in 40ms (v0.3.110.20191009) (120ms)
+123ms ║╔Execution stage started
+124ms ║╚Execution stage complete. (2ms)
+126ms ╚Event processed successfully (127ms)
11/23/2020, 3:21:45 PM +616ms
+1ms ╔Received event [Гаражна Врата].contact = closed with a delay of 78ms
+86ms ║RunTime Analysis CS > 19ms > PS > 33ms > PE > 34ms > CE
+89ms ║Runtime (39272 bytes) successfully initialized in 33ms (v0.3.110.20191009) (87ms)
+90ms ║╔Execution stage started
+103ms ║║Comparison (enum) on is (string) off = false (1ms)
+104ms ║║Cancelling condition #19’s schedules…
+105ms ║║Condition #19 evaluated false (11ms)
+106ms ║║Cancelling condition #1’s schedules…
+107ms ║║Condition group #1 evaluated false (state changed) (13ms)
+140ms ║║Comparison (time) 55305726 is_between (datetime) 1606143480000 … (time) 79200000 = false (7ms)
+142ms ║║Condition #15 evaluated false (33ms)
+143ms ║║Condition group #13 evaluated false (state did not change) (34ms)
+145ms ║╚Execution stage complete. (56ms)
+146ms ╚Event processed successfully (146ms)
11/23/2020, 3:20:55 PM +888ms
+1ms ╔Received event [Гаражна Врата].contact = open with a delay of 81ms
+90ms ║RunTime Analysis CS > 20ms > PS > 33ms > PE > 37ms > CE
+92ms ║Runtime (39273 bytes) successfully initialized in 33ms (v0.3.110.20191009) (90ms)
+93ms ║╔Execution stage started
+105ms ║║Comparison (enum) off is (string) off = true (1ms)
+106ms ║║Condition #19 evaluated true (9ms)
+107ms ║║Cancelling condition #1’s schedules…
+108ms ║║Condition group #1 evaluated true (state changed) (11ms)
+112ms ║║Comparison (enum) open changes_to (string) open = true (1ms)
+113ms ║║Cancelling condition #2’s schedules…
+114ms ║║Condition #2 evaluated true (5ms)
+115ms ║║Condition group #1 evaluated true (state did not change) (6ms)
+117ms ║║Cancelling statement #3’s schedules…
+130ms ║║Executed physical command [Осветление Стълбище].on() (10ms)
+131ms ║║Executed [Осветление Стълбище].on (12ms)
+134ms ║║Executed virtual command [Осветление Стълбище].wait (1ms)
+135ms ║║Requesting a wake up for Mon, Nov 23 2020 @ 3:25:56 PM EET (in 300.0s)
+170ms ║║Comparison (time) 55256028 is_between (datetime) 1606143480000 … (time) 79200000 = false (6ms)
+172ms ║║Condition #15 evaluated false (33ms)
+173ms ║║Condition group #13 evaluated false (state did not change) (34ms)
+175ms ║╚Execution stage complete. (82ms)
+177ms ║Setting up scheduled job for Mon, Nov 23 2020 @ 3:25:56 PM EET (in 299.96s)
+184ms ╚Event processed successfully (184ms)
DId you change the TCP to NEVER? At 3:21, it looks like the door closed which cancels the WAIT.
This should help in understanding…
To clarify a bit to @Jason_Meudt’s post:
WITH” on line 22
This will force the shutoff to continue… regardless of other circumstances.
