-
Notifications
You must be signed in to change notification settings - Fork 208
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
Clear characteristic cccd value when disconnect #376
base: master
Are you sure you want to change the base?
Conversation
Memory usage change @ d909b6c
Click for full report table
Click for full report CSV
|
Hi @fabik111. Thanks for your pull request. Please disregard the failed spell check. This is a spurious failure caused by bit rot in the antiquated infrastructure used for that check, nothing to do with the changes you propose here. The failed check won't block the reviewers from merging your PR and we'll be sure to fix the broken spell check system separately ASAP. |
d909b6c
to
2355c4d
Compare
Memory usage change @ 2355c4d
Click for full report table
Click for full report CSV
|
Problem
If the peripheral sketch with a subscribeable characteristic closes the connection with the central calling the
BLE.disconnect()
all subsequent subscriptions, after the first connection, are not notified and the characteristic stays always as "subscribed".Solution
In this PR the characteristic CCCD value is cleared when the BLE.disconnect() is called for resetting the characteristic subscription status and allowing new subscriptions.
Sketches for reproducing the problem
Central
Peripheral
Logs
Here the logs of the current behaviour.
Central
Peripheral