Abasz

As an additional update: Also the NimBleServer->getConnectedCount() does not get updated. Almost like the device is not connected. But centrals can subscribe to notifications and receive data. I tried this...

I was affraid of this (yesterday evening I was digging in your code and came to the same conclusion) :) its clear that the `connect.status` is false when my watch...

If you were to create a branch and update esp-nimble code to the latest master I am happy to test. Only thing is I need to understand what to change...

> NimBLEDevice::setSecurityAuth(false, false, false); So this is a bit complicated. In terms the onConnect being called, there is no difference. On the pairing side, if I have made a pair...

Thanks, I confirm that the workaround works. `onConnect` is now being called properly, connected device count is increased in case of this unsupported feature status. I have 2 questions: 1....

> In the case for a server the status code should always be zero, this is an upstream bug where espressif changed the original code to always request DLE and...

> I am using 2.2.3 what is the fix for it? Have you tried updating to 2.3.1? or the bugfix branch: https://github.com/h2zero/NimBLE-Arduino.git#bugfix/onConnect