• State Verified Answer
  • Replies 8 replies
  • Subscribers 75 subscribers
  • Views 221 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 346086
Options

Delete one side bond info,Cannot pair again

Martin Evans

Dear Nordic Team,

I am programming with ncs V2.9.0 and nrf52833.

There is a trouble happend when one side delete the pairing info,but the other not.

Peripheral has already forgot the info,But central still maintain it.And then central side will report this LOG.

I want to pair with it again WHENEVER WHATEVER happened.HOW I can do to avoid it?

Best regard.

Martin

Parents
  • 0

    Hi Martin

    This is the expected behavior when doing bonding with BLE. If one device still remembers the bonding it won't be able to bond with the device that has deleted the bonding information again as it still thinks it is bonded. This is part of the Bluetooth LE specification.

    If you add a way to erase the bonds on the other side either upon a disconnect or upon a failed connection/bonding attempt. Alternatively, don't erase the bonding info from one side in the first place.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi Simonr,

    I have never delete bonded info at any side,but our product happend.

    So I have to find out one way to solve or aviod this phenomenon.Do there any suggestions?

    Thanks

    Best regard

    Martin

  • +1 in reply to Martin Evans
    Martin Evans said:
    I have never delete bonded info at any side,but our product happend.

    I'm not sure I understand this statement, can you explain. Which side is deleting the bonding info in the first place? 

    If you add a way to erase the bonds on the other side either upon a disconnect or upon a failed connection/bonding attempt that should be a way around this. The other alternative is to not have bonding if you don't need the security features it provides in your product.

    Best regards,

    Simon

  • 0 in reply to Martin Evans

    If you already shipped the products it will have to be a recall.

    The BTLE examples leave out some functionality in order to make the code easier to understand and learn how it works.

    For real world products you need to add code that for example handles pairing mode and can delete bonds in specific situations like the one described above. This has to be an explicit user interaction here.

    HID devices require correct handling of bonding information as these devices always have security implications...

Reply
  • 0 in reply to Martin Evans

    If you already shipped the products it will have to be a recall.

    The BTLE examples leave out some functionality in order to make the code easier to understand and learn how it works.

    For real world products you need to add code that for example handles pairing mode and can delete bonds in specific situations like the one described above. This has to be an explicit user interaction here.

    HID devices require correct handling of bonding information as these devices always have security implications...

Children
Related
Terms of service