You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good morning! Thank you so much for this library. It is getting better every time and I really appreciate all the improvements in v2. The support you provide is so helpful, too! :-)
I am using this library to read advertisement data from sensors and to allow my device to be controlled with a mobile app. What I notice, and it is quite hard to reproduce, is that connections are not always closed. Maybe it is better to say cleaned up, because in this case it is about one mobile phone connecting to the device.
This graph shows the result of NimBLEDevice::getServer()->getConnectedCount():
At one point the device runs into the configured limit of 3 of CONFIG_BT_NIMBLE_MAX_CONNECTIONS and as a result the device would not allow new connections.
Did you ever run into this before? Maybe some things for me to check?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Good morning! Thank you so much for this library. It is getting better every time and I really appreciate all the improvements in v2. The support you provide is so helpful, too! :-)
I am using this library to read advertisement data from sensors and to allow my device to be controlled with a mobile app. What I notice, and it is quite hard to reproduce, is that connections are not always closed. Maybe it is better to say cleaned up, because in this case it is about one mobile phone connecting to the device.
This graph shows the result of

NimBLEDevice::getServer()->getConnectedCount()
:At one point the device runs into the configured limit of 3 of
CONFIG_BT_NIMBLE_MAX_CONNECTIONS
and as a result the device would not allow new connections.Did you ever run into this before? Maybe some things for me to check?
Thanks in advance!
The text was updated successfully, but these errors were encountered: