Per this --> https://github.com/espressif/esp-idf/bl ... ain.c#L285

the same callback handler is used for read / write and notify. So if you are creating a new characteristics, confirm if you have added correct flags for it or not.

Blecent example has a code to show how to do stack init / deinit in a loop. https://github.com/espressif/esp-idf/bl ... ain.c#L910 . You can check it for reference.

Can you share your sample application or console log to narrow down which function is returning this error. Also, can you share your complete sdkconfig ?

Hi ,

I just saw in the log shared has Data len as 245 . Is this correct field being printed ? Legacy adv packets are of maximum size 31.

Hello c3pnr-iot , HW Platform : ESP32 Build Env : Linux / ESP IDF 4.4 BLE Stack : NimBLE 1.3.0 Please note v4.4 is now EOL. I tested on 5.x also, but they give the same result. If you are able to reproduce the issue using blecent OR by making any modification, please do share your testing code too w...

Hello @c3pnr-iot, I tried running the example blecent with some debug prints for this. I can see below prints that indicate the value of data recieved. event->disc.length_data: 26 rssi -27 2 1 6 3 3 11 18 f 9 6e 69 6d 62 6c 65 2d 62 6c 65 70 72 70 68 2 a 3 D (2680) NimBLE: flags=0x06 D (2680) NimBLE...

The devices you want to allow to connect, you can add to whitelist . Once whitelist is generated, you can apply the setting to allow connection from filter list . This way, only connections from address which are present in the whitelist would be accepted and rest would be dropped.

> I was thinking of a method where the device is only visible for 30 seconds when pressing a pairing button

You can opt for limited discovery , where advertising is done only for limited period of time. After that advertising stops, so remote devices cannot find your device or initiate connection.

ESP chipsets have their own controller. So for Nimble ( or bluedroid ) only the host part of upstream mynewt-nimble code is used. The nimble controller part is not enabled / compiled in ESP-IDF .

Files like examples/bluetooth/nimble/common/nimble_central_utils/misc.c and examples/bluetooth/nimble/common/nimble_central_utils/peer.c are also needed. Infact all files of the nimble_central_utils folder need to compiled. Guess you are missing them.