Thanks for the submitting the feature request, @Robert_C – be sure to scroll up to the top of the thread and cast a vote.
And thanks for sharing the clarifying use case. I can see how the delay from the ‘auto off’ on a Hubitat Virtual Switch might not work as well here as you would have to wait to tap between each press.
Hubitat buttons can be authorized to SharpTools and used to trigger SharpTools rules. Historically, buttons were considered sensor devices within Hubitat – meaning they only reported their state when a button was physically actuated. It seems like the concept of virtual buttons as actuators has become more popular in the HE community though, so I can certainly see the use case here!
Workaround: SharpTools Rule
As something of a workaround, you could use a SharpTools rule to run the device commands and add that rule directly to your dashboard. For example, I might create a rule with just a device command in the Flow (no Triggers):
Then in my dashboard, I would directly add the rule as a tile to my dashboard. So each time I tap on that tile, it would send the device command (or multiple device commands if there were multiple in the flow):
Variables in Rules
For the Denon Amp driver, I imagine you might even be able to set the volume to a specific value/level. If so, you could potentially even use a numeric variable on your dashboard and then use that numeric variable changing as the trigger for your rule and as a parameter in the device command in the flow.