Yes, that’s what I meant with “except transmitting that switch on a different channel a 2nd time”. I did that in the past, but I only have 16 channels and I’m using 15 already…
I just looked into that, one minor question (before even having tried it yet):
I understand it can only set low/high/toggle (?) as parameter? If I could set a pulsewidth as input, it could also e.g. set the transmit power for Smart Audio, based on e.g. RSSI level in future…(?)
That might be possible. The trouble I see though is that scripts can’t currently directly read the pwm input. Script can’ read a “button’s” state (e.g. on or off) and a button can be setup to switch on or off based on the pwm value… but scripts can’t read the underlying pwm value going into the “button”.