Hello,
I had the same issue and found another work around rather than reverting to the previous version.

The topic is discussed here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931

It seems that this is intentional will not be changed in future versions.
As mentionned right at the beginning of that post the workaround is the following:

Set ClassicBondedOnly=false in /etc/bluetooth/input.conf Run: systemctl restart bluetooth # or reboot

It worked for me.
Maybe its worth digging a little bit more to know what is the more suitable way of handling this new way of working of BlueZ...

Perhaps this?

https://www.8bitdo.com/micro/

My goal is for my friend to be able to turn on his headphones and connect much like the 8bitdo is allowing me to with the controller.

Then you need to pair & trust the headphones BT first (via bluetoothctl), just like the gamepad was paired with the RetroPie Bluetooth script.

'm confused if the above lines are related to the adapter, why would it be referred to as retropie?

It's the 'local' BT adapter and the name is taken from the hostname of the system, that's why it shows as 'retropie'. Controller is also a mis-nomer, it refers to the BT local device, not the gamepad you have connected.

I want to bring up this topic again!

As I have noticed from experience, at SWITCH mode sn30pro + retropie could has much delay! And it's awful :(

So, in 2024 year, could someone tell how to get work sn30 at XINPUT mode? ( with both working Triggers and "hotkey" buttons)

@mitu Ahhh on the keyboard to be PAIRED? No, I did not understand. Thanks, I'll try that.

edit: of course, it now works. I can't quite believe I didn't understand that part of the instructions haha

Thanks. I'll try that when I can save up some money.

Also some other details. When I try to connect it to other devices like my phone or laptop, it also turns off by it's own, and what's more is that Windows 11 says that its a "Driver Error" when reconnecting to the controller.
Also when reconnecting with Android, there is also a pin requirement of "0000".
(Maybe my controller is just the Issue)

Also, Is there a way to run:

Bluetoothctl

and try to re-pair and connect when retropie Starts, Restarts, or Boot up?
Because this might solve my Issue.

I think opening the issue is ok - seems something is not working correctly. Note that SDL includes some testing applications in the test folder, one of them is a joystick test - if you can reproduce the issue with it, then there's no need for pysdl2 or any confusion on the usage of SDL's event handling functions.

@Thorr69 Yeah, DUH on me. I saw XBox and then put my bliinders on! MY bad!

I have the same problem i downloaded BleGamepad and it says same eror it dint connected even once

You can't change the name of the controllers, at least not the ones that show up in the selection script. They come from the OS and cannot be controlled from userspace. The input_device_display_name option is useful just inside RetroArch (shows just a friendly name for the device), so that won't help in the selection script.

@mitu I see, so use a USB extension cable for the dongle.... I was hoping to keep this as aesthetically pleasing as possible. Are theere any good dongles that have better range?

@lostless That's great news. I have come across numerous articles about changing the button config for certain games, but I didn't know you could change the controllers for certain BIOS. Thank you very much!

Please don't double post - I deleted the previous post.
As to your problem - the Bluetooth pairing configuration is mainly geared towards input devices (i.e. gamepads) so it might not work 100% with other device types. You can still pair it using the bluetoothctl command line utility (see https://wiki.archlinux.org/title/bluetooth, the Pairing section).

I'm having a similar issue. When you run emulationstation --debug, it recognizes the controllers beautifully.

Even when rebooting, it goes directly to the system list but the controllers don't work. Re-reun with --debug and it works fine.

Any suggestions?

@Gérard
I was able to get into the editor and I made the changes that were suggested, but unfortunately my Bluetooth controllers are still not working. They worked a few years ago when I originally bought my pi. I guess I’ll keep digging around on the Internet.

@qstyler said in Cannot setup 8bitdo bluetooth adapter on Pi 4:

Hi! I'm trying to set up an 8BitDo BlueTooth adapter but it doesn't seem to work for some reason.

First of all, I disabled Bluetooth in the config.txt file by adding dtoverlay=disable-bt

Then I plug my dongle and try to do bluetoothctl, but it hangs forever.

To fix the issue I tried to run the following:

$ sudo systemctl enable bluetooth Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable bluetooth $ sudo systemctl start bluetooth

This command gives no output...

And this is a status of the bluetooth:

$ sudo systemctl status bluetooth * bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) Apr 09 11:24:42 retropie systemd[1]: Condition check resulted in Bluetooth service being skipped.

If I try to get a list of USB devices, I can see my dongle, but without a name (device 004):

$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2dc8:3107 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here's the full dmesg output, maybe this will help.
https://pastecode.io/s/ejohjh6u

I'm using Raspberry Pi 4 Model B Rev 1.2

There are no other USB devices connected to my Raspberry.

And I'm using a default usb-c power adapter that came in a box.

The 8bitdo bluetooth adapter is not actually a bluetooth adapter in the traditional sense. When you plug it in, it is treated as a USB controller, not a bluetooth radio. To connect a controller to the receiver, press the pairing button on the adapter, then press the pairing button on your controller. When both lights are solid, the connection is made. It also means you can only have one controller paired to the adapter at a time, and need multiple adapters if you want to pair multiple controllers. Changing bluetooth settings in the OS will have no effect on the adapter.

@mitu The price of 11.90 € / 10.46 £ seems reasonable. Order is placed and it’s on its way to me now. Thanks for the recommendation!