Hey, a small hint for anybody looking analyzing the problem. It seems the issue in reconnecting is a Pi 4 related problem.
I tried it with a pi zero w and the controller is reconnecting.
I will also try the 3b+ I´m using for my 3D printer.
Maybe this will help any developer to solve the problem for Pi 4.
Happy Estern!
If it could be caused by BlueZ, is it possible tu update the version manualy to 5.56?
Knock knock, its me, with the next controller-related topic.
Sorry but I have no luck so far.
My problem is described like this post from December.
https://forum.recalbox.com/topic/21901/ps4-controller-not-automatic-pairing-after-boot/4?_=1616701963065
In short, the BT-Controller is not connecting after rebooting the Pi4 4GB. Version of recalbox is 7.1.1. It is flashed on a SD-Card with 32GB. Image is distributed and flash by Raspberry Pi Imager. The sticker of the Controller I bought is showing CUH-ZCT2E as model-number. I´m quiet sure it not an original one.
Here some info about the paired and actual connected controller given by bluetoothcli:
[Wireless Controller]# info 2D:92:30:00:96:C9
Device 2D:92:30:00:96:C9 (public)
Name: Wireless Controller
Alias: Wireless Controller
Class: 0x00002508
Icon: input-gaming
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v054Cp05C4d0100
I´m able to force the issue without reboot by turning the BT off and on again by cli command power off/on
When I try to connect then, the output looks like this:
[Wireless Controller]# power off
[CHG] Controller B8:27:EB:FF:08:35 Discoverable: no
[CHG] Device 2D:92:30:00:96:C9 ServicesResolved: no
[CHG] Device 2D:92:30:00:96:C9 Connected: no
Changing power off succeeded
[CHG] Controller B8:27:EB:FF:08:35 Powered: no
[CHG] Controller B8:27:EB:FF:08:35 Discovering: no
[bluetooth]# power on
Changing power on succeeded
[CHG] Controller B8:27:EB:FF:08:35 Powered: yes
[CHG] Device 2D:92:30:00:96:C9 Connected: yes
[CHG] Device 2D:92:30:00:96:C9 Connected: no
First it tells Connected: yes (Controller keeps blinking)
maybe 3 seconds later => no
I have testet all options in the recalbox.conf for PS3 controller ( bluez 5 / official / shanwan )
Am I doing something wrong?
The post above is closed with the info the issue is fixed with version 7.0.1
Thanks in advance
Svart
Hi together,
I think I have found something what my problem is about.
https://github.com/libretro/retroarch-joypad-autoconfig/issues/38
The device-ID is misslead.
Now as my ordered "official" PS4 Controllers arived, I will focus on them.
We will hear soon 
Maybe I did not discribe my problem adequate.
I´d like to use my triggers as analog inputs.
At the moment they act like switches.
All I saw on YT was old, 2017 earlier.
For example the guy in the video is doing the first keymapping.
Time: 1:36 https://www.youtube.com/watch?v=Y6uM5GJoU3w
The left trigger (L2) is showing as AXIS 2+, mine is showing as button 6.
All the things I read (date around 2015) were the other way round. They were about special options for the driver xboxdrv to force the triggers as switches.
I can´t find anything about driveroptions in the tutorials.
Or did I miss here something?
Thank you really for your effort!
@Zing The Version is 7.1.1-Reloaded
It is running on a Pi4 4GB. I flashed the SD card with Raspberry Pi Imager and the pretended image for Pi 4 / Pi 400.
Shall I flash an image from the website?
Regards
@Zing thanks for your posts.
I did not manage to figure out how to change the
input_l2_btn = "6"
input_r2_btn = "7"
in the file Xbox 360 Wireless Receiver.cfg to any kind of analog items to remap them to the right stick?
All I can find aside the links above are decrepated links leading to github.
Do anyone know if the correct name of the analog equivalent to input_x2_btn?
Thank you in advance!
Would it help to switch to a PS4 controller?
Hi, I like to use the analog triggers of the controller for acceleration and break. The idea is to remap this axis to the y-axis of the right joystick. I can get I to work as a switch.
Do you have any advice how I could solve the problem?
Best regards