Steam Controller

Steam Controller

TeeSeal 9 ABR 2019 a las 13:36
Switch Pro Controller won't reconnect through bluetooth
Recently bought myself a Nintendo Switch Pro Controller for use with my switch and PC. When I tried playing on PC the first time I paired it through bluetooth, windows started "setting it up", steam quickly detected it and everything went fine.

However after turning off the controller/PC and attempting to reconnect later, it never does. While the controller attempts to reconnect the steam client freezes, and only unfreezes when the controller gives up (the controller does appear as "connected" during this period in the control panel). Even worse, if I attempt to reconnect the controller while in big picture mode, it causes steam to crash completely.

Connecting through USB works fine. Also I have a PS4 controller that connects and reconnects through bluetooth alright as well.

Never had any kind of wonky controller driver software, just plain steam.

Right now, whenever I want to use the Procon, I have to delete it from the devices in the control panel and re-pair it with my PC, as that's the only time steam seems to interface with it properly.
< >
Mostrando 16-30 de 142 comentarios
Pancakes 2 AGO 2021 a las 2:19 
Following this up in 2021 because I had the same issue. I fixed it by connecting the Pro Controller to Steam, then going to Steam -> Settings -> Controller -> General Controller Settings. When the Pro Controller is connected, there should be a setting for 'Controller Shutdown Time'. Set it to 'Never', and Steam will never let the Pro Controller go to sleep. I've had mine just sitting next to me for the last hour or two and it's still connected.
Seph 19 AGO 2021 a las 16:04 
I'm a victim of the same issue. I guess it's important to check whether your bluetooth adapter is fully compatible with the Switch Pro Controller before buying it. One of my VERY old adapters works just fine and allows the controller to pair again from shutdown immediately upon pressing any button. I bought another one hoping for a range improvement, but was met with this unfortunate issue. It doesn't seem possible to fix without a driver update.
Airfryer 21 SEP 2021 a las 15:01 
Publicado originalmente por Olachim:
My issue has been solved, either by itself via some form of update through something or maybe I was just hitting the wrong button all along.

If I just push literally ANY button except the home and pair buttons, it connects and stays connected to my PC like it should.
thank you so much!! this solved my problem
Eternal 3 DIC 2021 a las 12:27 
Came across this thread trying to fix a similar issue. I ended up fixing this by switching the bluetooth adapter on my computer from a 5.0 adapter to 4.0. Bluetooth 4.0 appears to work seamlessly, whereas with the 5.0 adapter I was using i had to manually reconnect my controller every time I wanted to use it.

YMMV
tyoma53 10 DIC 2021 a las 23:35 
Publicado originalmente por Eternal:
Came across this thread trying to fix a similar issue. I ended up fixing this by switching the bluetooth adapter on my computer from a 5.0 adapter to 4.0. Bluetooth 4.0 appears to work seamlessly, whereas with the 5.0 adapter I was using i had to manually reconnect my controller every time I wanted to use it.

YMMV

strange, i have another laptop with intel bluetooth 5 card. i don't have any issues with switch pro controller reconnection there, so i was absolutely sure, any bluetooth 5 card/adapter will help me to solve the problem. but looks like it depends on chipset manufacturer, not on bluetooth version.
thanks for info.
Nickrixo 1 ENE 2022 a las 17:12 
I've ran into a similar issue as well.

So here's the story:

I was just playing through Halo Infinite's campaign. My pro controller had zero issues before and connected with ease. But as I was playing, I shot a brute with a skewer and apparently my game had a heart attack right as the bullet made contact. It made the whole ERRRRRRRRRRRR sound when it freezes and my pro controller was just stuck endlessly vibrating from the rumble. The game of course crashed at that moment, and while Halo Infinite has crashed on me several times before( obviously is has some performance issues), this was the first time it messed up my controller the way it did.
Cause even after the game had crashed, my pro controller was stuck vibrating and wouldn't respond to any button presses. I turned it off and it would stop, but as soon as I turned it on, it would be stuck vibrating again and wouldn't stop no matter what I tried.
That is until I booted up Halo again, but I had load all the way into the campaign again, and when I finally loaded in, IT STOPPED. It started working like normal, and I just started playing again... for like a minute. Then the controller itself died. So I shrugged it off, and just connected it via usb and had no issues after that.
It wasn't until the next day when I tried to reconnect it via bluetooth that the controller would NOT at all connect to my computer. The computer, however, detects it. It says it's connected and even confirms that its paired successfully, but the controller itself is just stays searching and the lights won't settle until it eventually gives up. I've tried forgetting the device and reconnecting but still won't work to this day. Like I said, the controller will search and the computer will detect and "pair", but the controller won't actually connect. It still works perfectly fine when its wired tho, but as soon as I pull the wire out, the controller just turns off. The controller still even connects wirelessly to my switch without issue, but not the computer.
Idk what happened, but if there's a fix, I would love to know. I also wondered if there was a way to factory reset the controller? idk if that would fix it or if it would even be possible. But yeah, thats my dilemma :P
Última edición por Nickrixo; 1 ENE 2022 a las 17:17
sam ⛟ 21 ENE 2022 a las 19:33 
Publicado originalmente por Veggie_Tables:
I've ran into a similar issue as well.

