1) Give a description of the problem
I have a simple (first) piston, which checks movement on 2 sensors (either) AND if between sunset & sunrise, turns on 2 lights.
2) What is the expected behavior?
Lights come on during the period between Sunset & Sunrise, but then do not trigger until the sunset for the day
3) What is happening/not happening?
Last night, no trigger before sunset as expected, then turned on after sunset - all fine. But this morning, the lights are still coming on well after sunrise (3 hours later)
4) Post a Green Snapshot of the piston
5) Attach any logs (From ST IDE and by turning logging level to Full)
3/28/2018, 10:26:40 AM +470ms
+1ms ╔Received event [Sensor - Ground Floor].motion = active with a delay of 119ms
+80ms ║RunTime Analysis CS > 13ms > PS > 39ms > PE > 29ms > CE
+83ms ║Runtime (38611 bytes) successfully initialized in 39ms (v0.3.104.20180323) (81ms)
+83ms ║╔Execution stage started
+95ms ║║Comparison (enum) active changes_to (string) active = true (0ms)
+96ms ║║Cancelling condition #9’s schedules…
+97ms ║║Condition #9 evaluated true (9ms)
+117ms ║║Comparison (datetime) 1522229200567 is_between (datetime) 1522261680000 … (datetime) 1522216080000 = false (2ms)
+119ms ║║Condition #32 evaluated false (22ms)
+120ms ║║Condition group #3 evaluated false (state did not change) (31ms)
+127ms ║║Comparison (enum) inactive is (string) inactive = true (2ms)
+128ms ║║Condition #21 evaluated true (6ms)
+132ms ║║Comparison (enum) active is (string) inactive = false (1ms)
+133ms ║║Cancelling condition #24’s schedules…
+133ms ║║Condition #24 evaluated false (5ms)
+134ms ║║Cancelling condition #15’s schedules…
+135ms ║║Condition group #15 evaluated false (state changed) (14ms)
+137ms ║╚Execution stage complete. (54ms)
+138ms ╚Event processed successfully (138ms)
REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.
