Multiple bluetooth gamepads with same name and slight differences

[dikdom]

Hello,
I have two bluetooth gamepads (you can find them on internet as Terios T3). If I want to configure them alone, they work properly. My problem is that I would like to use them at the same time. The root of the problem is that both of the devices report their names as "Gamepad". When they are connected at the same time, they are reconnecting every now and then..
After some research I edited the udev rule file and changed the select critaeria from their name to their BT address. Now both of the devices connects properly, no broken connections, etc..
But as the names of the devices are the same they have one configuration file in the /opt/retropie/configs/all/retroarch-joypads directory.
The button configuration of these two gamepads are different, the second one doesn't work with the first one's configuration and vice versa.

When I configured the second Gamepad using EmulationStation it showed as if it had found 'Gamepad 1' but it saved a file named Gamepad.cfg (actually had overwritten the first gamepad's config file)...

Is there a way to tell EmulationStation and/or RetroArch to differentiate the controller by their bluetooth addresses instead of the name the device reports about itself?

[dikdom]

Hello,
couple of weeks passed and things happened.
First, it turned out that the autoconfig files in the retroarch-joypads directory contain different values than the jstest tool prints. This is pretty confusing to me but when I executed the builtin joy configuration tool of retroarch, it created the file with different values for the two gamepads. And the buttons works with those 'different' values. So much for jstest. (I guess libretro doesn't use SDL2, but EmulationStation). Interestingly the scancodes of the joys are the same for jstest, but different for the retroArch config...

Secondly I visited the irc channel of retroArch and there I was told that the joys/gamepads are recognized by their name, vendorID and productID (bluetooth address doesn't play any role in this procedure - which is again surprising for me). These values are the same for my pads, so only one option is left for me: forget about autoconfiguration and configure the pads manually.
Now in my retroarch.cfg file I

• turned off autoconfiguration (input_autodetect_enable), so upon lr- game start the joy config files are not re-loaded
• configured the scancodes of the buttons/Dpads/axis in the retroarch.cfg file for both joysticks..

Now I can play Super Bomberman 3 happily with my kids in two player mode...

Thanks for reading!