I have been tested the codes both on Windows 10 and iOS, but I'm failed twice, here's my test code snippet

def __irq(self, event, data):
    if event == IRQ_CENTRAL_CONNECT:
        self.__conn_handle, _, addr = data
        self.__ble.gap_advertise(None)

        print("start pairing...")
        self.__ble.gap_pair(self.__conn_handle, bond=True, mitm=True, lesc=True)

On Windows, it will thrown OSError: ENOENT, and Bluetooth Control Panel show "driver error" to me.

On iOS, it will display the pairing dialog and complete the pairing operation correctly, but I cannot send keycode to the iOS text input area.

I want to know how to testing this commit in a right way, thanks~

Hi @Walkline80 this pr only adds the command to trigger pairing on the connected device, it doesn't include all the infrastructure to handle the pairing process; that's what the other two pr's linked in the top post are for.

They are still very much a work in progress however.

There's a lot of ongoing effort from myself and a couple of others to finish building a consistent pairing system that works on both stacks and most/all platforms. With our current schedule I hope to have basic pairing support finished within a couple of weeks.

@andrewleech thanks for your working, I also waiting for this for a long time, so, thanks again.

As far as I know, only iOS is a passive pairing system, which can be called by the development board to start pairing progress, but other systems such as Windows will actively initiate pairing, so I think there should be an irq callback to receive the pairing request from the central role, and then turn on passive pairing mode, is that true?

Superseded by #6651