Turn off TWO things doesn't

#1

1) Give a description of the problem
Shed WLED Off piston will not turn off at proper time.

2) What is the expected behaviour?
20 minutes before sunset, Garage WLED On and Shed WLED On pistons turn on. 11:00pm, Garage WLED Off and Shed WLED Off pistons turn off.

3) What is happening/not happening?
Both pistons turned on, only Garage turned off. The Garage piston has the proper log of turning on and turning off at the proper times. The Shed has the proper log of turning on, and has nothing at the turn-off time.

4) Post a Green Snapshot of the pistonimage

bothonoff
bothonoff.png1178×491 56.2 KB

5) Attach logs after turning logging level to Full
10/23/2020, 10:59:59 PM +153ms
+1ms ╔Received event [Home].time = 1603508400000 with a delay of -847ms
+105ms ║RunTime Analysis CS > 29ms > PS > 55ms > PE > 21ms > CE
+108ms ║Runtime (38058 bytes) successfully initialized in 55ms (v0.3.110.20191009) (105ms)
+109ms ║╔Execution stage started
+125ms ║║Cancelling statement #6’s schedules…
+139ms ║║Executed virtual command executePiston (10ms)
+154ms ║║Executed virtual command executePiston (10ms)
+157ms ║╚Execution stage complete. (49ms)
+159ms ║Setting up scheduled job for Sat, Oct 24 2020 @ 5:32:00 PM EDT (in 66720.688s), with 1 more job pending
+165ms ╚Event processed successfully (165ms)
10/23/2020, 5:31:59 PM +59ms
+1ms ╔Received event [Home].time = 1603488720000 with a delay of -941ms
+64ms ║RunTime Analysis CS > 23ms > PS > 32ms > PE > 8ms > CE
+66ms ║Runtime (38056 bytes) successfully initialized in 32ms (v0.3.110.20191009) (65ms)
+67ms ║╔Execution stage started
+96ms ║║Cancelling statement #2’s schedules…
+107ms ║║Executed virtual command executePiston (7ms)
+119ms ║║Executed virtual command executePiston (6ms)
+123ms ║╚Execution stage complete. (55ms)
+126ms ║Setting up scheduled job for Fri, Oct 23 2020 @ 11:00:00 PM EDT (in 19680.816s), with 1 more job pending
+138ms ╚Event processed successfully (137ms)

#2

This log shows both pistons were executed by this piston. Not much to diagnose here. Did you have logging set to full for both pistons being called so we can see they are receiving the execute command?

#3

Normally, it is wise to avoid executing two pistons simultaneously…
Maybe add an appropriate length WAIT + 2 seconds in between the commands?
(making sure the first piston has enough time to run top to bottom before the second piston starts)

#4

I’ll bet that’s what’s going on. The turn ON works just fine, oddly enough, but maybe that’s luck.

There IS no log for the turn-off for the Shed. Yet the test works fine. I’ll add a delay and see what happens tonight.

#5

Tried 2 seconds - no good. Upped it to 10 seconds, we’ll see what happens tonight.

#6

So what happens if you reverse the order of the two ‘off’ pistons?

#7

Haha I thought of that! I’m going to try the 10 seconds tonight, then if not I’ll try reversing them for tomorrow night.

#8

Just to clarify… My suggestion was to take the total duration of piston “Garage WLED On”, and adding a few extra seconds… and placing that WAIT in piston “77og”… in between the two commands.

(and using the same concept on the Off pistons)

#9

I went ten seconds Wait time last night - Shed didn’t turn off - BUT - there were entries in the log:

10/24/2020, 11:02:37 PM +524ms
+1ms ╔Received event [Home].time = 1603594948882 with a delay of 8642ms
+77ms ║RunTime Analysis CS > 21ms > PS > 40ms > PE > 16ms > CE
+79ms ║Runtime (36580 bytes) successfully initialized in 40ms (v0.3.110.20191009) (77ms)
+80ms ║╔Execution stage started
+81ms ║╚Execution stage complete. (1ms)
+82ms ╚Event processed successfully (82ms)
10/24/2020, 11:02:09 PM +111ms
+0ms ╔Received event [Home].wc_async_reply = httpRequest with a delay of 0ms
+80ms ║RunTime Analysis CS > 23ms > PS > 43ms > PE > 14ms > CE
+83ms ║Runtime (36585 bytes) successfully initialized in 43ms (v0.3.110.20191009) (81ms)
+83ms ║╔Execution stage started
+89ms ║╚Execution stage complete. (6ms)
+90ms ╚Event processed successfully (90ms)
10/24/2020, 11:02:08 PM +785ms
+0ms ╔Received event [Home].test = 1603594928785 with a delay of 1ms
+61ms ║RunTime Analysis CS > 18ms > PS > 30ms > PE > 13ms > CE
+64ms ║Runtime (36577 bytes) successfully initialized in 30ms (v0.3.110.20191009) (62ms)
+65ms ║╔Execution stage started
+70ms ║║Cancelling statement #1's schedules...
+92ms ║║Sending internal web request to: 10.69.0.205/json/state
+95ms ║║Executed virtual command httpRequest (17ms)
+96ms ║║Requesting a wake up for Sat, Oct 24 2020 @ 11:02:28 PM EDT (in 20.0s)
+113ms ║╚Execution stage complete. (49ms)
+120ms ║Setting up scheduled job for Sat, Oct 24 2020 @ 11:02:28 PM EDT (in 19.978s)
+127ms ╚Event processed successfully (127ms)
#10

The Test button will not do anything with the piston above…
(it only fires at the times specified)

#11

I assume that is the Shed WLED Off log? That is showing you the results of pressing the ‘Test’ button three nights ago. First the piston runs in response to the Test button being pressed, makes a local web request, and schedules a wake up in twenty seconds as a timeout. A second later the web response comes back and is processed, but there doesn’t seem to be anything for it to do, and then about about twenty-eight seconds later the piston is woken up (about eight seconds late) as scheduled but there is nothing for it to do.

The lack of logging information makes me wonder if the piston has been paused without you noticing.

#12

Nope, checked - not paused. And switching them for last night did not help. Sigh.