But I just have one concern regarding this issue is that we have already released one product based on ESP32 IDF 2.0 SDK and i don't want to upgrade whole ESP32 SDK now for this issue fix.


As per the reply I sent you on the other thread, updating to V2.1 and then V2.1.1 is the supported upgrade ...

Quite simple: The advertisement length of BLE is 32 bytes. With a 128bit UUID you cant even fit 2 withing an advertisement let alone a complete list.

Below is the only code I added on top of the service table example code, it shows the error when I read the sensor location.

E (104789) BT: GATTS_SendRsp conn_id: 4 waiting for op_code = 00
E (104789) BT: Sending response failed


case ESP_GATTS_READ_EVT:
memset(&rsp, 0, sizeof(esp_gatt_rsp_t ...

Probably 1073560042 is in raw milliWatts in decimal, because if you convert it to dBm ths gives 90.308263386 dBm. And since RSSI values vary from 0 to -120, probably this is -90.308263386 dBm.

But one question I have is that the value -120dBm would fall outside the int range described in esp_gap ...

1. Well radio implementations such as LORA for LPWAN, nothing more than that for in my side of the world(Kenya). It can even be an off chip addition that can be done as a module that one can buy in bulk from a single supplier. I have done deployments for such and the ESP32 is a real contender if ...

1. Well radio implementations such as LORA for LPWAN, nothing more than that for in my side of the world(Kenya). It can even be an off chip addition that can be done as a module that one can buy in bulk from a single supplier. I have done deployments for such and the ESP32 is a real contender if ...

The handle of the characteristic is stored in the attribute handle table returned after ESP_GATTS_CREAT_ATTR_TAB_EVT:


heart_rate_handle_table[CHARACTERISTIC_ENUM_VALUE]

will return the handle for CHARACTERISTIC_ENUM_VALUE.
Hi halfro,
Thanks for your response.But I can't get handle. I want to ...

The handle of the characteristic is stored in the attribute handle table returned after ESP_GATTS_CREAT_ATTR_TAB_EVT:
will return the handle for CHARACTERISTIC_ENUM_VALUE.

If the task runs at unpredictable times, why would you put in a watchdog at all?

Thanks for the insight. I haven't used watchdogs before so I was trying to understand if it can be used for non deterministic code to get rid of the "unable to feed task watchdog" message.

So I have a BLE task and the task contains a gatt server and advertisement data. Is there a way to feed the task watchdog. I have read the notes on the watchdogs but I can't find a way for my BleTask to be watched especially since BLE operations are very asynchronous.

Here is my trial at it ...