Here is the log…
This one didn’t even fire this morning at 5.00am
At 5.00am the variable had to become 2 but right now (6.15am) still reads ZERO
Last time was last evening…
Using multiple TRIGGERS in single IF
there you go…
Since I was focusing on why it did not work at 5.00 am i forgot about the other parts of the piston:)))))
Same thing happened again…
At 7.00am @mainentrancephases had to be “0”
Piston ran but nothing changed…
Here is the log for 6.59AM
10/31/2018, 6:59:59 AM +333ms
+1ms ╔Received event [Home].time = 1541005200000 with a delay of -667ms
+208ms ║RunTime Analysis CS > 58ms > PS > 85ms > PE > 64ms > CE
+210ms ║Runtime (44714 bytes) successfully initialized in 85ms (v0.3.108.20180906) (208ms)
+212ms ║╔Execution stage started
+223ms ║║Comparison (time) 25199552 happens_daily_at (time) 25200000 = true (0ms)
+224ms ║║Time restriction check passed
+226ms ║║Cancelling condition #2’s schedules…
+227ms ║║Condition #2 evaluated true (8ms)
+229ms ║║Cancelling statement #2’s schedules…
+235ms ║║Requesting time schedule wake up at Thu, Nov 1 2018 @ 7:00:00 AM HST
+239ms ║║Cancelling condition #1’s schedules…
+241ms ║║Condition group #1 evaluated true (state changed) (22ms)
+244ms ║║Cancelling statement #5’s schedules…
+250ms ║║Executed virtual command setVariable (1ms)
+294ms ║║Comparison (time) 25199588 happens_daily_at (time) 1541044860000 = false (1ms)
+296ms ║║Condition #8 evaluated false (42ms)
+318ms ║║Cancelling statement #8’s schedules…
+328ms ║║Requesting time schedule wake up at Wed, Oct 31 2018 @ 5:01:00 PM HST
+332ms ║║Condition group #7 evaluated false (state did not change) (78ms)
+341ms ║║Comparison (time) 25199670 happens_daily_at (time) 18000000 = false (1ms)
+344ms ║║Condition #12 evaluated false (6ms)
+346ms ║║Cancelling statement #12’s schedules…
+351ms ║║Requesting time schedule wake up at Thu, Nov 1 2018 @ 5:00:00 AM HST
+355ms ║║Condition group #11 evaluated false (state did not change) (18ms)
+368ms ║║Condition #16 evaluated false (8ms)
+369ms ║║Condition group #15 evaluated false (state did not change) (11ms)
+375ms ║╚Execution stage complete. (163ms)
+378ms ║Setting up scheduled job for Wed, Oct 31 2018 @ 5:01:00 PM HST (in 36060.29s), with 2 more jobs pending
+387ms ╚Event processed successfully (387ms)
This looks like the variable was set to ‘0’ at 7am. Can you confirm that the global changed correctly? If so, then the focus should be on the other piston that is monitoring that global.
They always show for me… I wonder if it depends on which browser you are using…
(as long as they are there as triggers, all is good, but triggers are one of the important things I look at when troubleshooting a piston)
I tested with SWITCH and global variables do change.
I tested with changing another global variable @movieroomphases and it worked.
What doesn’t work is HAPPENS DAILY AT
There have been some strange occurances with the various timers I have seen as of late. I am still working on identifying the strengths and weaknesses for each of them before making a detailed post for reference.
In the meantime, you could remove the line referring to the time, and make a new block:
Every day at 7am
Do
Set variable to 0
End Every
if you mean TIMER,
I just did
AND IT WORKED…
nice
WCmore to the rescue one more time:)
now I am just curious why HAPPENS DAILY AT is not working?
Well, it works in a block by itself, or else your 5am and sunset blocks would not be working. I will shoot you a message when I have enough data gathered to make a proper post for reference.
those also did not work:)))
at 5am it did not change…
I am not sure about the sunset but I will test it tonight.
Ahh, then perhaps using the Timer is the solution for those blocks as well…
I cannot remember the last time I put a time statement as a trigger in an IF block.
I usually do this instead:
(although I may place conditions in the next line or two)
Happens Daily, doesn't
Changed everything to timers as you suggested…
So far, 1hours to sunset worked perfectly…
UPDATE;
7.00 am also worked:)))