Ryan Powell
Ryan Powell
Thank you for the details, that will help me to reproduce the issue, though I think this may be caused by something upstream. I'll look into this soon.
~~@Abasz I think this has been fixed upstream: https://github.com/espressif/esp-nimble/commit/5a1882e4b97ab29e1a800144f576e6ad05fd4913~~ ~~If you'd like to test this I will be looking to update the core soon~~ Nevermind, we already have this commit.
@Abasz This is very strange for sure, does this happen with version 2.2.3 or just 2.3.x?
@Abasz what happens if you disable all the security features?: `NimBLEDevice::setSecurityAuth(false, false, false);`
Thanks @Abasz, that confirms the suspicion that this is an upstream bug, that was the major change in 2.3, so I will look into this and for now just used...
@Abasz I decided to workaround this issue, it will apply to esp-idf users as well so it made sense to do so. Please test #987 and let me know if...
> What is the purpose of checking for a non-zero status in the BLE_GAP_EVENT_CONNECT event? I dont know the cases when the stack calls this event but I assume that...
Yes, multiple connections are supported, that example was just not designed for it (it goes to sleep after disconnecting from 1 peer). I will not be updating the 2.2.x branch...
All you need to do is start advertising after a connection is made because the connection process stops the advertising. You can do this for up to 3 connections by...
Could you enable debug logs and share the output when this happens please?