Help with Pairing for non-display device

[Jon Trausti]

Hi,

I recently started upgrading an nRF chip on old SDK to the latest nRF Connect. The device has only one button and currently uses a static passkey (written on the device) while advertising constantly.

I want to make the following updates:

1. Limited advertising (advertise only when requested for a set period of time) - This works in my proof-of-concept.
2. Confirm pairing using a button press or another unique method.
3. Remove the static passkey.

I am able to send a feedback from the device to the nRF chip; however, when attempting to skip the static passkey, I do not achieve security level 3/4 during pairing. Is it possible to configure the chip to acknowledge that the pairing is confirmed/accepted using the button? What approach would you advise?

Best regards,

[Amanda Hsieh]

Hi, 

You can take a look at Bluetooth: Peripheral UART. 

Regards,
Amanda H.

[Jon Trausti]

Thank you Amanda, this seems to be what I'm looking for. I'm still having slight problem applying it to my setup.

I'm not receiving the .passkey_confirm callback, its seems my project is expecting me to input the random passkey generated. I'm getting the .passkey_display callback. 

What can be the cause of this, we are not using NUS if that is something, here is copy of my poc .cfg file 

[Amanda Hsieh]

Hi,

Is the application based on the Bluetooth: Peripheral UART? If so, to confirm pairing or bonding, press Button 1 on the device and accept the passkey value.

We are currently understaffed due to the summer vacation period, so delayed replies must be expected. I am sorry about any inconvenience this might cause.

-Amanda H.

[Jon Trausti]

Hi Amanda,

I'm just grateful for any assistance, I do understand it might take some time!

We are trying have this in our own project using the Peripheral UART example. These are the callbacks that we define: 

We send the "button feedback" from a different MCU, through the SPI interface. But as the "auth_passkey_confirm" is never called, the button functionality isn't doing anything at the moment - the implementation is similar to the UART example. 

The only thing I can see quickly is that I'm not using the NUS services. 

Would it help if I sent you the project?