On Client Power Loss or ESP32 Reset, BLE-Gamepad Stuck in False Connected Mode

[1stage]

When our Client device (using an ESP32-S3-WROOM) is turned off or it's ESP32 is reset, if our ESP32-BLE-Gamepad Server device has connected to it, no onDisconnect event gets sent, due to the abrupt power loss on the Client. The ESP32-BLE-Gamepad still shows as connected when the stats are polled...

21:49:59.867 -> BTLE Stats:
21:49:59.867 ->      StringAddress : 34:85:18:61:de:06
21:49:59.867 ->      NimBLEAddress : 34:85:18:61:de:06
21:49:59.912 ->       Peer Address : 34:85:18:61:de:06
21:49:59.912 ->    Peer ID Address : 34:85:18:61:de:06
21:49:59.912 ->    Peer ConnHandle : 1
21:49:59.912 ->  Peer ConnInterval : 7
21:49:59.912 ->   Peer ConnTimeOut : 600
21:49:59.912 ->   Peer ConnLatency : 0
21:49:59.912 ->           Peer MTU : 23

...yet there is no REAL connection. If the Client device is turned back on, it cannot re-connect with the ESP32-BLE-Gamepad, because it is already "connected" and not advertising its availability.

A power-cycle of the ESP32-BLE-Gamepad device fixes the issue... both devices re-connect with each other after both are power-cycled.

But is there a BLE-Gamepad function I can use to periodically validate the connection, and get it unstuck?

The Client device is using NimBLE as well, but not the Arduino build.