@twistednerd said in jusubb controller wont reconnect bluetooth:

Jusubb bluetooth controller https://tinyurl.com/xew8fzds

Your link is blocked by the my PiHole installation - can you post a direct link ?

can connect and configure controller but when I reboot it will not reconnect no matter the connection method used.

If you shut down the controller and start the Pi first, does it connect when you start it up again ?

After trying a few times, and it crashed my pi, it finally just worked, and I was able to map the buttons in emulationstation. The light will always move from left to right at the bottom of the pad, but it seems to work fine (for now).

These Android geared devices are not always working with Linux/RetroPie, we got a few topics in the forum for them with issues during connection or - even after connection - not working properly.
Do you have a vendor support page with a manual/instructions on how to make them work with a PC ? Do they have a 'mode switch' between Android/PC connection mode ?

@standarsh14 said in RetroArch won't distinguish between two controllers:

It seems like either controller will work with one registered bluetooth connection - which confuses me because I thought that with separate Serials, only the one registered would work.

That's unexpected, the controllers should have different MAC addresses (they appear in the pairing dialog) so the OS would be able to tell them apart and some pairing info to be also stored on the device itself. Deleting the device from the list of paired Bluetooth devices in RetroPie should force the gamepad to be re-configured.

With both devices connected, can you run

cat /proc/bus/input/devices

and post the output ?

You can also test with jstest if the controllers are acting separately. Run:

jstest /dev/input/js0

and press the buttons on 1st, then on the 2nd controller. Only one controller should yield any events/output on the test.

Hi again.

The above post has solved my problem. I was able to effortlessly pair both controllers by following those instructions. For anyone who is stuck and sees this thread, I believe it was this command that solved the problem: sudo apt install bluez=5.50-1.2~deb10u1+rpt2. After updating the packages and checking the bluetooth status, I still got the Failed error messages, but once I inputted this command they disappeared. Of course, try everything just to be safe.

Thanks for your help!

@pie_droid Yes, you would have to have to use the same setting you paired with on the pi. It gets recognized as a different controller otherwise.

I tested the same controller setup with a pi3A so I have confirmed that the controllers are working properly. It seems to be an issue with the pi0w as both I have on hand had the same problem. I will rethink my genesis focused build to leverage the 8bitdo mod30s on a pi3A instead.

The question is - do I leverage a Genesis cartridge as the case or some sweet colorful nes carts I just picked up. I would need a label for the genesis cart. Let me know if anyone knows of a place to get a custom genesis cart label (preferably that fits on an EA sized game).

Please add some some info about your system and emulator used, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

The pastebin link is ok; the error Bluetooth messages seem to be the only ones available (no detection info), but they don't provide any indication where the fault is, unfortunately.

The blueooth packages are part of the OS (Raspbian) - they can be upgraded if a new version is released by the upstream Raspbian project and can be installed with the apt utility, or just choosing to update your OS packages from RetroPie-Setup when you do an upgrade.

@bc320 You only need xboxdrv for specific setups, it's kind of a virtual device driver - https://retropie.org.uk/docs/Universal-Controller-Calibration-&-Mapping-Using-xboxdrv/.

@quicksilver you're right in Mame2003+ simply open the Retroarch Menu/GUI > Quick menu > Settings (not Controls indeed) and head for the Control Mapping setting. Change the value either to Analog (left stick) or Digital (Dpad). Thanks for the tip as I completely missed that opion!

@melbmatt50 I've only ever used mame with an all-sega image I built a couple months ago and used retroflag's wired megadrive controller, so no analogs but it worked fine, though I never tested the mame stuff out on analog controllers.

Do you have the same problem with other mame cores?

@lmjiang1 hello i had this same issue with xu4 retroarena, m30 after reboot i get no pair, m30 would pair but couldnt do anything in game or ES, i updated m30, no luck.
Xu4 has only 3 ports i had a hdd connected, wifi usb, bt dongle all my usb connects gone so i thought maybe i need to connect to 3.0 usb, i bought 2 bt and same issue happen.
I then added a multi usb but it would do the same thing, i had some try m30 with thoses 20 dollar usb bt by with like super mario block design and i thought i need one of thoses, same thing happen, no pairing all what i have type above.

So i gave it about 2 months and asked again and tried again, once i had turned on the xu4 after months it paired right up like nothing had happened, so i played.
I had help and we tired to pair with switch mode and android but no luck i was fed up dude.

The guys at retroarena dont know what it is, i been waiting for about 1 month in a half but i havent bothered anymore.

But the m30 works fine with all other machines, just might be the xu4 cos someone else tired and did the same thing, might be your pi2 is the samething.
Works fine on my pi3b+ i used thme and pair just fine.

So my solution at the end since i got xu4 for saturn and just more power i put it away and ordered a pi4 and works super awesome!
I installed yabause on desktop and played dracula x.

Im sorry that it acts the way it does and i hope someone can help.

@lex3001 Please excuse the question, but are you really sure about the ghost inputs only happening in the Arcade menu? I ask because It sounds rather strange. Did you wait long enough in all of the menus to rule out mere coincidence of it happening only in the Arcade menu?

You can test a controller for ghost inputs out of Emulation Station by pressing F4 (you'll land in Retropie's command console) and entering this command:

jstest --event /dev/input/js0

Any inputs coming from the device will be listed while the command is running. You may have to change js0 to the device name of your controller, e.g. js1, js2 etc. You can end the test by pressing ctrl+c and return to Emulation Station with the command exit.

As for solutions for ghost inputs from bluetooth controllers, I fixed those that came from my Qumox Wii U Pro controllers by using a Mayflash Wii U Pro wireless adapter instead of the Raspberry Pi's own bluetooth to connect them. That got rid of the ghost inputs for good.

@mitu alright so after updating everything from source and powering down and coming back I got the it to pair with my switch pro controller which seems to work fine now. I also turned off Bluetooth on all my other devices in the house phone smartwatch etc maybe that helped

Still having issues with the SteelSeries. Able to configure and regsiter all the buttons in device setup. In emulation station all the buttons seem to work as programmed but once a rom is launched the center buttons the ones I have programed to start and select don't register. Looking through the forums it seems will have to jump through a lot of hoops to get the device to play nice with the SteelSeries XL.

Any suggestions?

Btw thanks again!!!

@mitu
Note for WiFi on the new Raspberry Pi 3 Model B+:

WiiFi is disabled until wireless regulatory domain is set (Pi 3 B+ only)

The domain can be done through 'Raspberry Pi Configuration' (rc_gui),
'raspi-config' or by setting 'country=' to an appropriate ISO 3166
alpha2 country code in /etc/wpa_supplicant/wpa_supplicant.conf.

US= United States
GB= UK

Example by another user of what it should look like (with GB country code)

country=GB
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="myssid"
psk="mywifipassword"
}

@mr_rogers89 https://retropie.org.uk/forum/topic/3/read-this-first