Not that i‘m currently aware of.
Scenario 1 or current state:
- The trigger item
- A dummy switch that represents if the speedtest should be executed
- A rule that starts by a crown expression and checks the dummy before execution
Scenario 2 - a new Channel:
- A channel linked to a switch item that controls the execution of the speedtest
E.g. configure the Thing to execute every 30 minutes and then control if it‘s executed every 30 minutes or not with the new Channel
The aready existing trigger item isn‘t needed for the second scenario.
It‘s already there and don‘t need to be removed but neither is it needed when there‘s a Channel to control the automated execution.
I‘m fan of things build into the binding instead of working around something in rules.
Same goes for the homematic binding that uses the exact opposit logic for rollershuters compared to the original CCU.
Homematic 100% open / 0% closed
openHAB 100% closed / 0% open
The z-wave binding atleast has an option to invert this, but the homematic binding not.
But that‘s another discussion 