RE: Pairing mode - Disable bonded connections and allow non-bonded only

Ferencz Dominguez — Wed, 08 Jul 2020 21:18:27 GMT

Hi Edvin,

I solved the problem. First I did was to disable the connect_if_match during the scan_init() function.

Then I was able to use sd_ble_gap_connect() during the NRF_BLE_SCAN_EVT_FILTER_MATCH and NRF_BLE_SCAN_EVT_WHITELIST_ADV_REPORT depending if I have the whitelist active or not and if the MAC address scanned is in the whitelist or not.

Thanks for the help

RE: Pairing mode - Disable bonded connections and allow non-bonded only

Edvin — Wed, 08 Jul 2020 14:34:10 GMT

Hello,

So what you want is basically a blacklist, right? This is not something that is part of the softdevice, but it is possible to do something like this from your application

What you have to do is to disable the whitelist when you want to scan for new devices.

When you scan without a whitelist, you will get all the advertising reports in the event called BLE_GAP_EVT_ADV_REPORT. It is this event in nrf_ble_scan.c that usually decides whether or not to connect. You can see there is a lot of filter stuff in the nrf_ble_scan_on_adv_report() function called in this event. It boils down to setting is_filter_matched = true or false.

So if you are looking for a particular UUID you can use this filter as before. Look inside the function nrf_ble_scan_connect_with_target() function. You see there is a p_scan_ctx->connect_if_match. If this is set to true, it will try to connect. See if you can use this to not connect automatically, but check the address, whether it is present in the whitelist (that is currently not active) before you call sd_ble_gap_connect.

As a helper, you see that this function (nrf_ble_scan_on_adv_report()) will also generate the event NRF_BLE_SCAN_EVT_FILTER_MATCH() that is forwarded to the p_scan_ctx->evt_handler. Use this event to see only devices that has a filter match, and then decide whether you want to connect or not.

Best regards,

Edvin