thekurtovic

I had previously tried what is shown in that thread, but it did not seem to change anything for me. I tried again as a sanity check, still no dice....

Some other occurrences https://github.com/h2zero/NimBLE-Arduino/blob/master/src/NimBLEServer.h#L175 https://github.com/h2zero/NimBLE-Arduino/blob/master/src/NimBLEDevice.h#L166

@pikkaru You could add checks on the return values from `init` and `deinit`.

@gittehupe Your example checks the result but does nothing with it beyond printing. Should do something like this. ``` if (!connected) { Serial.println("Failed to connect to device."); return; } ```...

Same treatment as previous PR. I assumed similar rules apply here, but let me know if it's wrong. `NimBLEClient` also has a similar section of code. I was thinking of...

Sure, that works too.

Does `retrieveCharacteristics` need a check similar to https://github.com/h2zero/esp-nimble-cpp/commit/8158a16fbf3d716fd2dd16f6f8990c12265aefe7?

I introduced some minor changes since the previous successful build. Let me know if I should revert. Since `characteristicDiscCB` doesn't mention the function name in the log messages, I shortened...

Some of the BLE jargon just adds so much bloat when written in full like characteristic, descriptor, etc.; which then causes the need to break function calls up with one...

~There's one warning I wasn't able to resolve. `NimBLEUUID(const ble_uuid_any_t& uuid);`~ ~If I make that constructor explicit then I get this compile error.~ Log ``` managed_components/esp-nimble-cpp/src/NimBLERemoteValueAttribute.h: In constructor 'NimBLERemoteValueAttribute::NimBLERemoteValueAttribute(const ble_uuid_any_t&,...