My OSMC bluetooth pairing of 8Bitdo FC30 PRO controller -- doesn't re-connect when controller powered on

I have loaded OSMC and retrOSMC on my Raspberry Pi 3 device. I have an 8Bitdo FC 30 Pro that works well with my setup. I’m running into issues using the “My OSMC” -> Networking -> Bluetooth to pair the controller to the Pi.

The first time I pair the controller, osmc connects to the 8Bitdo device, and everything “just works.”

However, when I am finished with a session, I power off the 8Bitdo device (using it’s power button). When I am ready to use the device again, I power it on, and it does NOT “re-connect” with the osmc box.

The session below shows how to pair the device using the command line. When I pair the device this way, the device always re-connects whenever it is powered off and back on.

osmc@osmc1031:~$ bluetoothctl
[NEW] Controller B8:27:EB:56:3F:11 osmc1031 [default]

[bluetooth]# power on
Changing power on succeeded

[bluetooth]# scan on

Discovery started
[CHG] Controller B8:27:EB:56:3F:11 Discovering: yes
[NEW] Device 5C:9A:10:AF:08:B4 5C-9A-10-AF-08-B4
[NEW] Device E4:17:D8:C3:00:05 8Bitdo FC30 Pro

[bluetooth]# pair E4:17:D8:C3:00:05

Attempting to pair with E4:17:D8:C3:00:05
[CHG] Device E4:17:D8:C3:00:05 Connected: yes
[CHG] Device E4:17:D8:C3:00:05 Modalias: usb:v2DC8p3810d0100
[CHG] Device E4:17:D8:C3:00:05 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device E4:17:D8:C3:00:05 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device E4:17:D8:C3:00:05 Paired: yes
Pairing successful
[CHG] Device E4:17:D8:C3:00:05 Connected: no

[bluetooth]# trust E4:17:D8:C3:00:05

[CHG] Device E4:17:D8:C3:00:05 Trusted: yes
Changing E4:17:D8:C3:00:05 trust succeeded

[bluetooth]# connect E4:17:D8:C3:00:05

Attempting to connect to E4:17:D8:C3:00:05
[CHG] Device E4:17:D8:C3:00:05 Connected: yes
Connection successful

[8Bitdo FC30 Pro]# quit
[DEL] Controller B8:27:EB:56:3F:11 osmc1031 [default]
osmc@osmc1031:~$

Please let me know what I can provide in the way of logs, etc. to help troubleshoot / fix this issue with My OSMC.

Thank you for OSMC!
-Ryan