You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to connect companion to a Stream Deck XL through a KVM it is not connecting. Have tried directly to the computer and it works, but through KVM it will connect and disconnect continually (does not stay connected for more than a second). Was tested with an older version of Stream Deck XL and worked fine through KVM.
Steps To Reproduce
Stream Deck XL is connected to KVM via USB-C to USB-A.
I have tried using a power supply with the KVM and still got disconnects. I plugged in an older Stream Deck and it worked fine, so I'm assuming it has something to do with the firmware of the stream deck.
They may have changed something in newer firmware, but I'm hoping they haven't as I don't have a recent XL to use to figure out the change.
Could you double check that the streamdeck works if connected directly, instead of via the KVM. Just to rule out that as being an issue.
Is there anything in the companion log about this streamdeck?
Otherwise, yeah it could be something firmware, but I don't know how to debug that right now.
Although someone I work with got a new XL today, and they haven't had issues. Doesn't mean its not a firmware issue though.
Is this a bug in companion itself or a module?
Is there an existing issue for this?
Describe the bug
When trying to connect companion to a Stream Deck XL through a KVM it is not connecting. Have tried directly to the computer and it works, but through KVM it will connect and disconnect continually (does not stay connected for more than a second). Was tested with an older version of Stream Deck XL and worked fine through KVM.
Steps To Reproduce
Stream Deck XL Firmware Version: 2.01.002
Expected Behavior
Stream Deck is expected to connect to Companion without disconnects.
Environment (please complete the following information)
Additional context
No response
The text was updated successfully, but these errors were encountered: