A characteristic on a device has a handle - it's basically a number (a byte value?) which is the index of the characteristic in that device.
Then there's the cccd - it's another handle that is used for setting flags to do with that characteristic. Specifically Espruino uses that handle to write to a device and ask for notifications - it's done here: jswrap_nrf_BluetoothRemoteGATTCharacteristic_startNotifications
So Espruino stores those two as handle_cccd and handle_value (the actual characteristic) on BluetoothRemoteGATTCharacteristic. I think that should work for ESP32 as well.
I'm not sure about the others if I'm honest, but I think you could probably ignore them safely for now.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
As I understand it (I could be wrong!):
A characteristic on a device has a handle - it's basically a number (a byte value?) which is the index of the characteristic in that device.
Then there's the
cccd
- it's another handle that is used for setting flags to do with that characteristic. Specifically Espruino uses that handle to write to a device and ask for notifications - it's done here: jswrap_nrf_BluetoothRemoteGATTCharacteristic_startNotificationsSo Espruino stores those two as
handle_cccd
andhandle_value
(the actual characteristic) on BluetoothRemoteGATTCharacteristic. I think that should work for ESP32 as well.I'm not sure about the others if I'm honest, but I think you could probably ignore them safely for now.