After hids_client_send_write_report() client state never gets back to HIDS_CLIENT_STATE_CONNECTED
#573
Comments
ricardoquesada
added a commit
to ricardoquesada/btstack
that referenced
this issue
Mar 16, 2024
…_STATE_CONNECTED This commit sets the client state back to HIDS_CLIENT_STATE_CONNECTED after receiving a GATT_EVENT_QUERY_COMPLETE event. Fixes bluekitchen#573
|
Hi @ricardoquesada - the first bug was actually that the wrong packet handler was registered. With that in place, the state is set back to connected correctly. However, there was no event that indicates that the write is complete. I've changed the code to emit an empty GATTSERVICE_SUBEVENT_HID_REPORT. What do you think about this? Does this work for you? |
mringwal
added a commit
that referenced
this issue
Apr 17, 2024
…ds_client_send_write_report, fix #573
|
Thanks. works great. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After calling
hids_client_send_write_report(), the client state does not return toHIDS_CLIENT_STATE_CONNECTED.It remains on
HIDS_CLIENT_W4_WRITE_REPORT_DONE.To Reproduce
Just call
hids_client_send_write_report().It seems that
handle_report_eventis ignoring theGATT_EVENT_QUERY_COMPLETEevent triggered bygatt_client_write_value_of_characteristic(), and the client state remains atHIDS_CLIENT_W4_WRITE_REPORT_DONEThe text was updated successfully, but these errors were encountered: