About Peer Manager (Erase bond, limit bond devices, Service)

[John_Doe]

Hi Nordic,

I am using SDK 12.3.0 and S130 2.0.1. I would like to ask some questions about Peer Manager.

1. I want to erase all bond when I press a button. Do I just need to put pm_peers_delete() in button event handler? What is the proper procedure to delete all bond information when device is connected? Does the device need to be disconnected first? Do we need to call peer_manager_init() again?

2. I would like to limit the number of bond using pm_peer_count(). For example, when the number of bond reach 2, I would like my central would only pair with new peripheral instead of pairing + bonding. Where do I need to set this condition? pm_conn_secure() is the function to start bonding and I put it in case DISCOVERY_COMPLETE of service event handler. Do I need to call other function if I just need pairing?

3. Can Peer Manager save the bonded service in order to skip service discovery if connect to previous bonded device? How to implement this feature?

Thank you for your patience.

[John_Doe]

Anybody?

[haakonsh]

1. You can call pm_peer_delete, but you need to disconnect first. There's no need to re-initialize the library afterwords. From API docs:
   
   Warning!
   Use this function only when not connected or connectable. If a peer is or becomes connected or a PM_PEER_DATA_FUNCTIONS function is used during this procedure (until the success or failure event happens), the behavior is undefined.
   
   
2. You need to call pm_sec_params_set with a ble_gap_sec_params_t where 'bond' is set to '0' before you can call pm_conn_secure. And pm_peer_count does indeed return the number of bonds stored in flash, so it can be used as you propose. 
3. I believe you will need to call pm_peer_data_remote_db_store and pm_peer_data_remote_db_load.