-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_19_6_Client_GAPP: Timer Stop command never issued #48
Comments
My solution is to update the ble_gap_event BLE_GAP_EVENT_SUBSRIBE case to:
|
I have encountered the same issue. I implemented the fix in a similar way like yours. The only difference is that I updated config[0]. I don't think that is needed. I did it anyway. (My code)
I also found another problem. When I switched from notification to read, the battery level is fixed at 50 (not correct). I made a small change to use the global updated variable battry in the battry_level subroutine.
It is a good example. It needs updated to work with other mobile BLE apps (nRF Connect, Bluefruit, LightBlue) that do not allow me to write directly to the battery client configuration descriptor directly. It seems that the teacher has an app that does. Best, |
Hi Phil, I checked Espressif's standard Heart Rate measurement BLE peripheral. It follows your approach. I think you did the right way. https://github.com/espressif/esp-idf/tree/master/examples/bluetooth/nimble/blehr
|
In _19_6_Client_GAPP the timer remains running even when a client unsubscribes.
This behaviour does not match the tutorial.
The text was updated successfully, but these errors were encountered: