Whitelist Paradox

[Andrew]

Looking at the documentation here (for SDK 11, s130)...

infocenter.nordicsemi.com/index.jsp

I see two conflicting statements

These APIs require that the peer is connected before the procedures can be requested.

Then later with respect to the whitelist creation function

Also, if this routine is called when a connection exists with one or more peer devices, those connected devices are not added to the whitelist.

How is this possible and/or useful?

[tesc]

Hi,

The dm_whitelist_create() function does not require a connection, but the other two functions does. This was not updated after the introduction of dm_whitelist_create().

dm_whitelist_create() builds a whitelist containing bonded devices. If a bonded device is already in a connection it does not make sense to put it on the whitelist, because the whitelist is used only for setting up connections. Adding a connected device to the whitelist would make whitelisting use more resources for no benefit.

Regards, Terje

[Andrew]

This assumes that the whitelist is dynamic, right? If it is created every time just before there is a scan, then you can build the whitelist just-in-time and only for devices not yet connected. Yes?

[tesc]

That is correct.