Identify Bonded Devices through Advertisement

RE: Identify Bonded Devices through Advertisement

Susheel Nuguru — Thu, 21 May 2015 09:03:45 GMT

Whitelisting can be enabled both on central and peripheral. Central will use it for selective scanning and advertiser will use it for selective acceptance on connection/scan requests from central. Please look into this post.

RE: Identify Bonded Devices through Advertisement

danbujak — Wed, 20 May 2015 19:54:19 GMT

I am using the Nordic motherboard for now, but ultimately it will be an Android device. I am able to bond with a device, and store that bonding information (based on multilink example), but I can't figure out how to add the IRK of a bonded device to the whitelist for future connections.

I think I might be misunderstanding how whitelisting works. Is the whitelist implemented on the central or peripheral? I was under the impression that the central would add a peripheral to its whitelist after bonding and then the devices would be able to connect when the central is doing selective scanning. However all the examples I see seem to implement the whitelist on the peripheral side.

RE: Identify Bonded Devices through Advertisement

Susheel Nuguru — Sun, 17 May 2015 09:05:28 GMT

you can add the previously bonded devices in the whitelist (based on IRK if its IOS device) of the central device. This way the device can be configured to send a connect request when any advertisement packet with the device address in the whitelist is detected.

Search tis forum for whitelisting and you will find tons of information regarding it.