I heavily automate my Onyx setup with Bitfocus Companion using the telnet module. The Go To Q command GTQ works with cues without points (ex. 3 instead of 3.4). I’ve tried with the Windows Telnet client and PuTTY, and with the Companion module itself, and point cues cannot be called.
On the Telnet and UDP commands page, it says the Go To Q command works with whole and point cues. I’ve also dug through modules in other languages on Github and noticed that they make sure you’re only passing in an integer.
A successful call:
GTQ 1,2
200 Ok
MxCmd:[0003] GOTO CUE - CueListId:1 CueId:2
An unsuccessful call:
GTQ 1,8.5
200 Ok
MxCmd:[0003] GOTO CUE - CueListId:1 CueId:0
I just updated to the latest release of Onyx (was running 4.32.08xx before) so now testing with Onyx 4.32.1311, Companion 4.2.5, Onyx Telnet module 1.0.5, on an up-to-date Windows 11 box. Same problem persists. Have also tried this on my home computer (same OS and similar specs) and an instance of Companion running on a Mac (M1 Ultra Studio) running on the same LAN as Onyx.
I fat-fingered the command a few times, hence the 400s. Note that it can’t pull the cue ID when a decimal was passed to it (Onyx Manager notes it as CueId: 0), but using a comma instead of a period makes it think there’s an additional argument and it goes to cue 8 (“Sermon” in the screenshot) instead.
I also noticed in your response that you also get a 200 Ok response, but I get that too for incorrect commands like GTQ 1. Can you confirm that Onyx is responding correctly or are you just getting the 200 Ok response?
Same result when using Companion. Sadly, the module is very old and lacks proper logging, so I can’t debug further there, but I am working on an updated Companion module.
Thank you very much for the screenshots. It looks like you are sending Telnet commands to ONYX Manager, rather than ONYX. Please close ONYX Manager, and instead send the Telnet commands directly to ONYX. You should find you can then trigger point cues.
Telnet can be configured in ONYX from Menu > Remote > Telnet.
Ooof. That explains why my command responses have a different syntax than yours. Thanks for pointing me in the right direction.
The current module makes use of the QLActivecommand, which works with Onyx Manager but not Onyx directly. Do you know if there’s any plans to move that command over to Onyx itself?
