ble_gattc_evt_hvx_t :: handle gives you the handle of the peer's attribute. You will have had to peform service discovery beforehand to know what this handle corresponds to, you can use:
ble_gattc_evt_hvx_t :: handle gives you the handle of the peer's attribute. You will have had to peform service discovery beforehand to know what this handle corresponds to, you can use:
You mean that this handle gs_peripheral[peripheral_id].descriptor_handle should be equal to ble_gattc_evt_hvx_t handle?
If so, for me it's different, 18 and 17.
It seems that the characteristic value handle is not being stored, you could add that there, but essentially if you're getting 17 that means it's the right characteristic, because the "descriptor_handle" corresponds to the CCCD descriptor, which is placed right after the characteristic value.
Fount out this.
This gs_peripheral[peripheral_id].descriptor_handle is notification enable handle, but not my characteristic handle.
In example, after discovering characteristic there is an increment of handle_range
handle_range.start_handle = gsp_ble_evt->evt.gattc_evt.params.char_disc_rsp.chars[i].handle_value + 1;
thats why i missed it.
gsp_ble_evt->evt.gattc_evt.params.char_disc_rsp.chars[i].handle_value is what you're looking for, you could store that in a new member of peripheral_t that you can add. Store it right where it says "Characteristic found".
