NRF52 discovery event has all characteristic uuids 0

RE: NRF52 discovery event has all characteristic uuids 0

Joakim Jakobsen — Fri, 25 Jun 2021 14:36:26 GMT

Thanks for sharing.

Br,
Joakim

RE: NRF52 discovery event has all characteristic uuids 0

Chang.tsai — Fri, 25 Jun 2021 04:33:59 GMT

Thank you for the information, I have solved this problem.

According to the ticket you provided, I found the cause of the problem. The cause of this problem is that the basic UUID of the BLE service is different from the basic UUID of the characteristic.

When I used sd_ble_uuid_vs_add() to add a custom UUID before, only the UUID of the service was added, and the UUID of the characteristic was not added.

Now I use sd_ble_uuid_vs_add() to add the UUID of the characteristic to the custom UUID, and everything is good.

RE: NRF52 discovery event has all characteristic uuids 0

Joakim Jakobsen — Mon, 07 Jun 2021 08:15:30 GMT

Hi again.

Maybe you could add some code snippets for how you add the characteristics and the UUIDs?

Also, you might be able to find some relevant information from previous tickets. Like this one:
https://devzone.nordicsemi.com/f/nordic-q-a/40578/discovering-a-vs-uuid-characterisic-but-it-shows-uuid-as-0

Br,
Joakim

RE: NRF52 discovery event has all characteristic uuids 0

Joakim Jakobsen — Thu, 27 May 2021 21:05:38 GMT

Hi.

Sorry about the delayed response. I don't think the SD will tread the custom UUID differently, but I'll ask internally in our SD team and get back to you.

Br,
Joakim

RE: NRF52 discovery event has all characteristic uuids 0

Chang.tsai — Fri, 21 May 2021 09:38:04 GMT

I have conducted various tests for this issue these days.

I noticed that the customized UUID of this device is 0000fd6d-0000-1000-8000-00805f9b34fb.

Looks like the Bluetooth SIG basic UUID, Not sure if this is the cause of the problem...

Will SoftDevice treat the Bluetooth SIG basic UUID differently from the general custom UUID?