BLE passkey connection

RE: BLE passkey connection

T IJ — Fri, 17 Apr 2020 09:04:29 GMT

Well,it happens to be that I have a Nokia 8.1 as well, but I made a discovery...

When using the nRFConnect app:
First time connection equals to success, disconnecting and reconnecting are no issue except when I delete bonding information. Then there is no way for me to reconnect to the device without erasing everything.

When using standard Bluetooth from my phone:

I can connect, disconnect, delete bonding as much as I want and there is no problem. It all works flawlessly.

I'm currently still working on the client side to get it up and running, I'm just struggling a bit with the conversion from SDK15.2 in the example you handed over to SDK 15 which I'm using.

RE: BLE passkey connection

Simonr — Fri, 17 Apr 2020 08:53:02 GMT

Have you made sure to do a full flash erase of the DK, as this seems like the behavior of a DK with stored bonding information of a device that doesn't remember it. You can do a full erase by calling nrfjprog --eraseall for example.

Would the phone you have, by chance, be the Nokia 8.1. In that case, have one here on my end, so if you could upload your project I can test it here on my side and see if I'm able to reproduce/fix it. This is an alternative if erasing the DK flash doesn't help.

Best regards,

Simon

RE: BLE passkey connection

T IJ — Fri, 17 Apr 2020 06:23:06 GMT

I am using an android 10 Nokia phone with the nRFConnect app.

The situation is that I was able to connect the first time using my phone and the 52 dev kit, I could even disconnect and reconnect using the peer manager's bonding table. As soon as I deleted the bonding information on my phone I cannot connect to my device anymore. Even if I erase my 52 dev kit and reprogram it. It is only allowing my phone to connect if I program a completely different project first of my project I'm testing with.

When my project reaches the "PM_EVT_CONN_SEC_FAILED" event inside the peer manager, I get the peer ID from the connection handle and I flag it to be deleted from the bonding table, followed by sd_ble_gap_disconnect. In my ble_evt_handler under disconnect it then deletes the bond. Apparently my phone's credentials are still stored somewhere as I cannot reconnect afterwards.

The strangest part is that a friend of mine connected and disconnected his phone multiple times without a problem, same as my windows PC which is also works fine.

I shall finish the client side today and see if it has the same problems as my phone or not.

RE: BLE passkey connection

Simonr — Fri, 17 Apr 2020 05:24:03 GMT

Can you provide some more information? What phone and what application (on the phone) are you using? Some services, like for example passkeys, are not natively supported on most phones. I suggest using the nRFConnect app when connecting and see if that makes a difference

Is there any log messages at all that you get on either the phone or nRF debug log?

Best regards,

Simon

RE: BLE passkey connection

T IJ — Thu, 16 Apr 2020 11:39:55 GMT

Thank you, I will have a look.

At the moment, my device is showing me the passkey but after I enter the passkey on my phone I get a message saying connection failed, passkey incorrect

RE: BLE passkey connection

Simonr — Thu, 16 Apr 2020 11:37:04 GMT

Please take a look at this case, where my colleague has uploaded code examples for a central and peripheral (for SDK 15.0) that is able to connect and bond using a static passkey.

Best regards,

Simon

RE: BLE passkey connection

T IJ — Thu, 16 Apr 2020 11:14:55 GMT

Update:

Got it partially working, I'm currently only facing the problem that my server always responds with Failed to secure connection. Disconnecting.

Anyone know how to tackle this problem?