[nRF Connect SDK](Urgent)Re-bonding with Android

RE: [nRF Connect SDK](Urgent)Re-bonding with Android

Einar Thorsrud — Tue, 28 Jun 2022 06:21:29 GMT

I see. The fact remains that the bond has to be deleted on the Android device if deleted on the nRF, but other than that what you describe is fine. You can use bt_set_bondable() to enable or disable bonding, and you can use bt_conn_set_security() to encrypt a link (and start bonding if a bond does not already exist).

RE: [nRF Connect SDK](Urgent)Re-bonding with Android

Tim Hwang — Mon, 27 Jun 2022 23:54:42 GMT

1. Our usage requires lots of Android(+iOS) with one BLE device, so that BLE can delete its pairing.
2. As this case subject, I want to make bonding again without user action. If security_changed() have error (not 0), I call bt_conn_set_security(). BLE initiate bonding process. I want double check if it is fine.

Thanks.

RE: [nRF Connect SDK](Urgent)Re-bonding with Android

Einar Thorsrud — Mon, 27 Jun 2022 15:49:45 GMT

Hi,

Generally, if the bond is delete on the nRF and not deleted on the phone, any subsequent reconnections will fail and the only way to solve this is to also delete the bond on the phone. To avoid this, try to avoid having to delete bonds on the nRF (increase the maximum amount of bonds to a level you will normally not reach, provided you have enough flash for it).

[quote user="Tim Hwang"]

I found that if err is not 0, I call following two functions then BLE initiate pairing process again.
Is it good sequence? Or let me have good solution.

bt_set_bondable(true);
bt_conn_set_security(conn, BT_SECURITY_L4);

[/quote]

I do not see how this would fix the issue you described in your initial post, but perhaps there is something I am not getting. Perhaps you can elaborate?

RE: [nRF Connect SDK](Urgent)Re-bonding with Android

Tim Hwang — Mon, 27 Jun 2022 05:11:01 GMT

I found that if err is not 0, I call following two functions then BLE initiate pairing process again.
Is it good sequence? Or let me have good solution.

bt_set_bondable(true);
bt_conn_set_security(conn, BT_SECURITY_L4);