Problem when deleted Bonded master keeps bond

[Ignacio Lopez]

I am trying to manage the bonds as follows. I've defined the max bonded masters as 4 on my slave. When this list gets full, I delete a random bonded master on the slave (not the last one in use) after disconnection. This is working without any problem, but I have found the following issue. If a deleted bonded master keeps the bond with the slave and the slave starts advertising, the deleted bonded masters connects to the slave momentarily and then the slave disconnects. This is a problem because the deleted bonded masters still displays the slave as bonded but it is not able to keep the keeps the connection. I know that a solution is to delete the bond from the master but this may be confusion and difficult to interpret for the user. Is there any workaround for this issue?

Thank you.

[Ole Morten]

No, unfortunately for you, this is the way things are supposed to work. If one device loses bond information, it should require user interaction to create a new bond, and this can not really be handled automatically.

In general, I'd recommend you to try creating your device in such way so that this situation never occurs (for instance by requiring the user to manually delete a bond also on your device, or perhaps by just not using bonding at all), or at least doing some kind of effort to delete the least used Central or similar, instead of just deleting a random one.

[annapalu]

Hi, It's true also the contrary? I means, if i delete the bond information from the master, the slave connects momentarily and after few minutes disconnected . I must delete the bond information from the slave (so reload the soft device) to work, correctly.

thank you, Anna