Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
let it update the firmware on the controller
even the new shipped ones have outdated or orig firmware
that has an issue with button mappings
Sorry for replying late btw
Also, should have mentioned but its running on steam link hardware. The box they used to sell.
Official. Specifically, this one.
https://a.co/d/5GuGHE2
USB VID/PID (according to device manager) is
USB\VID_045E&PID_0B12&REV_050?
USB\VID_045E&PID_0B12
First thing I did when i got the controller.
Also, running build 851 on the steam link hardware.
Yep. Did it twice, actually.
Seems like the Bluetooth connection to the Xbox series controller is a problem, probably due to the switch to a Bluetooth LE module whereas the Xbox one s controller has standard Bluetooth.
Hey I also have this issue, although I do not have to re-pair every time. The only problem I'm having is that it will not wake up the steam link without another input device, or being plugged in. My steam link, and controller firmware were updated the day of this post 11/19/2022. Blue tooth pairings were reset on the steam link, restarted, and relinked to no avail.
This issue persists in Build 861
The controller is "Xbox Wireless Controller" Model: 1914. On the steam link shows up as "Xbox Series X Controller"
firmware version for the controller is 5.15.3168.0
Is there potential for this controller to be fully supported, or will this likely be a limitation of the hardware between the steam link and controller model?
I returned the 1914 model controller today, and bought a 1708 to replace it since I already had a 1708 that didn't have any issues with waking up/pairing with the steam link. for simplicity lets refer to my existing 1708 as black, and the new one as blue (that is their colors).
At first I could not pair the new blue controller via bluetooth, so I updated the firmware on it to 5.15.3168.0 (the 1914, and 1708 use the same firmware apparently). once I did that the blue controller will pair with the steam link, but has the same issues with waking up the steam link.
I have found in the time it took me to write this review that on 5.15.3168.0 the controller will wake up the steam link in about 3-5 minutes which is painfully slow.
Meanwhile my black controller had no issues waking up the steam link in a timely manor until today when I updated it to 5.15.3168.0 (I was updating the blue one, so I decided to update the black one as well), and it now has the same problem.
To me this looks to be an issue with the controller firmware on the MS side of things. I'm not sure what the firmware version was on my black controller before the update unfortunately.
From one computer engineer to another, I hope this information helps find a solution.
update: ok, so this controller (model 1708) is also having issues connecting and waking the steam link.
I think its the firmware on the controller. I think whatever microsoft did broke something, because it doesn't seem to want to connect to the steam link sometimes. I thought it was working at first, but after not using the steam link for a few days then picking it back up again, i wasn't able to get the controller to connect without hard-resetting the steam link (pulling the plug for 10 seconds then plugging it back in). After that it would connect to the steam link, but it took a bit to do so. Also, it doesn't seem to wake the steam link anymore. I mean it technically does, but its picky about it. sometimes it will, sometimes it won't.
Not sure if it's something valve can fix on their end through a software update or if its something microsoft has to fix via a controller firmware update.