Piston used to run all the way through


#1

1) Give a description of the problem
This piston controls my doggy door. It used to run all the way through both the opening and closing sequence, but now no longer does.

2) What is the expected behaviour?
Open routine starts the actuator and piston states that door is opening. When the piston has run for 40 seconds, the piston should state the door is opened and turn off the actuator.

3) What is happening/not happening?
The piston starts the actuator, but then stops there. I’ve had to create additional programming to turn off the piston after a longer wait. I tried setting Cancellation policy to never, but that didn’t help

3/10/2022, 1:42:21 PM +381ms
+3ms ╔Received event [Doggy Door].windowShade = open with a delay of 104ms, canQueue: true, calledMyself: false
+21ms ║RunTime initialize > 21 LockT > 0ms > r9T > 1ms > pistonT > 0ms (first state access 20 3 18)
+27ms ║Runtime (22064 bytes) initialized in 1ms (v0.3.114.20220203_HE)
+28ms ║╔Execution stage started
+197ms ║║Device missing from piston. Loading all from parent (166ms)
+204ms ║║Comparison (time) 49341000 happens_daily_at (time) 24000000 = false (0ms)
+205ms ║║Condition #2 evaluated false (2ms)
+207ms ║║Cancelling statement #2’s schedules…null
+212ms ║║Requesting time schedule wake up at Fri, Mar 11 2022 @ 6:40:00 AM PST
+216ms ║║Condition #3 evaluated false (4ms)
+217ms ║║Condition group #1 evaluated false (state did not change (15ms)
+221ms ║║Comparison (enum) open changes_to (string) open = true (0ms)
+222ms ║║Cancelling condition #11’s schedules…
+223ms ║║Condition #11 evaluated true (4ms)
+224ms ║║Cancelling condition #10’s schedules…
+224ms ║║Condition group #10 evaluated true (state changed (6ms)
+226ms ║║Cancelling statement #12’s schedules…null
+233ms ║║Calculating (string)1:42 P.M. + (string) on >> (string)1:42 P.M. on
+234ms ║║Calculating (string)1:42 P.M. on + (string)Thu, 3/10/2022 >> (string)1:42 P.M. on Thu, 3/10/2022
+236ms ║║Calculating (string)1:42 P.M. on Thu, 3/10/2022 + (string) >> (string)1:42 P.M. on Thu, 3/10/2022
+239ms ║║Executed virtual command setVariable (1ms)
+242ms ║║Calculating (string) The Doggy Door is OPENING at + (string)1:42 P.M. on Thu, 3/10/2022 >> (string) The Doggy Door is OPENING at 1:42 P.M. on Thu, 3/10/2022
+244ms ║║Calculating (string) The Doggy Door is OPENING at 1:42 P.M. on Thu, 3/10/2022 + (string) >> (string) The Doggy Door is OPENING at 1:42 P.M. on Thu, 3/10/2022
+246ms ║║Executed virtual command setVariable (1ms)
+248ms ║║Executed virtual command setState (0ms)
+251ms ║║ The Doggy Door is OPENING at 1:42 P.M. on Thu, 3/10/2022
+253ms ║║Executed virtual command log (2ms)
+255ms ║║Cancelling statement #17’s schedules…null
+417ms ║║Executed physical command [Doggy Door Open Relay].on() (158ms)
+417ms ║║Executed [Doggy Door Open Relay].on (160ms)
+421ms ║║Executed virtual command [Doggy Door Open Relay].wait (0ms)
+422ms ║║Requesting a wake up for Thu, Mar 10 2022 @ 1:43:01 PM PST (in 40000ms)
+428ms ║╚Execution stage complete. (400ms)
+451ms ║Setting up scheduled job for Thu, Mar 10 2022 @ 1:43:01 PM PST (in 40023ms),with 1 more job pending
+453ms ╚Event processed successfully (452ms)


#2

Well, I just set every line to Never Cancel…seems to be working now.