@Oppo_Lock Thanks for sharing your solution.

Thank you very much, your suggestion was right. Without the nespi case everything works fine. Thank you so much. Now I have to solve another problem that I don't have in my cabinet. Don't know why the controllers swap themselves after some reboot. I don't touch anything, simply turn off, turn on and magically pad 1 becomes 2 and 2 becomes 1..... howhever, don't wanna go out of post, I'll post it in another one. Thank you again.

I'm having the same issue,
i have 4 controllers, 2 nes(clone)(usb), 2 genesis(8bitdo)(usb wifi dongle).
they share the same name,"USB Gamepad ", vendor 0079, product 0011.
They both use "USB Gamepad .cfg"
I've been trying to get around this for a while now.

(8bitdo m30 2.4g)
cat /proc/bus/input/devices
I: Bus=0003 Vendor=0079 Product=0011 Version=0110
N: Name="USB Gamepad "
P: Phys=usb-0000:01:00.0-1.4.3/input0
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/0003:0079:0011.0003/input/input2
U: Uniq=
H: Handlers=js1 event1
B: PROP=0
B: EV=1b
B: KEY=3ff 0 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

(generic usb nes controller clone)
I: Bus=0003 Vendor=0079 Product=0011 Version=0110
N: Name="USB Gamepad "
P: Phys=usb-0000:01:00.0-1.4.4/input0
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.4/1-1.4.4:1.0/0003:0079:0011.0005/input/input4
U: Uniq=
H: Handlers=js2 event2
B: PROP=0
B: EV=1b
B: KEY=3ff 0 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

(8bitdo m30 2.4g)
udevadm info -q all -n /dev/input/event[1]
P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/0003:0079:0011.0003/input/input2/event1
N: input/event1
L: 0
S: input/by-id/usb-0079_USB_Gamepad-event-joystick
S: input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.3:1.0-event-joystick
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/0003:0079:0011.0003/input/input2/event1
E: DEVNAME=/dev/input/event1
E: MAJOR=13
E: MINOR=65
E: SUBSYSTEM=input
E: USEC_INITIALIZED=5712528
E: ID_INPUT=1
E: ID_INPUT_JOYSTICK=1
E: ID_VENDOR=0079
E: ID_VENDOR_ENC=0079
E: ID_VENDOR_ID=0079
E: ID_MODEL=USB_Gamepad
E: ID_MODEL_ENC=USB\x20Gamepad\x20
E: ID_MODEL_ID=0011
E: ID_REVISION=0105
E: ID_SERIAL=0079_USB_Gamepad
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.3:1.0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_3_1_0
E: ID_FOR_SEAT=input-platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_3_1_0
E: LIBINPUT_DEVICE_GROUP=3/79/11:usb-0000:01:00.0-1.4
E: DEVLINKS=/dev/input/by-id/usb-0079_USB_Gamepad-event-joystick /dev/input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.3:1.0-event-joystick
E: TAGS=:uaccess:seat:

(generic usb nes controller clone)
udevadm info -q all -n /dev/input/event[2]
P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.4/1-1.4.4:1.0/0003:0079:0011.0005/input/input4/event2
N: input/event2
L: 0
S: input/by-id/usb-0079_USB_Gamepad-event-joystick
S: input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.4:1.0-event-joystick
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.4/1-1.4.4:1.0/0003:0079:0011.0005/input/input4/event2
E: DEVNAME=/dev/input/event2
E: MAJOR=13
E: MINOR=66
E: SUBSYSTEM=input
E: USEC_INITIALIZED=93696483560
E: ID_INPUT=1
E: ID_INPUT_JOYSTICK=1
E: ID_VENDOR=0079
E: ID_VENDOR_ENC=0079
E: ID_VENDOR_ID=0079
E: ID_MODEL=USB_Gamepad
E: ID_MODEL_ENC=USB\x20Gamepad\x20
E: ID_MODEL_ID=0011
E: ID_REVISION=0106
E: ID_SERIAL=0079_USB_Gamepad
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.4:1.0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_4_1_0
E: ID_FOR_SEAT=input-platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_4_1_0
E: LIBINPUT_DEVICE_GROUP=3/79/11:usb-0000:01:00.0-1.4
E: DEVLINKS=/dev/input/by-id/usb-0079_USB_Gamepad-event-joystick /dev/input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.4:1.0-event-joystick
E: TAGS=:seat:uaccess:

@alain said in Keyboard hotkey setting gets overwritten when using keyboard and controller as the same player:

e the dedicated exit button to leave the game.
The hotkey button from the controller player one is expected to be pressed and

there is no need do disable hotkeys at all just use game focus mode

@cebix That's not a huge pain. Just saw a guy on

using it on a RetroPie setup and it was working. He just had to set it to "PS3" controller.

@mitu so if I go to bluetooth and search for controllers with the android button combination will it connect?

@mitu Yes. And you are right. Unfortunatelly I did not realize each emulated system needs it's BIOS. It was indeed written in the link that was provided. I was looking for a specific controller problem and being new to the whole raspberry thing, I overlooked that information.
@aewoodall520 just happened to point out the thing I was missing.

P.S.: After updating the ES, I had to reconfigure the controlls for PSX again. It was a breeze thanks to your link, thank you.

This is my workaround:-

my /opt/retropie/configs/all/autostart.sh:-

python ~/MFRC522-python/rfidlaunch.py &
emulationstation

my rfidlaunch.py contains:
subprocess.call("/home/pi/nesmario.sh &" , shell=True)
when a corresponding RFID card is detected

this nesmario.sh
contains :
/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS nes '/home/pi/RetroPie/roms/nes/Super Mario Bros..zip'
emulationstation

this means my RFID script runs all the time, when the RFID card is detected in emulationstation it kills emulationstation, runs the rom as user pi and when the rom has quit relaunches emulationstation.

Thanks for all your help everybody

@larsks I don't use mame4all, so I can't say for sure about the axis, hopefully someone else will be able to.

What might help is binding the arrow keys to input control in mame4all. Technically, if your up/down/left/right is bound to dpad in emulation station, it should also translate dpad input to arrow keys. This is how you are able to navigate the menus like retropie-setup with a controller. You might need to run joy2key by hand before launching mame4all. Not sure.

@brewskii said in Yet another controller issue...:

Quick question though, is one game pad "dominant"?

Sort of - Player1 is the only one that's allowed to use the RetroArch menu and the hotkeys (including the Start + Select to exit the game).

I did that and the result is the same. I´m going to try again.

In the other games works fine. except for this...

Is anyone running a Stretch version of Retropie with an Xbox 360 controller?

Can you tell me what your buttons map to, and if the player lights are working?

Thank you for the replies everyone. I am probably going to go for the two port Mayflash adapter. The Raphnet stuff does look higher quality to be sure, but it's also double the price and on back order.

@kill if you have matching controllers or encoders you never have to configure player 2. Both players share the same config file. After you setup player one if you want player two working immediately in emulationstation just restart emulationstation. Retroarch emulators dont need a restart to have player 2 already working in it. You can create problems trying to find an issue with encoders wiring between both players if you setup player 2 as it overwrites any configuration you setup with player one.

I assume the problem depends on the Debian system.

Can I test the pairing myself on the commandline? Which commands are used in that case?

How can I contact the developers of the ps3controller driver for retropi? Maybe they have some hints on this problem.

@mitu
That was it. Thanks a lot.