@mitu

After some testing it disconnects when have rumble enabled. Without rumble no problem at all. It only does that when in use. The problem starts when it have rumble enabled.

I have notice this also. When in dualschock mode on retroarch it disconnects far more times per minute from when having on standard mode which seems to be working with less rumble effect( probably one motor is working not both like on dualshock)

Regards.

Yeah I use my switch pro controller, I havent done any extra configuration at all and it pairs just fine. Can you try another bluetooth controller? Dualshock 4 or Xbone one controller?

If this is your first time pairing via bluetooth, you might want to check that your bluetooth is working correctly with this command in the terminal:

systemctl status bluetooth.service

@eberhab After more research it turns out that this is a "Pro Controller" related issue which affects all cores and emulators. It has already been beautifully solved here: https://retropie.org.uk/forum/topic/16503/how-to-connect-a-switch-pro-controller-with-analog-stick-without-xboxdrv

@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.

Update:

If I'm not loading the save state game and just run the game it fails to start and moves me back to EmulationStation list of Dreamcast games with controls not working.

Here is the log from /dev/shm/runcommand.log

[ERROR] emu_read_server_msg unknown cmd=0x1e4baa8 [ERROR] [/builds/inolen/redream-private/src/guest/memory.c:853] Check failed: res

@komarin By "pro controller", do you mean the switch pro controller ? If so, you might be interested in reading https://docs.google.com/document/d/10KXz0gD1Lo-7UkDyezSnyrm1vILn-fMSilwPE_kpOik/mobilebasic

Just to give a conclusion to the thread, I tried a whole bunch of stuff. I tried jscal, evdev-joystick, updating the kernel, downloading some different files... but ultimately, this is what worked:

https://retropie.org.uk/forum/post/227102

I installed hid-nintendo as described in the post and everything just worked like it was supposed to after rebooting the machine. It makes you reconfigure the controller, but after that, it just works.

I believe I have figured it out, although I'll see how everything acts for the next few days.

I did have to use a separate bluetooth controller for each switch pro controller. I did everything using bluetoothctl. I left scan on both bt controllers, discovery off, and agent to NoInputNoOutput. I then connected one switch pro to each bluetooth controller and trusted the switch pro controller. Seems like I can now turn off a controller and turn it back on and it will connect automatically, nothing manual required.

I can't figure out the analog sticks with two controllers. I saw a post about using xboxdrv and a udev rule and a systemd service file, I tried that, but only one controller was being recognized as a "Switch Pro Controller", the other still only recognized as a "Pro Controller" (so no analog up or right). Also, for some reason when I had all of this enabled and I would try to configure the inputs on a switch pro controller it would say that 5 gamepads were detected. Couldn't get anything to actually work in a game either, only in emulationstation. Once I uninstalled xboxdrv and deleted the udev rule and systemd service file and restarted retropie then worked correctly, only seeing 2 gamepads and they work in games.

Maybe one day the analog sticks will just werk without messin around with it. Until then I just won't be playing n64, which I guess doesn't work all that well anyway

@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.

Does it work too ?
if i am using two Pro Controller as in Player 1 and Player 2

Nevermind.... it doesn't work.

I tried redoing my configs because the switch pro controller would get recognized 1/4 of the time. Ended up with the Pi detecting the pro controller but not the switch pro controller.... I don't get with this is so difficult with the switch...

@mitu i used the configuration provided earlier in this conversation, the one provided by @Amishgamer .

@YFZdude thanks for the feedback, i will try to uninstall those drivers then and see if that helps

EDIT

now i completely messed it up i think...

EDIT 2

Actually, after it first crashed to the console, the controller now seems to work fine

And @Amishgamer 's config also works! Oh my god, thank you so much guys, you are awesoem!