You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe not much of an issue for me or many others, but I have noted that the 50-130% restriction in the automation of Profile percentage applies to both the Condition and the Action.
I understand why it's there in the Actions, limited to between 50% and 130%, for safety reasons. I could argue that this is a bit limiting in some cases, but don't want to debate the safety protocols.
My point is just that much broader restrictions exist for manual Profile percentage changes, from 30% to 250%.
So the Automation should theoretically be able to detect any existing Profile percentage, even if it can't Action it outside the safety range.
It's not stopping me from doing anything I might want to automate, as I could use < or > operators to look for values outside the safety range. It just struck me as an inconsistency that could be easily fixed (I think - not that I can code!)
The text was updated successfully, but these errors were encountered:
Maybe not much of an issue for me or many others, but I have noted that the 50-130% restriction in the automation of Profile percentage applies to both the Condition and the Action.
I understand why it's there in the Actions, limited to between 50% and 130%, for safety reasons. I could argue that this is a bit limiting in some cases, but don't want to debate the safety protocols.
My point is just that much broader restrictions exist for manual Profile percentage changes, from 30% to 250%.
So the Automation should theoretically be able to detect any existing Profile percentage, even if it can't Action it outside the safety range.
It's not stopping me from doing anything I might want to automate, as I could use < or > operators to look for values outside the safety range. It just struck me as an inconsistency that could be easily fixed (I think - not that I can code!)
The text was updated successfully, but these errors were encountered: