expose esp_ble_conn_data_t in ble_conn_mgr callbacks (AEGHB-1398)

[acouvreur]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

The esp_ble_conn_cb_t type does not expose the esp_ble_conn_data_t making it impossible to retrieve the connection ID.

There is a priv_data in the esp_ble_conn_cb_t type, however I'm not sure it is filled with anything in the nu lookup table callbacks ?

[XionHsieh1025]

Hi @acouvreur

This API can be used to obtain the Connection ID.

/**
 * @brief   Get current connection handle (read-only).
 *
 * @param[out] out_conn_handle  Pointer to store current connection handle. 0 if not connected.
 *
 * @return
 *  - ESP_OK on success
 *  - ESP_ERR_INVALID_ARG if out_conn_handle is NULL
 */
esp_err_t esp_ble_conn_get_conn_handle(uint16_t *out_conn_handle);

https://docs.espressif.com/projects/esp-iot-solution/en/latest/bluetooth/ble_conn_mgr.html#_CPPv428esp_ble_conn_get_conn_handleP8uint16_t

[acouvreur]

Hi @acouvreur

This API can be used to obtain the Connection ID.

/**

• @brief Get current connection handle (read-only).
• @param[out] out_conn_handle Pointer to store current connection handle. 0 if not connected.
• @return
• • ESP_OK on success
• • ESP_ERR_INVALID_ARG if out_conn_handle is NULL
    */
    esp_err_t esp_ble_conn_get_conn_handle(uint16_t *out_conn_handle);

https://docs.espressif.com/projects/esp-iot-solution/en/latest/bluetooth/ble_conn_mgr.html#_CPPv428esp_ble_conn_get_conn_handleP8uint16_t

Seems to work, but I god a little confused with:

0 if not connected.

It looks like 0 is a valid connection handle:

I (200851) blecm_nimble: mtu update event; conn_handle=0 cid=4 mtu=517

So maybe the not connected value should be changed

Would you be able to clarify that for me ?

[XionHsieh1025]

Hi @acouvreur
There are some issues with the comments here. Please refer to the actual output as the source of truth; we will review the comments and revise them accordingly.