... looks like the service UUID is not advertised, even though it should. I did some further testing / analysis (read: "trial and error"...) on my original issue and noticed that my initial problem description was not accurate. The original GATT server demo does correctly advertise the service UUID...

When I look at the APIs used to manipulate values (esp_ble_gattc_write_char), I see that it takes the connection id to the device (check ... that makes sense), the service uuid and the characteristic uuid ... and no mention of handles. Now ... my *guess* is that internally in the ESP-IDF APIs, the ...

for some reason, I'm not able to connect to the device using the Android app "BLE Scanner", while on iOS with "LightBlue", connection seems to work without any problems. EDIT: I moved two non-related questions to their own thread and also created a new thread concerning the Android connection probl...

I've been playing with the GATT server example lately and noticed that it looks like the service UUID is not advertised, even though it should. Even though there are two service UUIDs defined in the test_service_uuid128 array, none of them is advertised. When looking at the advertising data in e.g. ...