Light not turning off with timer

#1

1) Give a description of the problem
I have a piston to basically turn off the dining room light after 60 minutes. It runs, counts down, sends the signal but doesn’t turn it off.

2) What is the expected behavior?
Signal is sent and light turns off

3) What is happening/not happening?
Light is not receiving the signal somehow? I can turn it off via the switch, google home, the ST app, alexa, etc but not via this piston…

I’ve adjusted the time here to 2 minutes to run a new fresh log for you guys

4) Post a Green Snapshot of the pistonimage

image
image.png1178×630 29.9 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
5/22/2018, 9:52:06 PM +65ms
+0ms ╔Received event [Home].time = 1527047527562 with a delay of -1497ms
+130ms ║RunTime Analysis CS > 19ms > PS > 45ms > PE > 66ms > CE
+133ms ║Runtime (37383 bytes) successfully initialized in 45ms (v0.3.104.20180323) (132ms)
+134ms ║╔Execution stage started
+135ms ║╚Execution stage complete. (1ms)
+136ms ╚Event processed successfully (136ms)
5/22/2018, 9:50:07 PM +615ms
+0ms ╔Starting piston… (v0.3.104.20180323)
+586ms ║╔Subscribing to devices…
+594ms ║║Subscribing to Dining Room Lights.switch…
+797ms ║╚Finished subscribing (220ms)
+825ms ║Comparison (enum) on is (string) on = true (2ms)
+835ms ║Comparison (enum) on is (string) on = true (1ms)
+836ms ║Cancelling condition #10’s schedules…
+837ms ║Cancelling condition #8’s schedules…
+844ms ╚Piston successfully started (844ms)
5/22/2018, 9:50:07 PM +419ms
+2ms ╔Received event [Dining Room Lights].switch = on with a delay of 152ms
+125ms ║RunTime Analysis CS > 29ms > PS > 53ms > PE > 42ms > CE
+127ms ║Runtime (37391 bytes) successfully initialized in 53ms (v0.3.104.20180323) (123ms)
+127ms ║╔Execution stage started
+135ms ║║Comparison (enum) on is (string) on = true (1ms)
+136ms ║║Cancelling condition #5’s schedules…
+136ms ║║Condition #5 evaluated true (5ms)
+137ms ║║Cancelling condition #1’s schedules…
+138ms ║║Condition group #1 evaluated true (state changed) (7ms)
+139ms ║║Cancelling statement #6’s schedules…
+142ms ║║Executed virtual command wait (1ms)
+143ms ║║Requesting a wake up for Tue, May 22 2018 @ 9:52:07 PM MDT (in 120.0s)
+146ms ║╚Execution stage complete. (19ms)
+147ms ║Setting up scheduled job for Tue, May 22 2018 @ 9:52:07 PM MDT (in 119.996s)
+155ms ╚Event processed successfully (155ms)

#2

I am not at a PC right now, but why not something like this:

IF Switch 2 changes to on
THEN
WITH Switch 2
Wait 15 seconds <-- for testing purposes
Turn off

#3

How about.

IF
Switch 2 is on.
THEN
WITH
Switch 2.
DO
Wait 60 minutes.
Turn off.

#4

I originally had that, bobbles. But same problem… Here’s the log

5/23/2018, 6:44:03 AM +76ms
+0ms ╔Received event [Home].time = 1527079444818 with a delay of -1743ms
+110ms ║RunTime Analysis CS > 17ms > PS > 41ms > PE > 52ms > CE
+112ms ║Runtime (36804 bytes) successfully initialized in 41ms (v0.3.104.20180323) (111ms)
+113ms ║╔Execution stage started
+113ms ║╚Execution stage complete. (1ms)
+115ms ╚Event processed successfully (115ms)
5/23/2018, 6:42:04 AM +895ms
+1ms ╔Starting piston… (v0.3.104.20180323)
+322ms ║╔Subscribing to devices…
+326ms ║║Subscribing to Dining Room Lights.switch…
+502ms ║╚Finished subscribing (191ms)
+535ms ║Comparison (enum) on is (string) on = true (1ms)
+542ms ╚Piston successfully started (541ms)
5/23/2018, 6:42:04 AM +710ms
+1ms ╔Received event [Dining Room Lights].switch = on with a delay of 79ms
+88ms ║RunTime Analysis CS > 12ms > PS > 33ms > PE > 43ms > CE
+90ms ║Runtime (36808 bytes) successfully initialized in 33ms (v0.3.104.20180323) (89ms)
+91ms ║╔Execution stage started
+98ms ║║Comparison (enum) on is (string) on = true (1ms)
+99ms ║║Cancelling condition #5’s schedules…
+100ms ║║Condition #5 evaluated true (5ms)
+100ms ║║Cancelling condition #1’s schedules…
+101ms ║║Condition group #1 evaluated true (state changed) (6ms)
+103ms ║║Cancelling statement #6’s schedules…
+106ms ║║Executed virtual command [Dining Room Lights].wait (0ms)
+107ms ║║Requesting a wake up for Wed, May 23 2018 @ 6:44:04 AM MDT (in 120.0s)
+111ms ║╚Execution stage complete. (20ms)
+112ms ║Setting up scheduled job for Wed, May 23 2018 @ 6:44:04 AM MDT (in 119.997s)
+122ms ╚Event processed successfully (122ms)

(I changed it to 2 minutes for the sake of testing)

#5

and like I said, it works when being turned off any other way.

It uses the same zwave relay that I use many other places and all of them work on automation, but the dining room lights are not turning off… for some reason…

#6

Is your piston paused by another piston? Odd that it always has a “starting piston” trigger at the same time it receives an ‘on’ report from your switch.

#7

It’s probably because I was in the piston and hit save to come out?

Nothing else touches this piston

cannot get this to work