Do mass-produced Beacons have unique mac-address?

RE: Do mass-produced Beacons have unique mac-address?

Chao Ming — Tue, 25 Aug 2020 14:10:44 GMT

Aha, I got it.

Everything seems to okay now. Thanks for your help.

RE: Do mass-produced Beacons have unique mac-address?

Einar Thorsrud — Tue, 25 Aug 2020 11:15:43 GMT

You are not comparing the same things. nRF Connect for Android displays the address, but that is not available to the app from the BLE API on iOS. The data you see in the screenshot from iOS are parts of the advertisement packet payload, not the address. There is absolutely no way to obtain the address on iOS (unless the iOS Bluetooth API is updated to support it, and that would be up to Apple).

RE: Do mass-produced Beacons have unique mac-address?

Chao Ming — Mon, 24 Aug 2020 13:22:00 GMT

Please have a look at the screenshots.

RE: Do mass-produced Beacons have unique mac-address?

Einar Thorsrud — Mon, 24 Aug 2020 10:26:30 GMT

Hi,

How do you see this? Can you elaborate and show screenshots?

RE: Do mass-produced Beacons have unique mac-address?

Chao Ming — Mon, 24 Aug 2020 08:46:21 GMT

Oh, sorry, one more thing to ask.
The 6-byte mac-address is different in android and iOS devices for the same beacon.
Could you tell me the reason?

RE: Do mass-produced Beacons have unique mac-address?

Chao Ming — Mon, 24 Aug 2020 08:24:23 GMT

Thanks for letting me know.
I was thinking to generate a random device name if the mac-address of all produced beacons with the same frimware will not unique.

It will save my work a lot.

Thanks.

RE: Do mass-produced Beacons have unique mac-address?

Einar Thorsrud — Mon, 24 Aug 2020 07:10:31 GMT

Hi,

By default, the SDK examples use the address from FICR, which is randomly generated and (in practice) unique. So you do not need to modify the firmware in order to get unique addresses on all y our beacons. This old post is equally valid for the nRF52.