@rafaz182 having the same issue with 4.7.1. Downgraded to 4.6 with a new flash but stopped working after doing an "apt upgrade" on 4.6 - did this fix you posted worked on 4.7.1?

@ohmycommodore Went with mode D instead of X and yes that does seem to eliminate the delay.

@pscotto1234 said in Bluetooth RetroPie Setup Script Issues:

@spaceace said in Bluetooth RetroPie Setup Script Issues:

Hi, All.

Thank you for this thread. I found it AFTER I clicked the button to order my controller! I now have the 8BitDo SN30 Pro+ controller working flawlessly on a Raspberry Pi 4B, with RetroPie 4.7.1 on updated OS.

Before I attempted to pair, the pad was connected via USB to the Ultimate Software application for a firmware update. I also configured a Switch profile, with star(★) as turbo button.

I followed these steps before pairing, too. I consider these safe steps, as it only disables an unused SIM card driver and delays bluetooth start for two seconds at boot.

So, then...
$ sudo nano /lib/systemd/system/bluetooth.service
$ sudo nano /lib/systemd/system/bthelper@.service
$ sudo rm /etc/udev/rules.d/99-bluetooth.rules
$ sudo reboot
$ sudo /home/pi/RetroPie-Setup/retropie_setup.sh
Configuration / Tools -> bluetooth
hack OFF
power on controller by holding Y + start one second (Switch mode)
hold in pair button for three seconds
leds will rotate like knight rider
Register and Connect to Bluetooth Device
on "Searching" screen, pressing some buttons can help
choose "Pro Controller"
DisplayYesNo
Setup the udev rule
hold start three seconds to turn pad off
reboot
turn on controller
configure input
GOOD

I have the pad in Switch mode. To select the profile with turbo, press both sticks (L3+R3) and the heart/home button will light up. Hold a button and press star(★) to enable/disable turbo. It will stay in Switch mode with profile, so now all you have to do is hold the start button to turn it on or off.

Hope that helps. Cheers.

It works fine Smith DS4. Later I'll give it a try using a sixaxis controller.
@spaceace thank you so much!!!

Sixaxis works as well!!!

@zenoxio You can bring up the RetroArch's RGUI and check how the Pad 2 is setup - is it set to 'RetroPad' or something else ? Might be that Genesis-Plus GX has a strange default for the 2nd controller, you could try lr-picodrive and see if the same issue happens.

@dankcushions Thanks for that, clears it up a little bit.

@cook1e_mr
Different seller, but it was these: Ebay

After trying Bluetooth w/o success --- Does Retropie Support USB Headphones and Headsets? How does it work? I am new to Linux as well --- I am not afraid of using the command line --- I just need my handheld if needed. Thank you in advance.

Hi, please see this
https://retropie.org.uk/forum/topic/30346/issues-with-bluetooth-on-4-7

@dmg9626

OMG! IT WORKED 🤯

For the record this fixed my Retro-bit "SEGA Saturn® Bluetooth® Wireless Control Pad - Slate Grey" pairing issues with my rpi 4.

TYVM dmg9626 u the man 🥳

@agrajag
Sure, here it is

; ----------------------------------------------------------------------------------------- MAP 0 ; keymap 0 (default keymap) ; ----------------------------------------------------------------------------------------- F3 PAUSE JS0_BTN_10 QUIT JS1_BTN_10 QUIT ; ***** Joystick #0 - Left Controller ***** ; ** Side Buttons and Numeric Keypad ** JS0_BTN_01 PD0L_A_T JS0_BTN_04 PD0L_A_L JS0_BTN_05 PD0L_A_R 1 PD0L_KP1 2 PD0L_KP2 3 PD0L_KP3 4 PD0L_KP4 5 PD0L_KP5 6 PD0L_KP6 7 PD0L_KP7 8 PD0L_KP8 9 PD0L_KP9 BACKSPACE PD0L_KPC 0 PD0L_KP0 RETURN PD0L_KPE ; ** Direction Disc ** JS0_N PD0L_J_N JS0_NNE PD0L_J_NNE JS0_NE PD0L_J_NE JS0_ENE PD0L_J_ENE JS0_E PD0L_J_E JS0_ESE PD0L_J_ESE JS0_SE PD0L_J_SE JS0_SSE PD0L_J_SSE JS0_S PD0L_J_S JS0_SSW PD0L_J_SSW JS0_SW PD0L_J_SW JS0_WSW PD0L_J_WSW JS0_W PD0L_J_W JS0_WNW PD0L_J_WNW JS0_NW PD0L_J_NW JS0_NNW PD0L_J_NNW ; ***** Joystick #1 - Right Controller ***** ; ** Side Buttons and Numeric Keypad ** JS1_BTN_01 PD0R_A_T JS1_BTN_04 PD0R_A_L JS1_BTN_05 PD0R_A_R Q PD0R_KP1 W PD0R_KP2 E PD0R_KP3 R PD0R_KP4 T PD0R_KP5 Y PD0R_KP6 U PD0R_KP7 I PD0R_KP8 O PD0R_KP9 TAB PD0R_KPC P PD0R_KP0 SPACE PD0R_KPE ; ** Direction Disc ** JS1_N PD0R_J_N JS1_NNE PD0R_J_NNE JS1_NE PD0R_J_NE JS1_ENE PD0R_J_ENE JS1_E PD0R_J_E JS1_ESE PD0R_J_ESE JS1_SE PD0R_J_SE JS1_SSE PD0R_J_SSE JS1_S PD0R_J_S JS1_SSW PD0R_J_SSW JS1_SW PD0R_J_SW JS1_WSW PD0R_J_WSW JS1_W PD0R_J_W JS1_WNW PD0R_J_WNW JS1_NW PD0R_J_NW JS1_NNW PD0R_J_NNW

I found my solution and I will post it out here so it might help someone else with bluetooth audio problems.

I think my whole issue is because I did not add user "pi" to bluetooth. I followed the article here https://retropie.org.uk/forum/topic/20338/tutorial-bluetooth-audio-on-retropie-v4-4-and-raspberry-pi-3-model-b

Finally bluetooth connected in the GUI and it worked out for me in the end.

@monsterrob said in Wii U Pro Controller will not connect:

@mitu I have the most up to date version of retropie with nothing added so do you think your second point applies, I have read it but I wouldn’t know where to start with removing a configuration.

Please add the rest of the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Removing a configuration is done from the Bluetooth menu, using the Remove Bluetooth Device entry.

@luzer

In boot/config.txt I added dtoverlay=disable-bt to disable the onboard bluetooth. The bluetooth dongle is a cheap one (€10 ish) but it works fine. I did connect my controllers through the bluetoothctl command line options just so I could check how things worked behind the menu in retropie.

Can't help you any further though, sorry.

@mitu No, that doesn't work for me. That is my issue from the title: Device not available.

IMG_20210302_225753.jpg

@gordonfreemanjr said in 8bitdo FC30 not pairing via Bluetooth:

@jplank Was that it?

Someone suggested I SSH into the retropie and go to bluetoothctl and then scan now. I did so and neither of the controllers showed up. I rebooted and tried again, same result. Then I tried one last time to load emulation station and pair the controllers - and it worked right away.

The thing is that I had about 15 tabs open with any youtube tutorial and help thread that I could find and I was trying anything I could find. For me, it wasn't that I changed setting X and then it suddenly started working. I "think" the last setting I changed was when mitu suggested changing the pairing mode. I changed it back to default and had to try a few more times to connect before it finally did. There might have been some resetting in there. All in all, I spent hours trying to get it to pair. I hope you manage to get yours fixed in less time. I hope that helps a bit. Good luck!