static passkey s132

RE: static passkey s132

michaeld — Mon, 01 May 2017 12:18:34 GMT

Great post!

RE: static passkey s132

jroorda — Thu, 23 Mar 2017 14:58:21 GMT

Yes, it is!

RE: static passkey s132

Petter Myhre — Thu, 23 Mar 2017 14:49:04 GMT

Thanks for the update. So this is resolved?

RE: static passkey s132

jroorda — Thu, 23 Mar 2017 13:50:09 GMT

Thanks for the replies! Peter, I have set those parameters. Today I found out that the problem lies in my Android phone and not in my software. My Phone, a HTC One, does not handle the bonding correct. Upon bonding the OS does not generate a popup to fill in the passkey. Instead it indicates that the devices are bonded, but in reality they are not. Because when the Phone says bonded and I try to read a passkey protected characteristic it takes a long time and after a while disconnects from the device. When another phone is used, in this case a LG Nexus 5 it works as expected.

RE: static passkey s132

Petter Myhre — Thu, 23 Mar 2017 13:34:16 GMT

I don't understand, the defines I mentioned has nothing to do with sd_ble_opt_set().

RE: static passkey s132

Petter Myhre — Thu, 23 Mar 2017 12:49:35 GMT

Connect is connect, after you have connected you can pair and optionally bond.

Have you set that you want to bond, and that you require MITM protection?

#define SEC_PARAM_BOND                 1                                           /**< Perform bonding. */
#define SEC_PARAM_MITM                 1                                           /**< Man In The Middle protection required. */

Have you set the IO capabilites to display only?

#define SEC_PARAM_IO_CAPABILITIES      BLE_GAP_IO_CAPS_DISPLAY_ONLY                /**< Display I/O capabilities. */