NimBLE peer_addr_type=1 rejects connection and device needs to recouple
Posted: Tue Oct 22, 2024 12:08 pm
Hello community
I am using a ESP32 with IDF version 5.1.2 and NimBLE. On the other side i use a Samsung Galaxy S21 with Android 14 and an Iphone 13 with iOS 17.6.
I setup NimBLE do be able to store two devices and have one connection at a time. It seems to work quit good for several times. Connecting once with the iphone and sometime later with the android and later again with the iphone.
And then suddenly the iphone and also the android tells me that it can not connect anymore because the esp dropped the keys.
The only possible way to get them connected again is to remove them from the bonded devices and pair them again.
I atteched two log files. One where the connections always where ok and fine. The second one where the connection did not work. The first difference what i have found out was that always when the connection was ok the peer_addr_type was 0 and when the connection was not possible it was 1.
How can that change at the same device? Is there maybe a hint what could be the problem?
thx
I am using a ESP32 with IDF version 5.1.2 and NimBLE. On the other side i use a Samsung Galaxy S21 with Android 14 and an Iphone 13 with iOS 17.6.
I setup NimBLE do be able to store two devices and have one connection at a time. It seems to work quit good for several times. Connecting once with the iphone and sometime later with the android and later again with the iphone.
And then suddenly the iphone and also the android tells me that it can not connect anymore because the esp dropped the keys.
The only possible way to get them connected again is to remove them from the bonded devices and pair them again.
I atteched two log files. One where the connections always where ok and fine. The second one where the connection did not work. The first difference what i have found out was that always when the connection was ok the peer_addr_type was 0 and when the connection was not possible it was 1.
How can that change at the same device? Is there maybe a hint what could be the problem?
thx