Failure to broadcast 32-bit UUID!

RE: Failure to broadcast 32-bit UUID!

user75734 — Mon, 30 May 2022 10:25:38 GMT

This case is nearly 3 years old at this point. I see that you have created a ticket of your own already. The appropriate engineer will be assigned to it, and you should get a reply there soon.

Best regards,

Simon

RE: Failure to broadcast 32-bit UUID!

user53608 — Mon, 30 May 2022 09:17:47 GMT

We meet the same problem.The advtising data is 050501020304.That mease

advlen=0x05,

advtype=0x05

advdata=01020304.

we want to set the 32-bit uuid in advtising data.But it is failue to call functon sd_ble_gap_adv_set_configure return NRF_ERROR_NOT_SUPPORTED.So we want to konw if the softdevice suppot 32-bit uuid in advtising data?

RE: Failure to broadcast 32-bit UUID!

user75734 — Mon, 15 Jul 2019 09:13:49 GMT

Hi Giannis

16 and 32 bit UUIDs should only be used if they're assigned by the Bluetooth SIG, companies or individuals should not randomly use them. When used in GATT, the 32 bit UUID can't be used and must be converted to a 128 bit UUID. This example explains how to add a 128 bit UUID. This post explains more about 32 bit UUID usage.

Due to the summer holidays in Norway, our support team is understaffed this week, and delayed replies must be expected. Sorry for the inconvenience!

Best regards,

Simon