[nRF Connect SDK] Connect to iOS with mac address

[Tim Hwang]

Target nRF52832(nrf52dk_nrf52832)
SDK NCS v2.0.0


Hello.
Recently I know that iOS cannot get BLE mac address by scan, but my project requires connection based on BLE mac.
I add bt mac adversting data using BT_DATA_LE_BT_DEVICE_ADDRESS but it failed.

I believe you have guide for iOS connection based on BLE mac.
How can we make it? Or What is good way to add ble mac address into adv data?

Thanks in advance.

[Tim Hwang]

+addition

static const struct bt_data ad[] = {
BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
BT_DATA(BT_DATA_LE_BT_DEVICE_ADDRESS, local_bda, 6),
BT_DATA_BYTES(BT_DATA_UUID128_ALL, BT_UUID_BUS_VAL),
};

I could add ble mac at adv data, but it seems iOS does not show those information except for service UUID.
Can you give me any guide?

[AHaug]

Hi,

It should be possible to use DEVICEADDR (i.e MAC address) to identify the device as well as IRK and RPA 

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/connectivity/bluetooth/api/gap.html#c.bt_id_create

You can have a look at this relevant sample: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/connectivity/bluetooth/bluetooth-dev.html#bluetooth-application-example

Here is a colleagues comment on public address vs. random static address that you may find useful:

"There is no need to use public address type anywhere no, the random static address type is by far the most used (I don't think this address type was available in BT classic). We have seen very few questions on using public address type (only some companies use them for historic reasons coming from BT classic products, and likely have already purchased/registered public address types that can be used).

So I suggest to stay with random static address type, simply avoid the "hazzle" of registering with IEEE and also the logistic problem of assigning them to products in production.

All nRF devices come with a random static address generated during Nordic production test and programmed to FICR."

 

Kind regards,
Andreas

[Tim Hwang]

Thanks for updating.

First of all, I have to use public mac because mac is printed the cover of product. Customer should use it.

And I could manage to insert ble mac into adv data.
I'm waiting for my customer's reply.

I'll ask more request then. Thanks anyway!

[AHaug]

Noted! That explains the use for public mac. Thank you for elaborating.

Then I would suggest adding the MAC into the adv data as you mention and let the central decide if they should connect to that based on the identity created from the mac address or from the address advertised

Kind regards,
Andreas