So here's the story:

I was just playing through Halo Infinite's campaign. My pro controller had zero issues before and connected with ease. But as I was playing, I shot a brute with a skewer and apparently my game had a heart attack right as the bullet made contact. It made the whole ERRRRRRRRRRRR sound when it freezes and my pro controller was just stuck endlessly vibrating from the rumble. The game of course crashed at that moment, and while Halo Infinite has crashed on me several times before( obviously is has some performance issues), this was the first time it messed up my controller the way it did.
Cause even after the game had crashed, my pro controller was stuck vibrating and wouldn't respond to any button presses. I turned it off and it would stop, but as soon as I turned it on, it would be stuck vibrating again and wouldn't stop no matter what I tried.
That is until I booted up Halo again, but I had load all the way into the campaign again, and when I finally loaded in, IT STOPPED. It started working like normal, and I just started playing again... for like a minute. Then the controller itself died. So I shrugged it off, and just connected it via usb and had no issues after that.
It wasn't until the next day when I tried to reconnect it via bluetooth that the controller would NOT at all connect to my computer. The computer, however, detects it. It says it's connected and even confirms that its paired successfully, but the controller itself is just stays searching and the lights won't settle until it eventually gives up. I've tried forgetting the device and reconnecting but still won't work to this day. Like I said, the controller will search and the computer will detect and "pair", but the controller won't actually connect. It still works perfectly fine when its wired tho, but as soon as I pull the wire out, the controller just turns off. The controller still even connects wirelessly to my switch without issue, but not the computer.
Idk what happened, but if there's a fix, I would love to know. I also wondered if there was a way to factory reset the controller? idk if that would fix it or if it would even be possible. But yeah, thats my dilemma :P
did you find a fix?
Nickrixo 21 ENE 2022 a las 23:17 
Nope. Still doesn't connect to this day
GTechRepublic 3 FEB 2022 a las 12:49 
Ok. I just recently discovered this issue and couldn't take it anymore. Stole my wife's Broadcom BCM20702 4.0 adapter. No longer an issue. Immediately connects. What was I using before? Asus BT500 5.0 adapter.
arkaii 17 MAR 2022 a las 11:48 
I have the same exacte issue, i try download the drivers of the bluetooth dongle, i bought another dongle, a 5.0 one, same issue ... i'm using cable..
rrsgg 18 MAR 2022 a las 10:47 
Hi, same issue here. Actually, It works as it should with a tp-link UB400, but I tried to update to a UB500 of the same brand and found this issue; I also tried with another bt 5.0 and had the same problem. Can anybody tell an specific bt chipset 5.0 which works properly? Thank you
tyoma53 19 MAR 2022 a las 4:15 
intel's chipset works fine for me. seams, realtek chipsets has this issue, because i had one with it
rrsgg 25 MAR 2022 a las 16:13 
Thank you! The intel bt 5.0 does work as it should!
Marten Ratte 22 ABR 2022 a las 15:57 
I had the same problem and now is fixed.

i am using ROG B550F motherboard, and last year the bt part broke for no reason, then i bought a TPlink U500 adapter(bluetooth 5.0). With this adapter i had the problem, i couldnt automatically connect my pc after successfully paired(the first connect is all good but after shutting down the bt i cant automatically connect again), only to delete the device and pair again.

But my roomate has no this problem, and he is using TPlink U400(bluetooth 4.0), i tried his adapter on my pc and it does work.

So i bought a U400 to deal. Kind of ironic xD
Fluffy Hat 9 AGO 2022 a las 8:48 
I finally fixed it!

I was previously using a Asus BT500 5.0 adapter and had the same reconnecting issue as everyone else.

I downgraded to a Asus BT400 4.0 adapter and now my Switch pro reconnects after sleep.

It does seem to be a Bluetooth 5.0 issue, and going back to Bluetooth 4.0 fixes it.
< >
Mostrando 16-30 de 142 comentarios
Por página: 1530 50