Service UUID advertised by non-connectable device

RE: Service UUID advertised by non-connectable device

Adam Heinrich — Fri, 18 Dec 2015 14:01:39 GMT

Thank you!

RE: Service UUID advertised by non-connectable device

run_ar — Fri, 27 Nov 2015 09:51:51 GMT

Yes, there are some limitations using ibeacon. But as EricS says you are allowed to advertise a 128bit custom uuid, so that is possible.

RE: Service UUID advertised by non-connectable device

Adam Heinrich — Thu, 26 Nov 2015 06:39:37 GMT

I am including 20B of custom data (4B manuf. specific + 16B data) into scan response. I think I can't use iBeacon as the iOS API does not allow me to work with its raw advertising data.

RE: Service UUID advertised by non-connectable device

run_ar — Wed, 25 Nov 2015 19:28:53 GMT

What else are you advertising? Have you considered using iBeacon technology instead (Since this can be received when the app is in the background)?

RE: Service UUID advertised by non-connectable device

Eric Stutzenberger — Wed, 25 Nov 2015 18:20:55 GMT

Hi Adam,

This is perfectly fine to do. Per the Bluetooth Spec, you are allowed to advertise a 128-bit custom UUID. In addition, you are essentially performing the Broadcaster role since the advertising packets are sent as non-connectable. iOS will report the advertising packets to you. In fact, this is very similar to how their iBeacon (and other Beacon) technology works. The main difference is that you are simply doing normal advertisements where Beacons have a specific Beacon packet structure.

Hope this helps,

Eric