How can I stop a connection and BLE advertisement?

RE: How can I stop a connection and BLE advertisement?

Simonr — Thu, 28 May 2020 06:18:11 GMT

I think this is due to the on_disconnected() function in ble_advertising.c which handles the disconnected events and starts advertising back up upon disconnect events. You will either have to wait for this function to trig and then call sd_ble_gap_adv_stop() or change the on_disconnected() function to not start advertising when called.

Best regards,

Simon

RE: How can I stop a connection and BLE advertisement?

Giannis Anastasopoulos — Wed, 27 May 2020 10:49:00 GMT

Dear Simonr,

I have added your snippet, with some small changes:

if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
        {
            err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
            if (err_code != NRF_ERROR_INVALID_STATE)
            {
                APP_ERROR_CHECK(err_code);
            }
            m_conn_handle = BLE_CONN_HANDLE_INVALID;
        }
        m_advertising.adv_evt = BLE_ADV_EVT_IDLE;
        err_code = sd_ble_gap_adv_stop(NULL);

        if (err_code != NRF_ERROR_INVALID_STATE)
        {
            APP_ERROR_CHECK(err_code);
        }
    }

because I am using the v16.0.0 SDK.

The result is similar to what I had before. If there is no connection, everything seems to work fine.

But when I have established a connection and I press the button, the connection stops as expected, but the device is still beaconing. Why is that? With the above sample I need to press the button twice. Once the device will disconnect and the next time the beaconing will stop.

RE: How can I stop a connection and BLE advertisement?

Simonr — Wed, 27 May 2020 08:55:18 GMT

If you call sd_ble_gap_adv_stop() when you aren't advertising, for example while you're connected, the function will return the NRF_ERROR_INVALID_STATE. You should not call this function when you aren't advertising, or you have to ignore the invalid state error message. Same goes for the sd_ble_gap_disconnect() function if you call it if a disconnection is already in progress.

You can try something like this code snippet to circumvent these errors:

uint32_t err_code;

if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
{
    err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
    if (err_code != NRF_ERROR_INVALID_STATE)
    {
        APP_ERROR_CHECK(err_code);
    }
}

err_code = sd_ble_gap_adv_stop();
if (err_code != NRF_ERROR_INVALID_STATE)
{
    APP_ERROR_CHECK(err_code);
}

Best regards,

Simon