As a follow up, I solved this issue adding a characteristic handle variable to the services' definition structure. static const struct ble_gatt_svc_def services[] = { .type = BLE_GATT_SVC_TYPE_PRIMARY, .uuid = &serviceUUID.u, .characteristics = (struct ble_gatt_chr_def[]) { { .uuid = &characteristic...

I have kind of resolved the issue. I changed the device address type to public using the following sync callback: assert(ble_hs_util_ensure_addr(0) == 0); ble_hs_id_copy_addr(ownAddrType, addr_val, NULL); ESP_LOGI("BLE_Sync", "Device address %02X:%02X:%02X:%02X:%02X:%02X type %i", addr_val[0], addr_...

I am facing the exact same issue explained on this post, is the problem solved in any way? I am not able to resolve the addresses even enabling RPA on the ESP32 using ble_hs_pvcy_rpa_config(1).

I have found that when a device subscribes to all of the characteristics I have (24 in total) the descriptors are saven on the NVS. As I pretend to save bonding information of 4 devices and the stack automatically saves the descriptors of each device I understand tha I need enough space on the NVS f...

I am working on a BLE project using NimBLE on a ESP32-SOLO-1 and I am encountering a problem with the bonding of multiple devices. When I connect a new device the bonding process starts and completes correctly. I am able to read and write all the characteristics without any problem. I can even bond ...

As an update, I am trying to know what do I need to do when a client registers for notification. At the moment I do nothing when I get the BLE_GAP_EVENT_SUBSCRIBE event. I should register the connection somewhere to know which connections are registered and which not, but I cant find how.

Hello, I am trying to create a BLE peripheral on a ESP32-SOLO-1 using NimBLE Stack. I have successfully created characteristics and I am able to read and write on them, but I can't notify new values to the client. I have configured the characteristic with read, write and notify flags (.flags = BLE_G...