RE: Available 16-bit UUIDs

José Villanueva — Tue, 24 Oct 2017 22:17:51 GMT

Thanks endnode, now I know they wanted me to doubt about my researches. Also, I agree with you in that they should generate their own 128-bit UUID which as you say is 'free' and would help them comply with their BT SIG certification, which as far as I know, they are just starting the process to get one. I should talk to them again and make them understand how much respecting even the smallest detail of the BT SIG Specifications accounts for having a quality device in every aspect.

RE: Available 16-bit UUIDs

endnode — Tue, 24 Oct 2017 20:19:14 GMT

You were right and them wrong: all 16-bit UUIDs mapped to default 128-bit BT SIG UUID base are restricted in the Bluetooth world to GATT objects specified by the group and they are not "free to use". Last 512 numbers in that space (0xFE00..0xFFFF) are allocated to organizations/corporations but they are all subject of registration and fee. Indeed you might disrespect this rule and hard to say if anything wrong happens... but formally you shouldn't do it. It's pretty clearly visible in these two UUID lists on BT SIG page: 16-bit UUIDs for members and 16-bit UUIDs for SDOs. So your customer or supplier is most probably violating BT SIG certification of their device (if they have any) and as it is so easy and "free of charge" to generate custom 128-bit UUID base it's pretty lame not doing it.