Flash Lights on and off when turned off

#1

1) Give a description of the problem
I’ve got a set of Christmas lights that have 8 different patterns that they can run through but I’ve found that when they’re off for a long time, they’ll go to the next pattern when turned back on. I’ve found that you can make it go to the next one if power hasn’t been on for too long, so I thought maybe I could have Webcore cycle back around to the pattern they were left on. They’re plugged into a smart switch (Peanut) and I thought that I could use Webcore to detect when the switch has been off for X amount of time and then flash. But it’s not working. I’m totally new to this so any help would be greatly appreciated.

2) What is the expected behaviour?
After the switch has been off for X time (I have been testing with 2 minutes but will eventually change to something like 12 hours), turn the lights on for 10 seconds and off for 60. Repeat 7 times.

3) What is happening/not happening?
When the switch turns off, the piston executes and turns it back on, but then it stops.

**4) Post a Green Snapshot of the piston!

download
download.png1178×500 51.7 KB

(Side note - I find the code it generated hilarious since apparently that’s what I’m making of this piston)

5) Attach logs after turning logging level to Full
12/2/2019, 2:06:38 PM +86ms
+1ms ╔Received event [Edgewood Office].time = 1575313599271 with a delay of -1185ms
+110ms ║RunTime Analysis CS > 22ms > PS > 80ms > PE > 8ms > CE
+113ms ║Runtime (37604 bytes) successfully initialized in 80ms (v0.3.110.20191009) (111ms)
+113ms ║╔Execution stage started
+114ms ║╚Execution stage complete. (1ms)
+115ms ╚Event processed successfully (115ms)
12/2/2019, 2:06:29 PM +875ms
+2ms ╔Received event [Stephen’s Christmas Lights].switch = on with a delay of 261ms
+119ms ║RunTime Analysis CS > 22ms > PS > 84ms > PE > 13ms > CE
+122ms ║Runtime (37601 bytes) successfully initialized in 84ms (v0.3.110.20191009) (119ms)
+123ms ║╔Execution stage started
+131ms ║║Comparison (enum) on stays (string) off = false (2ms)
+133ms ║║Cancelling any timed trigger schedules for condition 2
+134ms ║║Cancelling statement #2’s schedules…
+135ms ║║Cancelling condition #2’s schedules…
+135ms ║║Condition #2 evaluated false (8ms)
+136ms ║║Cancelling condition #1’s schedules…
+137ms ║║Condition group #1 evaluated false (state changed) (11ms)
+143ms ║╚Execution stage complete. (21ms)
+144ms ╚Event processed successfully (144ms)
12/2/2019, 2:06:29 PM +128ms
+0ms ╔Received event [Edgewood Office].time = 1575313590148 with a delay of -1021ms
+103ms ║RunTime Analysis CS > 29ms > PS > 67ms > PE > 7ms > CE
+105ms ║Runtime (37605 bytes) successfully initialized in 67ms (v0.3.110.20191009) (104ms)
+106ms ║╔Execution stage started
+112ms ║║Cancelling condition #2’s schedules…
+113ms ║║Condition #2 evaluated true (2ms)
+114ms ║║Cancelling condition #1’s schedules…
+115ms ║║Condition group #1 evaluated true (state changed) (3ms)
+117ms ║║Cancelling statement #3’s schedules…
+133ms ║║Executed physical command [Stephen’s Christmas Lights].on() (5ms)
+148ms ║║Executed virtual command [Stephen’s Christmas Lights].flash (25ms)
+149ms ║║Requesting a wake up for Mon, Dec 2 2019 @ 2:14:39 PM EST (in 490.1s)
+156ms ║╚Execution stage complete. (50ms)
+160ms ║Setting up scheduled job for Mon, Dec 2 2019 @ 2:06:39 PM EST (in 9.983s), with 14 more jobs pending
+170ms ╚Event processed successfully (171ms)
12/2/2019, 2:04:29 PM +929ms
+2ms ╔Received event [Stephen’s Christmas Lights].switch = off with a delay of 149ms
+202ms ║RunTime Analysis CS > 23ms > PS > 100ms > PE > 78ms > CE
+204ms ║Runtime (37608 bytes) successfully initialized in 100ms (v0.3.110.20191009) (202ms)
+206ms ║╔Execution stage started
+216ms ║║Comparison (enum) off stays (string) off = true (2ms)
+218ms ║║Adding a timed trigger schedule for condition 2
+221ms ║║Condition #2 evaluated false (10ms)
+222ms ║║Condition group #1 evaluated false (state did not change) (11ms)
+225ms ║╚Execution stage complete. (20ms)
+227ms ║Setting up scheduled job for Mon, Dec 2 2019 @ 2:06:30 PM EST (in 119.993s)
+235ms ╚Event processed successfully (235ms)

#2

Never tried this one before but in this piston you are trying to send a command to an OFF outlet.
I can only guess here and say, try turning it ON first…

#3

I am thinking outside the box here, but why not prevent it from staying off for too long??

Every 3 hours
    Turn on
    Wait 60 seconds
    Turn off
END EVERY

That 3 hours can be tweaked, but ideally, as long as possible where the current setting sticks.
Also…
That 60 secs can be tweaked, but ideally, as short as possible where the current setting sticks.

#4

Hmm that’s an interesting idea. I’d want to add a component to that to not do it when they’re already on but that could work.

#5

Yes, good call.

I would start hours small, and increase until it “forgets”… Then back up a bit.

Same with the seconds… Start large (60?), and lower it until it “forgets”… Then raise it a bit

Once you know the requirements for the setting to stick, then you can build upon that logic.