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
esp32_ble: Consider ESP_BT_STATUS_DONE a successful state #6493
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #6493 +/- ##
==========================================
- Coverage 53.70% 53.43% -0.28%
==========================================
Files 50 50
Lines 9408 9537 +129
Branches 1654 1685 +31
==========================================
+ Hits 5053 5096 +43
- Misses 4056 4130 +74
- Partials 299 311 +12 ☔ View full report in Codecov by Sentry. |
fcedc32
to
50b43c0
Compare
Sooo, anything else that needs to happen? I consider this ready to be reviewed |
50b43c0
to
55fa9a6
Compare
@clydebarrow Could you please have a glance? |
Co-authored-by: Clyde Stubbs <2366188+clydebarrow@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks! |
Co-authored-by: Clyde Stubbs <2366188+clydebarrow@users.noreply.github.com>
What does this implement/fix?
This fixes the log messages below from repeatedly being written:
The issue seems to arise from BT_STATE_DONE being interpreted as an error. Following the documentation for this value leads to
packages/framework-espidf/components/bt/common/include/bt_common.h
describing it asrequest already completed
. Assuming that whatever was being performed is idempotent, mapping this state to success should be ok.Types of changes
Related issue: esphome/issues#4058
Test Environment
Example entry for
config.yaml
:Checklist:
tests/
folder).