Whitelist vs Directed Advertisement (without peer manager)

[shreyab]

hi,

I'm using SDK 15.1.0 and s132

I have two custom boards one peripheral and one central. i don't want to use peer manager (according to requirements)

And i want the peripheral to connect to that one central only. so the way it should happen is ->

peripheral starts adv and central scans and they connect (without any directed adv or whitelist), now on some trigger peripheral needs to connect to the same central!

should i use whitelist for central or peripheral or should i use directed adv ??

PS: is there an example that uses whitelist without peer manager? it would really speed up my feature.

EDIT : i have multiple such pairs, so UUID based filter won't help in this case!

[droghio]

No need to use a peer manager. You can get away with the peers broadcasting undirected advertisements and in their advertisements you include a service UUID or some other identifier that the central can use to determine whether it should connect or not.

[shreyab]

hi droghio

thanks for the reply, what if i have multiple of such pairs ??

[droghio]

I still do not see an issue. Each peripheral can have an individual UUID, or another value (like a name) that the central will scan for.

I am not sure what you mean by multiple pairs though, as in one central should connect to one and only one peripheral?

[shreyab]

yes, i have multiple of these central and peripheral pairs and one central should connect to only one peripheral, the name or uuid based filter won't be practical in production though

[Kenneth]

How about allowing some kind of pairing by the end user? 

For instance ask the user to press a button and keep the two devices very close together, then both devices can go into a "pairing mode", where the devices will only connect with a peer that is very close by (measured by using rssi value in "pairing mode"). Then the devices can store the gap address of the peer to flash for future communication.

Best regards,
Kenneth

[shreyab]

hi Kenneth,

alright, thanks for your response, this future communication will essentially be implemented as a manual whitelist right?

[Kenneth]

Hi, 

Yes, the white list will have only one entry: the gap address of the peer you want to allow connection from.

Best regards,
Kenneth