I don’t want no stinking trigger :)

#1

1) Give a description of the problem
I do not want any triggers in the piston. I will call “Execute Piston” when I want it to run. Any way to do this?

2) What is the expected behaviour?
Only execute when I call it

3) What is happening/not happening?
Appears to be subscribing to 2 triggers

**4) Post a Green Snapshot of the piston

image
8C994EE7-CBD8-46C1-9DDE-C72F8AF27416.png1242×2208 262 KB

#2

The easiest way (don’t laugh) is to add an IF at the very bottom like this:

IF $hour24 changes to 25
    Then 
END IF

Yes, that is an empty block, that can never be true… but “changes to” acts like a trigger (removing all of your other lightning bolts)… The icing on the cake is system variables (such as $hour24) will not work as a trigger.

Essentially, as long as your code has only conditions, it forces this up top:

pic
pic.jpg708×58 7.54 KB

#3

Brilliant, just brilliant!

#4

But of coarse, thank you

#5

And this is why we will always win in a battle with the machines…illogical human ingenuity. :smiley:

#6

Hey, who are you calling illogical?!? LOL

I just combined three logical processes into one…

  • Add a trigger to prevent conditions from triggering
  • Make it a system variable to disable that new trigger
  • Make the trigger false 100% of the time

The last one may be optional, but I feel better with it left in.

#7

Couldn’t you just disable event subscriptions in the settings for the piston? That is what I have done in the past for pistons like this.

#8

As with everything webCoRE… There may be a dozen ways to achieve this…

#9

Thanks dude, that is exactly what I was looking for. I hunted around and finally found what you are referring to. After disabling subscriptions in the piston settings the lightning bolts are still there. Perhaps a GUI glitch. I’m not going to bother testing it, nothing is going to trigger those variables anyway.

#10

I did this but I still have lightening bolts in the margin. However, I do see this