Combined scan filtering

RE: Combined scan filtering

Brus — Mon, 15 Jun 2020 07:19:04 GMT

Thank you very much. That was the point!
Filtering information must be on the advertising packet. Scan response information are not useful in the filtering procedure.

RE: Combined scan filtering

hmolesworth — Fri, 12 Jun 2020 19:16:34 GMT

If the UUID is in the scan response and not the advertising packet with the name then the match will fail; see this post for details get-device-name-from-filter-match-event

RE: Combined scan filtering

Einar Thorsrud — Fri, 12 Jun 2020 17:32:59 GMT

Hi,

I have not been able to reproduce this. Using the Bluetooth: Central UART sample as a reference with only the following modifications, it works as expected on my side when testing on an nRF52 DK.

devzone.nordicsemi.com/.../7446.main.c.diff

devzone.nordicsemi.com/.../prj.conf.diff

Log output:

*** Booting Zephyr OS build v2.1.99-ncs1  ***
Starting Bluetooth Central UART example
I: 6 Sectors of 4096 bytes
I: alloc wra: 0, fd8
I: data wra: 0, 1c
I: No ID address. App must call settings_load()
Bluetooth initialized
UART initialized
Scan module initialized
NUS Client module initialized
Scanning successfully started
Filters matched. Address: c6:a3:38:69:c3:45 (random) connectable: 1
...

RE: Combined scan filtering

Brus — Thu, 11 Jun 2020 14:26:44 GMT

I forgot mention that. I'm using NCS v 1.2.0.

RE: Combined scan filtering

Einar Thorsrud — Thu, 11 Jun 2020 14:14:53 GMT

Hi,

I do not see that you are missing anything. It should work. I have not been able to test yet but will do so.

Are you using an NCS release? If so, which?