When the Aquarius+ is turned off or it's ESP32 is reset (SHIFT+CTRL+ESC), if an Aq+ Gamepad Server device has paired and is connected to it, no onDisconnect event gets sent back to the Aq+ Gamepad, due to the abrupt power loss on the Aquarius+. The Aq+ 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 Aquarius+ is turned back on, it cannot re-connect with the Aq+ Gamepad, because it thinks it is already "connected" and not advertising its availability.
A power-cycle of the Aq+ Gamepad fixes the issue... both devices re-connect with each other after both are power-cycled.
Can this be fixed so a check happens automatically?
When the Aquarius+ is turned off or it's ESP32 is reset (SHIFT+CTRL+ESC), if an Aq+ Gamepad Server device has paired and is connected to it, no onDisconnect event gets sent back to the Aq+ Gamepad, due to the abrupt power loss on the Aquarius+. The Aq+ Gamepad still shows as connected when the stats are polled...
...yet there is no REAL connection. If the Aquarius+ is turned back on, it cannot re-connect with the Aq+ Gamepad, because it thinks it is already "connected" and not advertising its availability.
A power-cycle of the Aq+ Gamepad fixes the issue... both devices re-connect with each other after both are power-cycled.
Can this be fixed so a check happens automatically?