gatt_security_server is not paired with a peer completely. It does with IOS, but not with android.
It looks like to exchange keys but not be recognized each other when reconnecting after bonded. And ESP_GAP_BLE_SEC_REQ_EVT evnet is not received to application.
Android recognizes ESP32 as a completely different device when reconnecting after a few seconds after bonded.
And bellow messages occur after a few minutes after re-connect.
I (831) SEC_GATTS_DEMO: The number handle = 8
I (841) SEC_GATTS_DEMO: advertising start success
I (6021) SEC_GATTS_DEMO: ESP_GATTS_CONNECT_EVT
E (36031) SEC_GATTS_DEMO: ESP_GAP_BLE_AUTH_CMPL_EVT
I (36031) SEC_GATTS_DEMO: remote BD_ADDR: 6b20639a05bd
I (36031) SEC_GATTS_DEMO: address type = 1
I (36041) SEC_GATTS_DEMO: pair status = fail
I (36041) SEC_GATTS_DEMO: Bonded devices number : 1
I (36051) SEC_GATTS_DEMO: Bonded devices list : 1
I (36051) SEC_GATTS_DEMO: 52 cf 44 e9 2f 02
E (39031) BT: btm_sec_clr_temp_auth_service() - no dev CB
I (39031) SEC_GATTS_DEMO: ESP_GATTS_DISCONNECT_EVT
I (39031) SEC_GATTS_DEMO: advertising start success
E (39171) BT: Device not found
In the iOS, it works well..
Please tell me that it's still in implementation and is included in the plan.
Is not the BLE stack implemented yet?
Re: Is not the BLE stack implemented yet?
When ive been implementing SM layer in Neils Kolban library i didnt found any of this issues. My esp32 remember all bounded devices and is reconnecting without keys exchange when is connecting with bounded device.It looks like to exchange keys but not be recognized each other when reconnecting after bonded. And ESP_GAP_BLE_SEC_REQ_EVT evnet is not received to application.
Android recognizes ESP32 as a completely different device when reconnecting after a few seconds after bonded.
Re: Is not the BLE stack implemented yet?
I've known the slave usually send LTK to the master to encrypt the connection when reconnecting with each bonded devices in the BLE specification. Is what I know wrong?
Re: Is not the BLE stack implemented yet?
Hi -
I am seeing the same issue. Has there been any further investigation?
I am seeing the same issue. Has there been any further investigation?
Who is online
Users browsing this forum: No registered users and 131 guests