https://devzone.nordicsemi.com/f/nordic-q-a/18623/service-discover-returns-ble_gatt_status_atterr_attribute_not_foundI&#39;m using SD132 as a central, that I want to connect to a custom peripheral device. I first add the 128-bit base UUID with: sd_ble_uuid_vs_add(&amp;mys_base_uuid, &amp;p_mys_c-&gt;uuid_type); I assign the type (offset) and 16-bit service UUID with: mys_uuiden-USTelligent Community 13Wed, 28 Dec 2016 17:08:41 GMThttps://devzone.nordicsemi.com/thread/71904?ContentTypeID=1Wed, 28 Dec 2016 17:08:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8a14ae8d-0863-4d31-8a4b-3d4983c965abc cook<p>Solved it. The problem was on the peripheral side. I add my 128-bit UUID with sd_ble_uuid_vs_add(...), and the call returns a type 2. I then assign the 16-bit service UUID and type to ble_uuid</p> <pre><code> ble_uuid.type = p_light-&gt;uuid_type; ble_uuid.uuid = BLE_UUID_MYSWITCH_SRV </code></pre> <p>but had left the macro</p> <pre><code>BLE_UUID_BLE_ASSIGN(ble_uuid, BLE_UUID_MYSWITCH_SRV); </code></pre> <p>in my code, which set the uuid.type = 1. So when I called sd_ble_gatts_service_add(...) the wrong value for ble_uuid.type was used. In my central code, listed in the question above, I was expecting the 128-bit UUID, but was getting a 16-bit value. After commenting out BLE_UUID_BLE_ASSIGN(...) on my peripheral side, my central app was successful in discovering the service</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/71903?ContentTypeID=1Wed, 28 Dec 2016 09:34:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:25261152-7612-4ca7-865a-10ac8bdd13d9Petter Myhre<p>I&#39;m not sure. You are only registering one UUID with ble_db_discovery_evt_register()? Could you share your project so I can test them here?</p><div style="clear:both;"></div>