Closed rafaelpm closed 1 year ago
When you send notifications it sends the current value of the characteristic, if you're doing this in a loop it will keep sending the notification.
Removing NIMBLE_PROPERTY::NOTIFY so don't send in a loop, however, don't send anything. How set and reset notify flag in runtime? Is need to stop and start server?
Thanks for the reply, bug has been fixed. I wrote the below code in my loop.
if(pServer->getConnectedCount() > 0) {
NimBLEService* pSvc = pServer->getServiceByUUID(UUID_SERVICE_SERIAL_PORT);
if(pSvc) {
NimBLECharacteristic* pChr = pSvc->getCharacteristic(UUID_CHARACTERISTIC_FIFO);
if(pChr) {
pChr->notify(false);
}
}
}
Everyone know about lack components, so I need to replace a Bluetooth NINA-B112. The behavior below occurs on the Nina W106 and ESP32-CAM (AI Thinker) modules. I started a project from example server, but editing lines like bellow:
My defines are:
I used u-blox app: https://play.google.com/store/apps/details?id=com.ublox.BLE Using this android app, when connected, I receive a lot of same data like: RAFAEL. If I send data in chat tab (for example: Test), I receive a lot of "Test". My conclusion is that it sends what is in the buffer, but what started it? How control it?