Helix Stadium - macOS unexpected keyboard interactions

[zscientist2002]

I use Karabiner Elements (a keyboard key mapping utility) on macOS to modify key mappings on an external keyboard when my macbook is docked at my desk. The keyboard is connected to a hub (CalDigit TS4+), which is then connected to my macbook by a single TB4 cable.

When connecting the Stadium to my macbook via a USB-C cable through one of the ports on the CalDigit hub, the Helix is recognized as a keyboard by macOS and Karabiner. As a result, some of my mappings break and there are intermittent issues with my keyboard's keystrokes not registering (cuts in and out randomly every 15-30 seconds). The Stadium appears as an audio interface in the Audio Midi Setup utility, but is also detected and treated as a keyboard/HID which is causing some issues. 

Not sure if this is a bandwidth issue/limitation cause by how macOS handles USB ports through hubs, but I wanted to see if there is a relatively simple workaround to prevent the Stadium from being recognized/treated as a keyboard to avoid the problems altogether. 

[jpdennis]

On 12/26/2025 at 11:02 AM, zscientist2002 said:

I use Karabiner Elements (a keyboard key mapping utility) on macOS to modify key mappings on an external keyboard when my macbook is docked at my desk. The keyboard is connected to a hub (CalDigit TS4+), which is then connected to my macbook by a single TB4 cable.

When connecting the Stadium to my macbook via a USB-C cable through one of the ports on the CalDigit hub, the Helix is recognized as a keyboard by macOS and Karabiner. As a result, some of my mappings break and there are intermittent issues with my keyboard's keystrokes not registering (cuts in and out randomly every 15-30 seconds). The Stadium appears as an audio interface in the Audio Midi Setup utility, but is also detected and treated as a keyboard/HID which is causing some issues. 

Not sure if this is a bandwidth issue/limitation cause by how macOS handles USB ports through hubs, but I wanted to see if there is a relatively simple workaround to prevent the Stadium from being recognized/treated as a keyboard to avoid the problems altogether. 

Forgive me if you've already attempted this.

 

Have you looked into the control permissions in

System Settings -> Privacy & Security using the "allow accessories to connect" feature?  We used to use this at work for cameras, microphones, etc. so we could limit their use to a specific app.  It was a little painful when non-Apple devices had to be allowed for one app and then denied for all others.  I do not recall the terminal command, however, I realize you are asking for a "relatively simple workaround".  

 

Any high-level Mac experts out there?

 

jpd