case switch should always break;
if you are at the last characteristic, the next get will cause some other case or error.

i think %0 is NULL

Do you mean a unique identifier for the esp32 bluetooth? like Bluetooth Device Address? Something like this?

Can you use the same implementation as arduino?
millis() https://github.com/espressif/arduino-es ... misc.c#L50
micros() https://github.com/espressif/arduino-es ... misc.c#L33

it finds the next one, if the last param != 0. See esp_gattc_api.c:172 :176 :180 This gets the first characteristic esp_ble_gattc_get_characteristic(gattc_if, conn_id, &alert_service_id, NULL); The result then contains a char_id, and will get the next characteristic esp_ble_gattc_get_characteristic(...

Have a look at: Its return type is esp_err_t: This would be correct:

You can also try Mongoose OS or MicroPython which simplify this process.

uhh you might want to put the adc value you read into one of your GET if-statements or inside your http Response-body.
Your sensor value read is outside the whole http-server stuff. client.stop() was already called when you call client.print(sensorValue);.

Hi all, I've been dabbling a bit in GATTC, and I noticed the Gatt authentication request type for the reads and writes. I've tried the different levels but all seem to fail. What do I need to set-up to use these authentication types? Can anyone enlighten me? I (5469) Provision: Searched device Nexus...

Before you reset do you properly close the connection?
I also sometimes get errors and a closed connection. usually when I try to access some characteristic that is not set by the server.
The nRF Connect app on android helped me debug things. I could close the connection(or pairing?) etc.