1) Give a description of the problem
Switch activated twice, yet piston only seems to fire once.
2) What is the expected behavior?
Switch should activate once at 9AM and then not again until 30 mins before sunset.
3) What is happening/not happening?
I have setup a piston to open some curtains at 9AM and then close them again at 30 mins before sunset. Curtain movement is triggered by a fibaro FGS-222 relay turning on. The relay is programmed to auto turn off after 5 seconds. At the programmed time the relay turns on and the curtains open. The problem is that on some days about a minute later the relay turns on again and closes them. This had been working flawlessly for months when this issue started to happen so I re-wrote the piston from scratch to use timers instead if firing “if time is x”. I have not seen any change though.
**4) Post a Green Snapshot of the piston![image|45x37]
5) Attach any logs (From ST IDE and by turning logging level to Full)
( 20/04/2019, 09:01:35 +672ms
+1ms ╔Received event [Home 2].time = 1555747200000 with a delay of 95672ms
+462ms ║RunTime Analysis CS > 240ms > PS > 184ms > PE > 37ms > CE
+465ms ║Runtime (40360 bytes) successfully initialized in 184ms (v0.3.10a.20190223) (462ms)
+466ms ║╔Execution stage started
+468ms ║╚Execution stage complete. (3ms)
+471ms ║Setting up scheduled job for Sat, Apr 20 2019 @ 7:03:00 PM BST (in 36083.858s), with 2 more jobs pending
+482ms ╚Event processed successfully (482ms)
20/04/2019, 09:01:07 +246ms
+1ms ╔Received event [Home 2].execute = recovery with a delay of 61ms
+95ms ║RunTime Analysis CS > 20ms > PS > 39ms > PE > 36ms > CE
+98ms ║Runtime (40351 bytes) successfully initialized in 39ms (v0.3.10a.20190223) (96ms)
+99ms ║╔Execution stage started
+120ms ║║Condition #16 evaluated false (7ms)
+121ms ║║Condition group #15 evaluated false (state did not change) (9ms)
+124ms ║╚Execution stage complete. (25ms)
+127ms ║Setting up scheduled job for Sat, Apr 20 2019 @ 7:03:00 PM BST (in 36112.628s), with 2 more jobs pending
+138ms ╚Event processed successfully (138ms)
20/04/2019, 09:00:52 +757ms
+1ms ╔Received event [Home 2].time/recovery = 1555747252756 with a delay of 1ms
+453ms ║RunTime Analysis CS > 243ms > PS > 166ms > PE > 43ms > CE
+455ms ║Runtime (40365 bytes) successfully initialized in 166ms (v0.3.10a.20190223) (453ms)
+457ms ║╔Execution stage started
+482ms ║║Comparison (boolean) true is (boolean) true = true (3ms)
+484ms ║║Condition #3 evaluated true (9ms)
+486ms ║║Condition group #2 evaluated true (state did not change) (10ms)
+489ms ║║Cancelling statement #6's schedules...
+14322ms ║║Executed physical command [Lounge Curtain Motor].on() (13828ms)
+14323ms ║║Executed [Lounge Curtain Motor].on (13831ms)
+14328ms ║╚Execution stage complete. (13871ms)
+14331ms ║Setting up scheduled job for Sat, Apr 20 2019 @ 7:03:00 PM BST (in 36112.913s), with 2 more jobs pending
+14341ms ╚Event processed successfully (14341ms)
20/04/2019, 09:00:55 +727ms
+1ms ╔Received event [Home 2].execute = recovery with a delay of 56ms
+7357ms ║RunTime Analysis CS > 17ms > PS > 7303ms > PE > 36ms > CE
+7358ms ║Piston waited at a semaphore for 7262ms
+7360ms ║Runtime (40426 bytes) successfully initialized in 7303ms (v0.3.10a.20190223) (7358ms)
+7361ms ║╔Execution stage started
+7382ms ║║Condition #16 evaluated false (7ms)
+7384ms ║║Condition group #15 evaluated false (state did not change) (9ms)
+7386ms ║╚Execution stage complete. (25ms)
+7389ms ║Setting up scheduled job for Sat, Apr 20 2019 @ 9:00:00 AM BST (in 1s), with 2 more jobs pending
+7398ms ╚Event processed successfully (7398ms)
Here is the ST event log for the device.
My thoughts are that this may have something to do with the last section starting and the large delay of 95672ms ?
Any help appreciated.