How to Respond with pairing unsupported

[brianreinhold]

Again I am asking a question I should not because I cannot find it documented.

I get a pairing request from the central. I need to respond with sd_ble_gap_sec_params_reply()

There is a status parameter in the method and that I figure I can set to BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP. But what about the remaining parameters? There is nothing in the documentation which indicates how to set the other fields when I set the status to BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP. I want to set them to NULL but there may be a NULL check in there that returns an error.

Found no help in the GAP sequence diagrams either.

So how do I respond to a pairing request with BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP?

[Amanda Hsieh]

Hi, 

Have a look at sd_ble_gap_sec_params_reply doc.:

This function is only used to reply to a BLE_GAP_EVT_SEC_PARAMS_REQUEST, calling it at other times will result in an NRF_ERROR_INVALID_STATE.

What is the error? Is it NRF_ERROR_INVALID_STATE? If so, Possible causes are listed here. This post might help.

Regards,
Amanda

[Jimmywong2003]

You can refer to the blog (https://jimmywongiot.com/2021/06/29/how-to-allow-reject-the-ble-bonding-request-from-central/).

[brianreinhold]

I think you misunderstand the question. I am not getting the error, but I have GOTTEN a pairing request ( BLE_GAP_EVT_SEC_PARAMS_REQUEST,)  from the client but I do not support pairing. I want to send that error message to the client in the sd_ble_gap_sec_params_reply().

However, there is nothing in the documentation that says how I should populate the remaining fields (keys and other stuff) when I set the status entry to BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP.

I WANT TO SEND THE ERROR IN RESPONSE TO THE CLIENT REQUEST, I am not getting an error from the client!

[Amanda Hsieh]

Reject the request:

error_code = sd_ble_gap_sec_params_reply(m_conn_handle, BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP, NULL, NULL);

-Amanda

[brianreinhold]

It was the NULL, NULL part that I was unsure of. As I stated in the original question, there was nothing in the docs indicating that and I wasn't sure if that would cause some kind of exception. In any case, that was my guess but it would help if the case were documented so I would not have to ask.

By the way, this is on a DK and not the ble-pc-driver so there is no 'adapter' parameter.