The bonding function does not take effect

RE: The bonding function does not take effect

Edvin — Fri, 05 Jul 2024 21:16:48 GMT

Hello,

Whenever the connection is encrypted, you should see the event:

PM_EVT_CONN_SEC_SUCCEEDED

in pm_handler_pm_evt_log() (or in pm_handler_on_pm_evt, but this one doesn't log anything itself).

Is that what you were asking for, or did I misunderstand?

Best regards,

Edvin

RE: The bonding function does not take effect

Mark — Thu, 04 Jul 2024 02:40:33 GMT

Hello,

When pairing, "case BLE_GAP_EVT_AUTH_STATUS:" is called in the central and "case

BLE_GAP_EVT_AUTH_KEY_REQUEST:" is called in the peripheral.

But when bonding, neither "case" will be called.

So I want to know what is going to be called after the bonding because I want to do something after the full connection and

the "case BLE_GAP_EVT_CONNECTED" is too early to meet my requirements.

RE: The bonding function does not take effect

Edvin — Wed, 03 Jul 2024 21:44:50 GMT

Hello,

It is possible to bond with one device and still connect to new devices. However, it is possible (and the typical use case) to limit the possibility for new devices to connect after you are bonded with one (or more) devices. This is done by advertising with a whitelist. Please check out the ble_app_gls example for how to do this.

Best regards,

Edvin