Bluetooth pairing fails when running sample peripheral_cts_client

[Burt]

I am trying to run the sample using NCS v2.5.0. This is what happens on the console when I try to connect from the dongle, when running the Test Procedure:

The discovery procedure succeeded
Security failed: E3:FE:4E:E0:6D:C5 (random) level 1 err 4
Pairing failed conn: E3:FE:4E:E0:6D:C5 (random), reason 4
Disconnected from E3:FE:4E:E0:6D:C5 (random) (reason 0x16)

Please advise. I don't have much BLE experience. Thank you.

Burt Silverman

[Burt]

I have solved the problem of the time not getting to the client. It was the user interface on BLE App. When you fill in the 10 byte Time, you have to press the check mark--I'm not sure if it is after or before hitting the Write button--regardless, the poor instructions in the documentation do not describe the user interface properly--no mention is made about the check box.

In order to not get screwed up with double bonding I added

CONFIG_BT_SMP_ALLOW_UNAUTH_OVERWRITE=y

to my prj.conf. Please advise of any other possibilities that will protect me from having to re-flash. Also, please have the documentation team correct the instructions in the documentation to make them idempotent. I should be able to run through the test procedure as written multiple times without a severe error that requires re-flashing. Thank you.

Burt Silverman

[Susheel Nuguru]

Burt said:

Please advise of any other possibilities that will protect me from having to re-flash.

Maybe create a button event if your board has a button to clear out all or some bonds when needed? I am not sure, there are many ways to do it but that depends on your product and application.

Keep one identity for stable testing, or set CONFIG_BT_ID_MAX and switch identities to repeat tests.

[Burt]

Thank you, Susheel. I think I have to learn and get a better understanding of how to use the BLE Application to check for bonds and/or remove bonds on one or both sides of the connection. I know there is online documentation for the BLE Application--it seems like it was a bit sketchy in this area, but I will have to go back and check. 

Burt