Closed c0d3h4x0r closed 2 years ago
it is no longer possible to interactively pair devices that require the user to type an uncommon/custom pairing code into MiSTer
pin code entring is supported by standard pair dialog. So if you pair something like keyboard, then you will see on dialog "enter code XXXXXX and then press enter".
If I have a BT gamepad that requires an unusual pairing pin (such as 7254
), there is no way for me to type that code into MiSTer, because the OSD does not attach stdin to the pairing script.
But the bigger issue (for me) is that I cannot initiate BT pairing from my gamepad anymore. I have to get up off my couch and go over to my TV stand and press and hold the physical button on the MiSTer to initiate pairing. Kind of a pain when I just want to pair a BT keyboard using the gamepad I already have connected.
I tried writing a thin wrapper script around btpair
that I can launch via the OSD's Scripts
menu, but that doesn't work, because btpair
is designed to run forever (until the user hits CTRL+C). The OSD appears to trap/eat/block CTRL+C so that any script it launches this way cannot be interrupted, so btpair
runs forever and cannot be terminated when launched via the Scripts
menu.
Ever since the Bluetooth stuff was rewritten a few months ago, this script has been broken (contains reference to
pair-agent
, which no longer exists). This means it is no longer possible to interactively pair devices that require the user to type an uncommon/custom pairing code into MiSTer, and it is no longer possible to initiate Bluetooth pairing using a game controller. This script needs to be fixed or replaced by equivalent functionality.