Hi. I'm using a nRF52840 chip and have a flavour of Proximity profile example being used with some custom services and characteristics that have been added. All is good in Android but for iOS because I can't see UUID's the app developers are asking if we can somehow embed serial number (10digits) somewhere so that they can see device without connecting.
I am evaluating the following options but have limited experience with iOS beacons -->
1) Embed 10digit serial number in a 128bit UUID in a new service/characteristic.
2) Advertisement packet - Add serial number here. But on nrfconnct on ios I can only see the minors of services and my company name. Is the advertisement data normally visible using proximity example on iOS to app?
I am trying to study if I need iBeacon or not. I rather use existing code for being very close to production but do I definitely need an iBeacon to have advertisement data visible to iOS app "without" connecting.
3) If ibeacon is necessary then other than company ID is that a major change to the proximity example code?
My application is basically beacons which are only connected to when I need to blink some LED's or so but mainly we monitor beacons and their RSSI.
Sorry for the delayed response here.
I don't see why you would need to go for an iBeacon solution here. The advdata that is displayed depends on which advertisment data you choose to add.
1. This should be possible. Note that you have limited space in a single advertisement packet and the 128bit UUID will consume a lot of that.
You can take a look at the ble_app_uart example, which adds a 128bit UUID to the advertisement packet. You can see a picture of how the ble_app_uart looks in nRF Connect for iOS below:
2.Mabye it could be an option for you to add your serial number to the manufacturer specific data?
Did a quick modification to the ble_app_proximity example and added the manuf. spec. data:
Best regards, Joakim
Many thanks Joakim. Option 2 worked well for me. :)