nRF5 SDK client scan does not see names advertised on nRF Connect peripheral

RE: nRF5 SDK client scan does not see names advertised on nRF Connect peripheral

Einar Thorsrud — Fri, 24 Nov 2023 09:01:18 GMT

To put everything in the advertising packet, the snippet from your original post would look like this:

static char bt_device_name[CONFIG_BT_DEVICE_NAME_MAX + 1] = CONFIG_BT_DEVICE_NAME;
static uint32_t conntimeout;

static struct bt_data ad[] = {
        BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
        BT_DATA_BYTES(BT_DATA_UUID128_ALL, MY_SERVICE_UUID),
        BT_DATA(BT_DATA_NAME_COMPLETE, bt_device_name, (sizeof(CONFIG_BT_DEVICE_NAME) - 1)),
}; 

// Start advertising
err = bt_le_adv_start(BT_LE_ADV_CONN, ad, ARRAY_SIZE(ad), NULL, 0);
if (err) 
{
        LOG_INF("Advertising failed to start (err %d)\n", err);
        return;
}

RE: nRF5 SDK client scan does not see names advertised on nRF Connect peripheral

fgeldenh — Fri, 24 Nov 2023 03:51:54 GMT

Can you assist me getting this right. On the client I have a scan filter set up for the custom 128 bit UUID

MY_SERVICE_UUID BT_UUID_128_ENCODE(0x9DAB8E8E, 0x75E9, 0x448B, 0xAD73, 0x98D596826FA8)

I would like to advertise with this UUID and a name of 8 characters.

on the present nRF5 SDK Implementation the advertisement is set up as below. I would like to do the same in nRF Connect. I was under the impression that that is what I had done.

static void advertising_init(void)
{
    ret_code_t    err_code;
    //ble_advertising_init_t init;

    memset(&adv_init, 0, sizeof(adv_init));

    adv_init.advdata.name_type               = BLE_ADVDATA_FULL_NAME;
    adv_init.advdata.include_appearance      = false;
    adv_init.advdata.flags                   = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
    adv_init.advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    adv_init.advdata.uuids_complete.p_uuids  = m_adv_uuids;

    adv_init.config.ble_adv_fast_enabled   = true;
    adv_init.config.ble_adv_fast_interval  = APP_ADV_INTERVAL;
    adv_init.config.ble_adv_fast_timeout   = APP_ADV_DURATION;
    adv_init.config.ble_adv_on_disconnect_disabled = true;  // do not advertise after disconnect

    adv_init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &adv_init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

RE: nRF5 SDK client scan does not see names advertised on nRF Connect peripheral

Einar Thorsrud — Thu, 23 Nov 2023 14:54:52 GMT

Hi,

On the advertiser, you have the UUID in the advertising packet and the name in the scan response packet (which is an "extra" advertising packet). However, the scanner handles the advertising packets and scan response packets separately. So with this configuration it will not work (the UUID and name are not in the same packet). If you don't need long advertising names, try fitting everything in an advertising packet and don't use scan response.