Hi,
Our device is DA14682. I want the peripheral device only to accept our own central devices' connection request, but reject other devices. It seems the peripheral cannot read the central device name, is that true? And from this thread:https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/da14680-whitelist-ble, there is no whitelist for central device address in 14680? Is it still the same case for 14682?
If both of them are true, how can I achieve my goal easily?
Thanks!
Yingfen
Device:
Hi yingfen,
Yes, both DA14680/1 and DA14682/3 use the same SDK and there isn’t any API for whitelisting functionality in our current SDK. However. I ‘ll ask internally if we include whitelisting API in our future SDK release.
Thanks, PM_Dialog
Hi PM_Dialog,
谢谢你的回复。所以除了白名单,曲线ntly there is no existing internal function we can use to filter the central device, but have to do it externally?
Thanks,
Yingfen
Hi yingfen,
Can you please provide me more inputs regarding your requirement in order to understand what you are trying to accomplish? If I am not mistaken, the Peripheral is a DA14682 chip, but what about the Central device?
Regards, PM_Dialog
Hi PM_Dialog,
Both the peripheral and central devices are using the same da14682 chips. I wonder if there is a way that our peripheral can only connect to our central (by Mac address/device name or other methods are OK) devices, and reject other connection requests. We have mutiple centrals and multiple peripherals. One peripheral can connect to multiple centrals and vice versa.
If there are any existing demos, I can also read and follow them.
Thanks,
Yingfen
Hi yingfen,
If the Peripheral knows the BD Address of the Central, and vice versa, directed advertising could be achieved.But not sure, if this is possible when peripheral should be connected with multiple Centrals. I have to ask it internally and I will let you know. There isn’t any available demo for that.
Thanks, PM_Dialog
Hi PM_Dialog,
Thanks. I will wait for it.
Yingfen
Hi PM_Dialog,
Any updates since last week? It will be great if we don't need to check the central device manually.
Thanks,
Yingfen
Hi yingfen,
Apologies for the delay. White list is not supported in our SDK. Whitelist management API is not present in this release, so setting a filtering policy for advertising is not possible. I ‘m trying to figure out how you can do it…
Thanks, PM_Dialog
Hi PM_Dialog,
谢谢你的回复。We can wait for it as it's not an urgent task. But it will make our system more secure, so we also hope we can add the feature to it.
Thanks,
Yingfen
Hiyingfen,
Apologies for the delay, hope I can help. Each peripheral can populate an unique ID (encrypted or decrypted). Each central will scan over the air, and if I get’s the proper ID from the peripheral, then the connection should be achieved. You can also add authentication in your design.
Thanks, PM_Dialog
Hi PM_Dialog,
I think the solution is from the central side, not the peripheral side.
1. For the central side, we currently use the device name as a filter. But the solution you referred to seems to be better. Can you explain in detail about how to populate the unique ID for the peripheral? Or is there any demo?
2. But the question in this thread we want to ask is from the peripheral side: If an unknown central device wants to connect with our peripheral, how the peripheral knows it's unknown and rejects this connection request?
Thanks,
Yingfen
Hi Yingfen,
White-list feature is not supported for DA1468x. To do so, if you would like to be connected with a specific Central, you should reject the connection inside your application. You can check the Central’s BD address, so the application will decide either to reject or keep the connection. Regarding the ID, it could be placed into the advertising data.
Thanks, PM_Dialog