Custom uuid in nRF Connect

RE: Custom uuid in nRF Connect

bjorn-spockeli — Mon, 16 Oct 2017 12:34:21 GMT

You cannot create your own custom 16-bit UUIDs as these are reserved for the official Bluetooth SIG Services. You need to create 128-bit UUIDs for custom services and characteristics.

RE: Custom uuid in nRF Connect

Mehdi Chafik — Mon, 16 Oct 2017 12:28:38 GMT

I add a screenshot, you can see the json file and the nRF Connect not translate the Service and Characteristic UUID to display the name.

RE: Custom uuid in nRF Connect

bjorn-spockeli — Mon, 16 Oct 2017 12:06:12 GMT

So the custom UUIDs does not show up in the drop down menu in the Bluetooth Low Energy app when you try to set up a server?

RE: Custom uuid in nRF Connect

Mehdi Chafik — Mon, 16 Oct 2017 11:39:50 GMT

If you recheck my message, I said: "I restart the application on each change to the json file"

RE: Custom uuid in nRF Connect

bjorn-spockeli — Mon, 16 Oct 2017 10:41:45 GMT

Hi Mehdi,

the structure of the uuid_definitions.json file will not be checked upon startup of the Bluetooth Low Energy application in nRF Connect. You will get an error if there is an invalid UUID when you try to add a custom service/characteristic/descriptor.

In order for the changes to take affect you need to re-connect the adapter or reload the Bluetooth Low energy application using CTRL+r, this is stated in Chapter 11 in the nRF Connect Bluetooth® Low Energy User Guide v2.0.