esp-nimble-cpp
esp-nimble-cpp copied to clipboard
C++ library for the esp32 NimBLE stack based on and mostly compatible with @nkolban cpp_utils BLE library.
This adds a callback that is called when a device is initially discovered. It is always called wether scanning in passive or active mode. This allows for active scanning to...
hey there so im using esp32 project and got compilation issues. if you can assist me and tell where issue is. ty ``` C:\Users\cooki\Desktop\engi\ESP\esp32\ESP32Marauder-master\esp32_marauder\WiFiScan.cpp: In member function 'void WiFiScan::RunSetup()': WiFiScan.cpp:138:19:...
The onRead callbacks are never trigger. I traced it down to the packet header length always being 8 in line: https://github.com/h2zero/esp-nimble-cpp/blob/a36655c105444f26d1ef7dd0893b189ab26f23ce/src/NimBLECharacteristic.cpp#L278 So apparently the filter for first and follow up...
Hello! Could you please share a little example how to use bootInput and bootOuput characteristics? I understand how to create them and add to HID service, but can't understand how...
Not sure if this intentional. Example Code: ``` NimBLEScan *pBLEScan; class MyAdvertisedDeviceCallbacks : public NimBLEAdvertisedDeviceCallbacks { void onResult(NimBLEAdvertisedDevice *advertisedDevice) { // // local variables from bluetooth scan uint8_t blueRSSI =...
Hi there, been a while for me, but i needed to make an update to my existing project so i figured id update the Nimble-CPP component i had to make...
First off, thanks for this great set of classes! I'm using an esp32c3 and need to transfer a huge stream of data to iPhone (and Android) over BLE and wonder...
Due to [L2CAP not really working](https://github.com/espressif/esp-idf/issues/9044) yet, I'm looking to transfer larger stream of data (i.e. up to 4KB) via consecutive READs (and WRITEs for the response) to a characteristic...
I find that if I scan for advertised devices requesting no duplicates my callback sees duplicates repeated at almost exactly 60 second intervals. I wonder if I'm doing something wrong...
I have a few changes in mind that will break the current API in a few ways and would like to get feedback on these. If you're interested please check...