Quote from: patrike on April 04, 2023, 06:53:32 AM

Quote from: bensam1231 on April 03, 2023, 02:40:45 AM

Quote from: patrike on March 30, 2023, 01:43:35 PM

Quote from: bensam1231 on March 29, 2023, 02:18:11 PM

Aye... Thanks.

Errr... I don't think the variable change thing really solves the original problem. The problem was it would constantly trigger if conditions were met, not only once when they're first met.

So I have two different variables, and a rule that triggers turning miners off if one variable is true. Then I have another rule when both variables are false that turns things back on. However, if it's setup normally the miners will keep resetting (turning off) as long as one of the variables is true and with the 'detect change' wont be able to know the correct state that both need to be in to turn things back on.

Thanks for the feedback.

If I understand correctly, your rules looks something like this today.
Rule#1: If Var1=true or Var2=true -> Stop miners
Rule#2: If Var1=false and Var2=false -> Start miners

Do you think this concept could work?
Rule#1: If Var1=true or Var2=true -> Set Var3=true
Rule#2: If Var1=false and Var2=false -> Set Var3=false
Rule#3: If Var3=true and Var3 has changed -> Stop miners
Rule#4: If Var3=false and Var3 has changed -> Start miners

This way the actions for Rule#3 and #4 should only run once.

This does work, I feel as though the 'detect change' or 'comparison' should instead be checkboxes, instead of radial buttons and could eliminate this, while being more intuitive and simplistic. So it could do both in one or either/or.

I don't know if you can do anything about the rulespam, but the comparison activates every 6s and keeps hitting the logs, which buries anything of value.

Thanks for the feedback.

Is it entries in the Awesome Miner log file you are referring to? I did find a few related to triggers but not many. Can you give an example and I will look into it in more detail? Thanks!

Tools > Rule History

Maybe it's not a normal log that gets saved, however with variable triggers it only keeps about a hour worth of data before it gets pushed out due to the variable activating every 6s.