Ryan Powell

I think this is resolved in the latest commits in release 1.4 and master. Calling `NimBLEDevice::setSecurityInitKey(3);` in older commits should also work; Please re-open if you still have this issue.

The only thing I can think of that could cause that assert to trigger is if the connection closed just before processing the read request. Other than that, there could...

This can be done by calling `NimBLEDevice::startSecurity` in the onConnect callback.

You can simply create multiple client instances and maintain the connection with up to 9 devices.

Thanks for pointing this out. I looked at the code and it requests the info from the controller, may be a bug in the espressif controller and not NimBLE. Do...

> btw, i tested ota over ble with 2M_PHY and data are sent way too fast, the code has no chance to write on flash in time Cool, I'll have...

Phones use a random resolvable address. You would need to bond with the phone to be able to recognize it when the address changes and retrieve its static address.

the `desc->peer_id_addr` would be what is needed. But this has changed going forward.

This is how BLE works, unlike bluetooth classic. Here we can have devices that have some data secured and other data not secure. What you can do if you want...

> Sorry, I am no expert in BLE. I see that the security is based on the characteristic settings and not on the service nor the device. I am trying...