You are not logged in.
I recently bought a Switch Pro Controller. Pairing it and connecting it in Bluetooth to my computer works, but if I reconnect it after a disconnect, it doesn’t work. I have to remove and re-add the controller.
More details:
When I reconnect the controller, instead of lighting the first led, it shows the waiting pattern (the four leds in front of the controller light up one after the other in succession), until at some point it gives up and turns off.
It doesn’t seem to depend on the kind of disconnect (manually from the OS, manually or automatically (power save) from the controller).
It doesn’t seem to depend on whether I just press a key (reconnecting it automatically) or the reset button (reconnecting it manually from my OS) to connect the controller.
Removing the controller, re-pairing it, and reconnecting it always works.
It seems something goes wrong just after connecting, and that happens all the time except after the first connection after pairing.
My system is up-to-date, the controller firmware is up-to-date (according to my Switch), other Bluetooth devices reconnect just fine, I have tried putting `ControllerMode=bredr` in my `/etc/bluetooth/main.conf` and restarting the Bluetooth daemon, it’s the same whether Steam is open or not, etc.
Bluetooth logs:
$ bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller C0:B5:D7:1F:83:C4 Discovering: yes
[NEW] Device 50:23:6D:97:07:5B Pro Controller
[bluetooth]# pair 50:23:6D:97:07:5B
Attempting to pair with 50:23:6D:97:07:5B
[CHG] Device 50:23:6D:97:07:5B Connected: yes
[CHG] Device 50:23:6D:97:07:5B Bonded: yes
[CHG] Device 50:23:6D:97:07:5B Modalias: usb:v057Ep2009d0001
[CHG] Device 50:23:6D:97:07:5B UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device 50:23:6D:97:07:5B UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 50:23:6D:97:07:5B UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 50:23:6D:97:07:5B ServicesResolved: yes
[CHG] Device 50:23:6D:97:07:5B Paired: yes
Pairing successful
[CHG] Device 50:23:6D:97:07:5B WakeAllowed: yes
[Pro Controller]# connect 50:23:6D:97:07:5B
Attempting to connect to 50:23:6D:97:07:5B
Connection successful
[Pro Controller]# disconnect 50:23:6D:97:07:5B
Attempting to disconnect from 50:23:6D:97:07:5B
[CHG] Device 50:23:6D:97:07:5B ServicesResolved: no
Successful disconnected
[CHG] Device 50:23:6D:97:07:5B Connected: no
[bluetooth]# connect 50:23:6D:97:07:5B
Attempting to connect to 50:23:6D:97:07:5B
[CHG] Device 50:23:6D:97:07:5B Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-create-socket
[CHG] Device 50:23:6D:97:07:5B Connected: noUnit logs:
$ journalctl --boot -e --unit=bluetooth
Mar 09 16:39:55 potipat bluetoothd[22149]: Bluetooth management interface 1.22 initialized
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/ldac
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/aptx_hd
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_hd
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/aptx
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/aac
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aac
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/sbc
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/sbc
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/sbc_xq
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/sbc_xq
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/faststream
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/opus_05
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/opus_05
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Mar 09 16:39:55 potipat bluetoothd[22149]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Mar 09 16:40:02 potipat bluetoothd[22149]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mar 09 16:40:07 potipat bluetoothd[22149]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 2C:E0:32:A6:BC:46: Host is down (112)
Mar 09 16:40:13 potipat bluetoothd[22149]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mar 09 16:41:19 potipat bluetoothd[22149]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info
Mar 09 16:42:17 potipat bluetoothd[22149]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info
Mar 09 16:42:57 potipat bluetoothd[22149]: profiles/input/device.c:control_connect_cb() connect to 50:23:6D:97:07:5B: Connection refused (111)Kernel logs:
$ journalctl --boot -e --dmesg
Mar 09 16:41:20 potipat kernel: nintendo 0005:057E:2009.0008: unknown main item tag 0x0
Mar 09 16:41:20 potipat kernel: nintendo 0005:057E:2009.0008: hidraw5: BLUETOOTH HID v80.01 Gamepad [Pro Controller] on c0:b5:d7:1f:83:c4
Mar 09 16:41:22 potipat kernel: nintendo 0005:057E:2009.0008: using factory cal for left stick
Mar 09 16:41:22 potipat kernel: nintendo 0005:057E:2009.0008: using factory cal for right stick
Mar 09 16:41:22 potipat kernel: nintendo 0005:057E:2009.0008: using factory cal for IMU
Mar 09 16:41:23 potipat kernel: nintendo 0005:057E:2009.0008: controller MAC = 50:23:6D:97:07:5B
Mar 09 16:41:24 potipat kernel: input: Nintendo Switch Pro Controller as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb1/1-1/1-1:1.0/bluetooth/hci0/hci0:1/0005:057E:2009.0008/input/input29
Mar 09 16:41:24 potipat kernel: input: Nintendo Switch Pro Controller IMU as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb1/1-1/1-1:1.0/bluetooth/hci0/hci0:1/0005:057E:2009.0008/input/input30Offline
Same problem here. The only thing I can add is that in gnome-control-center, pressing a button on the switch controller after it has been disconnected will make the control center show "connected" for a few seconds.
Offline