RE: Filter mac with only two bytes

AP1 — Wed, 21 Feb 2024 08:54:25 GMT

Hi Edvin Thanks for your quick reply based on your suggestion now we are able to get the required devices

RE: Filter mac with only two bytes

Edvin — Tue, 20 Feb 2024 14:31:55 GMT

Hello,

The easiest way to do this is to not use the built in filters (because they would require the entire address), but just add the BLE_GAP_EVT_ADV_REPORT event to your ble_evt_handler() in main.c. It should start occuring when you start scanning. When it does, you can use this event to check the address:

        case BLE_GAP_EVT_ADV_REPORT:
            NRF_LOG_INFO("received adv_report from %02x:%02x:%02x:%02x:%02x:%02x", p_ble_evt->evt.gap_evt.params.adv_report.direct_addr.addr[0],
                                                                                    p_ble_evt->evt.gap_evt.params.adv_report.direct_addr.addr[1],
                                                                                    p_ble_evt->evt.gap_evt.params.adv_report.direct_addr.addr[2],
                                                                                    p_ble_evt->evt.gap_evt.params.adv_report.direct_addr.addr[3],
                                                                                    p_ble_evt->evt.gap_evt.params.adv_report.direct_addr.addr[4],
                                                                                    p_ble_evt->evt.gap_evt.params.adv_report.direct_addr.addr[5]);
            break;

And then do whatever you like based on the address, such as connecting, store advertising data or whatever you want to do.

If you dig deep into the scan filters in nrf_ble_scan.c, you will find that it also just use these BLE_GAP_EVT_ADV_REPORT events, and do a bunch of filtering based on the incoming advertisement packets, so I think just checking a few bytes in the advertising packet using this event in your main ble_evt_handler() is easier than starting to modify the scanning module from the SDK.

Best regards,

Edvin