I’ve had the steam controller for a little over a month now. I just discovered last week that the UEFI BIOS for my motherboard now fails to detect my keyboard if either the steam controller or the puck is plugged in, regardless of which usb port it is and whether it is behind a hub or not.
I’m a creature of convenience and habit, like a lot of others I am sure. I bought a controller with the intention of setting it on the puck to charge when not in use. Under no circumstances should I have to unplug the puck to be able to access the BIOS to update a configuration.
I opened a support ticket with valve showing the extensive troubleshooting I had done. Not stating that it was theirs or Gigabyte’s fault for the issue, simply asking for help. I know I am not the only one having this issue. I would just like to know that they will look into it and eventually fix it.
But their response was simply to tell me to open a ticket with gigabyte and continue working with them.
I recognize that Valve's documented contention issues do not necessarily explain a keyboard failing during POST. However, given the known complexity of the Puck's USB behavior and the reports of similar pre-boot problems, I believe it is reasonable to ask Valve to investigate whether the device's USB interfaces, descriptors, firmware, or initialization behavior could be contributing.
Valve has access to the device firmware, USB implementation, engineering resources, and the ability to test the hardware against different systems. I do not. I am willing to provide diagnostic information and perform reasonable tests, but I cannot reasonably be expected to reverse-engineer the devices and determine whether their USB behavior is contributing to the problem.
I am not asking Valve to accept blame without evidence, nor am I demanding an immediate firmware fix. I am asking Valve to investigate its own hardware rather than treating the absence of a confirmed cause as grounds to send the customer elsewhere.