Enabling notifications from custom UUID as central

RE: Enabling notifications from custom UUID as central

Petter Myhre — Thu, 17 Aug 2017 07:28:18 GMT

You add a UUID base by calling sd_ble_uuid_vs_add(). After you have called it, the UUID type or UUID base reference will be found in uuid_type.

RE: Enabling notifications from custom UUID as central

pbirkner — Wed, 16 Aug 2017 17:08:39 GMT

"You should add your custom UUID base and use the outputted UUID type as a reference to that base"

How do I do this?

RE: Enabling notifications from custom UUID as central

Petter Myhre — Wed, 16 Aug 2017 17:05:20 GMT

You can't use 0x01 for custom UUIDs. And it doesn't make sense to set it to 0x01. The argument UUID type argument to sd_ble_uuid_vs_add() is an output, not an output. You should add your custom UUID base and use the outputted UUID type as a reference to that base.

@param[out] p_uuid_type  Pointer to a uint8_t where the type field in @ref ble_uuid_t corresponding to this UUID will be stored.

RE: Enabling notifications from custom UUID as central

pbirkner — Wed, 16 Aug 2017 13:44:57 GMT

I am able to connect to the device. It also has a heart rate service, which I am able to discover. I am not able to discover the service with a custom UUID. I believe my issue stems from the fact that their custom service starts at the 0x01 index of their custom UUID rather than the 0x02 index. This is why I explicitly state: p_ble_nus_c->uuid_type = 0x01.

RE: Enabling notifications from custom UUID as central

Petter Myhre — Wed, 16 Aug 2017 09:09:49 GMT

The problem is that custom service starts at the FIRST index of the 128 bit UUID rather than the second.

I don't quite understand what you mean by this. Could you elaborate? You are able to connect? But not discover the service? What happens?

(Not relevant, but why are you doing p_ble_nus_c->uuid_type = 0x01;?)