You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My sketch setups NimBLEDevice::init("TEST"); but only "TE" name is advertised. Any name attempt only shows its first two letters.
This happened after updating NimBLE-Arduino to 1.4.2 and ArduinoEsp32 3.0.2 update was aborted.
My board is ArduinoEsp32 2.0.11
Multiple nrFConnect clients see the same two-letter name.
While updating ArduinoESP32 3.0.2 i suddently read this, so i aborted.
Migration from 2.x to 3.0
BLE
Changes in APIs
Changed APIs return and parameter type from std::string to Arduino style String.
Changed UUID data type from uint16_t to BLEUUID class.
BLEScan::start and BLEScan::getResults methods return type changed from BLEScanResults to BLEScanResults*.
Is NimBLE-Arduino 1.4.2 compatible to ArduinoESP32 3.0.2?
Any idea, please, this is driving me crazy,
Thanks in advance,
Osmany
The text was updated successfully, but these errors were encountered:
osmany-ferrer
changed the title
NimBLE-Arduino 1.4.2 is compatible with ArduinoESP32 3.0.2?
NimBLE-Arduino 1.4.2: problem with device name?
Jul 7, 2024
Hello,
My sketch setups NimBLEDevice::init("TEST"); but only "TE" name is advertised. Any name attempt only shows its first two letters.
This happened after updating NimBLE-Arduino to 1.4.2 and ArduinoEsp32 3.0.2 update was aborted.
My board is ArduinoEsp32 2.0.11
Multiple nrFConnect clients see the same two-letter name.
While updating ArduinoESP32 3.0.2 i suddently read this, so i aborted.
Migration from 2.x to 3.0
BLE
Changes in APIs
Changed APIs return and parameter type from std::string to Arduino style String.
Changed UUID data type from uint16_t to BLEUUID class.
BLEScan::start and BLEScan::getResults methods return type changed from BLEScanResults to BLEScanResults*.
Is NimBLE-Arduino 1.4.2 compatible to ArduinoESP32 3.0.2?
Any idea, please, this is driving me crazy,
Thanks in advance,
Osmany
The text was updated successfully, but these errors were encountered: