RE: Can't send two separate BLE indications

kruenheck — Tue, 16 Sep 2025 18:42:16 GMT

Thank you, that helps a lot.

RE: Can't send two separate BLE indications

Vidar Berg — Tue, 16 Sep 2025 14:41:22 GMT

Hello,

You were on the right track. The problem, as you pointed out, is that ind_params.attr must point to the correct attribute handle (the one matching the characteristic you are trying to send the indication from). &my_lbs_svc.attrs[2] points to the value handle for your BT_UUID_LBS_BUTTON characteristic, which is correct for my_lbs_send_button_state_indicate(), but this index needs to be updated in my_lbs_send_kdr_state_indicate().

&my_lbs_svc.attrs[4] or &my_lbs_svc.attrs[5] should work for my_lbs_send_kdr_state_indicate().

int my_lbs_send_kdr_state_indicate(bool kdr_state)
{
    if (!indicate_enabled)              
    {
        return -EACCES;
    }
    ind_params.attr = &my_lbs_svc.attrs[5];
    ind_params.func = indicate_cb;
    ind_params.destroy = NULL;
    ind_params.data = &kdr_state;
    ind_params.len = sizeof(kdr_state);
    return bt_gatt_indicate(NULL, &ind_params);
}

How you can find this index is explained in section 5.2 of the exercise your are working with.

Best regards,

Vidar