Switch Pro controller bluetooth - br-connection-create-socket error

sylverena · 2024-08-25 20:50:21

Hello all, writing here today as my first post about some issues I've been having while trying to connect my Switch Pro controller via bluetooth to my laptop. I've been working at this for several hours, been looking through the wiki, here, and some adjacent forums, but have yet to find a verified solution. Detailed below are my specs and what I have tried:

Specs

Kernel: 6.10.6-arch1-1
DE: KDE Plasma 6.1.4 x11 (KWin)
Bluetooth: Realtek Bluetooth Radio (Using bluez and bluez-utils packages)

What I have tried

Several reboots
Checking if bluetooth was blocked via rfkill
Installing bluez-hid2hci
Trying to forget, re-pair, connect through bluetoothctl instead of the KDE frontend
Full system update
Checking udev rules and additionally installing game-devices-udev from the AUR
Checking if the bluetooth kernel module wasn't being loaded
modprobe hid_nintendo

At first, when I wanted to connect the controller, I tried connecting to it using the KDE gui frontend for bluetooth. The wizard seems to consistently fail with no error message. However, in looking on the devices menu, it would appear that they paired. Trying to connect directly to the controller after this gives an error through KDE that says 'br-connection-create-socket'. I checked the service status via systemctl and the output is as follows:

$ systemctl status bluetooth.service

[...]

Aug 25 14:42:27 sylpup-ARLP bluetoothd[3216]: profiles/input/device.c:control_connect_cb() connect to DC:CD:18:A9:37:9B: Connection timed out (110)
Aug 25 14:43:49 sylpup-ARLP bluetoothd[3216]: profiles/input/device.c:control_connect_cb() connect to DC:CD:18:A9:37:9B: Permission denied (13)
Aug 25 14:43:54 sylpup-ARLP bluetoothd[3216]: profiles/input/device.c:control_connect_cb() connect to DC:CD:18:A9:37:9B: Permission denied (13)
Aug 25 14:43:59 sylpup-ARLP bluetoothd[3216]: profiles/input/device.c:control_connect_cb() connect to DC:CD:18:A9:37:9B: Permission denied (13)
Aug 25 14:45:48 sylpup-ARLP bluetoothd[3216]: profiles/input/device.c:control_connect_cb() connect to DC:CD:18:A9:37:9B: Connection timed out (110)

After doing some searching around, I decided to try pairing with the controller through bluetoothctl. Here is the output from that:

pair DC:CD:18:A9:37:9B
Attempting to pair with DC:CD:18:A9:37:9B
[CHG] Device DC:CD:18:A9:37:9B Connected: yes
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B Bonded: yes
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B Modalias: usb:v057Ep2009d0001
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B ServicesResolved: yes
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B Paired: yes
[Pro Controller]# Pairing successful
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B WakeAllowed: yes
[Pro Controller]# [CHG] Device E8:E0:7E:01:14:64 RSSI: 0xffffffb6 (-74)
[Pro Controller]# [CHG] Device 4A:1D:96:AE:77:34 ManufacturerData.Key: 0x004c (76)
[Pro Controller]# [CHG] Device 4A:1D:96:AE:77:34 ManufacturerData.Value:
[Pro Controller]#   09 08 13 96 c0 a8 01 c5 1b 58 16 08 00 0c 7b dc  .........X....{.
[Pro Controller]#   5e b2 d4 c1                                      ^...            
[Pro Controller]# [CHG] Device DC:CD:18:A9:37:9B ServicesResolved: no
[CHG] Device DC:CD:18:A9:37:9B Connected: no

And trying to connect after pairing:

connect DC:CD:18:A9:37:9B
Attempting to connect to DC:CD:18:A9:37:9B
[CHG] Device DC:CD:18:A9:37:9B Connected: yes
[Pro Controller]# Failed to connect: org.bluez.Error.Failed br-connection-create-socket
[CHG] Device DC:CD:18:A9:37:9B Connected: no

which is the same error that the KDE frontend gave me. Beyond this,, I tried all the miscellaneous solutions i have listed above, and then tried re-pairing and connecting for each one, but I get the same error message each time. Additionally, it seems that the devices don't truly pair because tapping the home button on the controller powers on my switch in the same room. I made sure to fully power off my switch to ensure no conflicts between them, but the issues still persist. Any ideas? I've been working on this for so long and I'm completely stumped

astdd · 2024-09-03 11:48:24

I'm having a similar problem after upgrading to AX210.

This issue seems interesting to me: https://github.com/bluez/bluez/issues/824
And if I connect directly from bluetoothctl without pairing first, it would connect, though no hid events would be sent back (so it's useless).

Edit:
There is a workaround for now. In bluetoothctl, first remove the device.
Then trust MAC -> pair MAC -> connect MAC.
It would make the controller usable until it's powered off. You'll need to do the same thing again on the next power cycle.

Last edited by astdd (2024-09-07 01:32:52)

sylverena · 2024-09-23 18:17:55

Interesting. I am not at home right now but I will try again once I get home. I have since ran some system upgrades, and some previously unnoticed issues with connecting to my phone as well have been resolved. If this does not work, I will try the workaround. Thank you for the information!!

sylverena · 2024-09-27 14:10:20

Apologies for the delay, things have been hectic. Based on what I am seeing, the issue still persists when applying the workaround, however funnily enough trying it over and over again does actually get it connected. The updates to the kernel and bluez however have not allowed things to work as expected yet. I think I will mention on the github issue what has been happening

plsdnttm · 2024-12-23 13:05:17

hi. adding for future reference. I had the same error but with a ps4 controller. As the device was listed as available in the settings after first try (just like yours), I ended up fixing it by simply clicking connect from there and re-enabling "pair mode" with my controller again

italoghost · 2025-04-18 19:14:20

Hi, everyone! I don't know why this works, but I have been able to successfully pair my 8BitDo Pro 2 Controller in Switch mode on a gamescope session. After pairing it and switching to the desktop session (I use COSMIC) my controller was recognized normally.

SimonJ · 2025-06-04 11:18:41

I am getting this error

br-connection-create-socket

with a new BT controller.

I have a script to remove, pair and connect which means it works but is there an actual fix yet?

Arch Linux

#1 2024-08-25 20:50:21