Nintendo Switch Pro controller won't disconnect from bluetooth after upgrading to V40 (Raspberry Pi 4 build)

[bigjake125]

Batocera build version

Stable V40 for Raspberry Pi 4

Your architecture

Raspberry Pi 4 B (SBC)

Your Graphic Processor Unit(s) (GPU)

Integrated Broadcom VideoCore VI

Issue description

The controller functions normally in all aspects once connected, the only issue is when I try to disconnect it (interestingly, initial bluetooth pairing only seems to work on the "automatic pairing" rather than the "manual pairing" option, but that might be irrelevant) This problem only began after installing the V40 stable update.
Normally when I finish a play session, I turn off my switch pro controller by pressing the sync button (on the top next to the usb-C port) to preserve battery. On the previous builds I've used (V38 and 39), batocera would recognize the disconnection after about 15 seconds and pop up with a "pro controller disconnected" message. Since upgrading to Stable V40, the controller connection persists in the batocera interface despite the controller being off. This means that when I try to reconnect by turning the controller back on, the controller is left trying to reconnect indefinitely because it is still recognized as "connected" in batocera. To fix it I have to plug in a USB controller and force batocera to "forget" that connection by toggling the bluetooth off and back on in the settings menu.
At this point, if I turn the pro controller back on it will immediately reconnect and continue to work normally unless I try to turn it off again. I don't have any other bluetooth controllers to test, so I don't know if this problem is unique to the Switch Pro or not.

Detailed reproduction steps

1. Install Stable V40 for Raspberry Pi 4 on a micro-SD and insert into pi
2. Pair Nintendo Switch Pro controller via bluetooth "automatic pairing" in the settings menu
3. Press the sync button on the top of the pro controller to power off

Details of any attempts to fix this yourself

I have tried deleting and re-pairing the controller from the bluetooth menu, as well as power-cycling the system, innumerable times. I also tried a completely fresh install of V40, but the problem persisted. Down-grading to V39 did resolve the issue.

Details of any modifications you have made to Batocera.

No modifications

Logs and data

It appears to only be an issue with V40, as everything worked properly on previous builds I've used (V38 and V39).

[jk7gr]

I second the issue. My DS4 v1 controllers are turning off automatically after a period of time being idle. In v39, the controller was disconnected from the system immediately. Now, in v40, it stays until I manually close the Bluetooth. What makes it worse is that if I turn back on the controller, 50% of the time is not reconnecting, and the other 50% reconnects but with different index (light blue color instead of dark blue). I downgraded for the time being back to v39.

[MizterB]

I have this same Pro Controller issue starting in v40 x86_64. Host is a 2014 Mac Mini.

[MizterB]

With my Pro Controller, when I turn it off, its controller icon continues to display in ES. If I then turn on a different controller, a second icon is displayed, but any controller activity on that second controller is applied to the first controller icon. Additionally, configgen correctly makes this second controller primary when launching a game.

In summary, it appears that the Pro Controller disconnects successfully, and ES is aware of the disconnection. It is only the visibility of the controller indicator icons does not reflect the change correctly.

[mvrk69]

I have the same issue on RPI5 with V40 and 8Bitdo Pro 2 controllers, on V39 was working fine.