Ryan Powell

This is the behavior that should already be happening. When the bond limit is reached the oldest one gets deleted and the new bond is created. If this is not...

Closing as stale, please re-open if still an issue.

There are examples in the esp-nimble-cpp repo that do this, for instance https://github.com/h2zero/esp-nimble-cpp/blob/master/examples/basic/BLE_scan/main/main.cpp

That example is in the master branch which has some API changes, the blocking scan call no longer uses `start()` instead the `getResults()` call replaces it. Yes the Client example...

@Apvilchez Sorry I missed this, is this still an issue for you?

Closing this as unable to reproduce, also will be changed in the near term.

Thanks! These 2 methods should have the same result, so certainly this is not intended. I think an adjustment to remove the trailing NULL would be best, let me know...

The error is because the connection times out, which causes the secure connection call to fail and all the subsequent calls will obviously fail also. From the log `rc=13` is...

Yes it certainly should be noted as a possible breaking change. Thanks!

> Is there any equivalent method to do ESP_GATT_AUTH_REQ_NO_MITM in NimBLE? This should do the same thing: `NimBLEDevice::setSecurityAuth(true, false, true);`