Ryan Powell

@davidandreoletti If you could please check that this is resolved by #757 I will merge it

What you are doing is operating 2 devices via one. This isn't really possible as bonding stores the identity address of the devices so that they are recognizable at all...

@vodka-bears There is some possibility of a way to do what you are seeking but it would require some in-depth handling of the bonding mechanics that are outside the scope...

I don't think a PR for this would be appropriate here. What you can do is override the bonding functions and handle them for your needs though. The functions are...

Sorry I missed this. Your configuration is incorrect for passkey input, it should be: ``` NimBLEDevice::setSecurityIOCap(BLE_HS_IO_KEYBOARD_ONLY); /** passkey */ ``` if that still doesn't work then I suggest you try...

Thanks, seems espressif has added this strange new feature that is not in the official NimBLE code. Not sure if simply checking the IDF version will be enough to detect...

Thanks for the report, could you provide more logs and if possible a decode of the backtrace?

Thank you for the feedback, I will work on a fix shortly.

There is no provision the the BLE spec to advertise characteristics, only services.

You need to call `service::start()` after adding the characteristics. Please make sure there are no devices connected when you do this.