solicited uuids

RE: solicited uuids

Ole Morten — Thu, 20 Feb 2014 15:48:51 GMT

This error indicates that the size of your advertisement packet is too big. Take a look at this question: https://devzone.nordicsemi.com/index.php/what-s-the-maximum-size-for-an-advertisement-package#reply-76

I'd also be happy if you could accept my answer here, to clear up this question. :)

RE: solicited uuids

sherin — Thu, 20 Feb 2014 13:40:24 GMT

Thank you.

I am integrating Alert Notification Client and Apple Alert Notification Client. Now, the solicited uuid for ancs is 128 bit uuid, whereas solicited uuid for alert notification is 16 bit. How can I list both these types in the solicited uuid list? I did this:

ble_uuid_t    ancs_uuid, anp_uuid;
ancs_uuid.uuid = ((ble_ancs_base_uuid128.uuid128[12]) | (ble_ancs_base_uuid128.uuid128[13] << 8));
ancs_uuid.type = BLE_UUID_TYPE_BLE;     

anp_uuid.uuid = 0x1811;
ancs_uuid.type = BLE_UUID_TYPE_BLE;

ble_uuid_t solicited_uuids[] = 
{
  ancs_uuid, anp_uuid
};

It gives me NRF_ERROR_DATA_SIZE.

RE: solicited uuids

Ole Morten — Thu, 20 Feb 2014 12:19:26 GMT

This is really dependent on how the Central device behaves, so it's hard to say for sure, but I would definitely expect the Central to connect, no matter if there are more than one service in the solicited services field.

In the case of iOS, it will for example show a device advertising Apple Notification Center Service as in the Bluetooth settings, even if it also advertises another service as solicited.