Piston was working correctly and now is not HELP. :)


#1

1) Give a description of the problem
The piston was operating correctly turning Christmas lights on at sunset but now is not for the last few days. I’m not sure where it is hiccuping. I don’t understand the correlation between the Log Lines noted and the code lines.
2) What is the expected behavior?
Turn on all Christmas lights including the tree if the wife or I am home at sunset. If neither of us is home then turn on everything except the firestarter (aka Christmas tree).

3) What is happening/not happening?
Shutdown at 11:13PM seems to work. Last year the turning on and off of the tree worked upon departure and arrival. Up until the last ST update everything seemed to come on at sunset as it should have. The only exception being the tree because we didn’t get it up till Monday night I believe.

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

5) Attach any logs (From ST IDE and by turning logging level to Full)

12/18/2018, 5:25:59 PM +141ms
+1ms ╔Received event [Home].time = 1545175560000 with a delay of -860ms
+182ms ║RunTime Analysis CS > 45ms > PS > 52ms > PE > 85ms > CE
+186ms ║Runtime (51911 bytes) successfully initialized in 52ms (v0.3.109.20181207) (183ms)
+188ms ║╔Execution stage started
+206ms ║║Comparison (dynamic) true is (boolean) true = true (3ms)
+209ms ║║Condition #55 evaluated true (12ms)
+211ms ║║Condition group #null evaluated true (state did not change) (15ms)
+234ms ║║Comparison (time) 62759357 is_between (time) 28740000 … (time) 81000000 = true (15ms)
+266ms ║║Time restriction check failed
+269ms ║║Condition #88 evaluated false (53ms)
+287ms ║║Comparison (time) 62759412 is_between (time) 28740000 … (time) 81000000 = true (13ms)
+311ms ║║Time restriction check failed
+314ms ║║Condition #89 evaluated false (43ms)
+315ms ║║Condition group #83 evaluated false (state did not change) (101ms)
+324ms ║║Comparison (time) 62759462 is_any = true (1ms)
+326ms ║║Time restriction check passed
+328ms ║║Condition #91 evaluated true (8ms)
+330ms ║║Cancelling condition #70’s schedules…
+332ms ║║Condition group #70 evaluated true (state changed) (12ms)
+346ms ║║Condition #73 evaluated false (12ms)
+366ms ║║Comparison (enum) present is (string) not present = false (2ms)
+368ms ║║Condition #90 evaluated false (21ms)
+370ms ║║Cancelling condition #70’s schedules…
+372ms ║║Condition group #70 evaluated false (state changed) (38ms)
+391ms ║║Comparison (time) 62759517 is_between (time) 28800000 … (time) 81000000 = true (12ms)
+393ms ║║Time restriction check failed
+395ms ║║Condition #77 evaluated false (20ms)
+412ms ║║Comparison (time) 62759538 is_between (time) 28800000 … (time) 81000000 = true (11ms)
+414ms ║║Time restriction check failed
+416ms ║║Condition #78 evaluated false (19ms)
+432ms ║║Comparison (time) 62759558 is_between (time) 28800000 … (time) 81000000 = true (12ms)
+434ms ║║Time restriction check failed
+437ms ║║Condition #79 evaluated false (19ms)
+505ms ║║Comparison (time) 62759579 is_between (time) 1545175620000 … (time) 81000000 = false (14ms)
+507ms ║║Condition #80 evaluated false (69ms)
+509ms ║║Condition group #66 evaluated false (state did not change) (133ms)
+530ms ║║Comparison (time) 62759654 is_between (time) 1545175620000 … (time) 81000000 = false (13ms)
+532ms ║║Condition #100 evaluated false (20ms)
+533ms ║║Condition group #57 evaluated false (state did not change) (21ms)
+540ms ║║Comparison (time) 62759678 happens_daily_at (time) 83580000 = false (1ms)
+542ms ║║Condition #102 evaluated false (5ms)
+543ms ║║Cancelling statement #102’s schedules…
+548ms ║║Requesting time schedule wake up at Tue, Dec 18 2018 @ 11:13:00 PM CST
+551ms ║║Condition group #101 evaluated false (state did not change) (14ms)
+554ms ║╚Execution stage complete. (367ms)
+556ms ║Setting up scheduled job for Tue, Dec 18 2018 @ 11:13:00 PM CST (in 20820.304s)
+565ms ╚Event processed successfully (565ms)


#2

I am not a coder or an expert so I wouldn’t be able to tell what’s going on with ST updates etc.
I am just going to recommend a test. One of my pistons had similar triggers and as your piston it stopped working …I wrote a new version saying the same thing but with a different design…

1 - Somehow Everyday At Sunset started giving me problems and I changed it to Every Day At 6.00pm
2 - And if this was my piston - just to test it - I would combine lines 32 and 34
IF time is between this and that only these days…
3 - I had a very very simple piston stopped working after a year. As simple as walk in to a room, lights are ON,
no motion for 3 minutes lights are OFF
it stopped working and all I did was delete the piston, re-write it - exactly the same way - and started working.

just some ideas…


#3

Sooooo…you turned it off and on again. :wink:


#4

Did this start working again? Everything looks like it should work. Not sure where 11:13PM comes in since your code specified 10:30PM but that is up to you.


#5

DAMN “IT” response. :stuck_out_tongue: LOL!!!


#6

WOW I just looked at the “green” version and that’s not what the piston looks like…


#7

Sorry guys, I’m not sure what happened but I now have uploaded the correct “Green” shot of the piston. Also, today the weirdest thing happened. Right before the piston fired the lights correctly, I was home alone and ST turned off ALL the lights, armed the alarm and set off the alarm because my front door was open. I opened the app and it showed my phone “present”, the alarm “armed” but no alarm detected that needed to be cleared.


#8

If you’ve got all the bells and whistles turned on (Show True/False, Variables, etc.), then any unused parts will be removed for the snapshot.


#9

So this isn’t the only piston not working correctly now. And it has all been since they did the update last week.