This probably is just getting immediately overridden by the TO.OSC messages Ansible is sending. I don’t know that there’s a way around this, would maybe need something like TO.OSC.OFF that behaves kind of like JF.SHIFT.
This should work, Ansible is sending TO.ENV n 1 when the gate goes high and TO.ENV n 0 when it goes low.
No, this would be cool but I already felt the velocity / duration relationship was slightly strained. Open to suggestions here, the duration alt parameter seems like one possibility though I’m hesitant about the best option for a whole UI page (and am not sure about the memory / flash requirements of an additional parameter).