Emmanuel Thiessen

Hello everyone! I'm also witnessing this issue, or at least a similar one. Our peripheral has a long readable characteristic (~200 bytes), and the callback only gets triggered on the...

> @AnnoyingMoose That is the intended function, the callback should only be called on the first read which provides an opportunity to change the value before the client reads it....

``` // Read \#1 D (49215) NimBLECharacteristic: Characteristic beb5483e-36e1-4688-b7f5-ea07361b26a8 Read event D (49216) NimBLECharacteristic: Read: CHandle 1; Value length 0; Header length 8; MTU 23 D (49221) NimBLECharacteristic: >> setValue:...

I just did the same test with NimBLE-Arduino. The header for the initial read event is 10 bytes, and all subsequent reads for the same high-level read have header length...

> NimBLE-Arduino comes with NimBLE since the esp32 core does not have that code. I didn't realize that. It looks the version of NimBLE that comes with ESP-IDF v4.4.6 is...

> You can also use NimBLE-Arduino with IDF, you'll just need to disable nimble in menuconfig. That... makes things **much** easier. And it works! Thank you!

Greetings from the future! I am also having the same problem: Win11 Pro; Node 20.9.0; Noble 1.9.2-23: Peripheral discovered by Noble incorrectly has an empty string for `advertisement.localName`.