-
Notifications
You must be signed in to change notification settings - Fork 20
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
Handle cancellation while waiting for an encrypted IP response #354
Conversation
Only fixes the IP controller. BLE and coap likely have similar issues home-assistant/core#97888
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #354 +/- ##
==========================================
+ Coverage 74.50% 74.60% +0.09%
==========================================
Files 99 99
Lines 9301 9320 +19
==========================================
+ Hits 6930 6953 +23
+ Misses 2371 2367 -4 ☔ View full report in Codecov by Sentry. |
# If we get a timeout or any other exception then we need to | ||
# close the connection as we are now out of sync with the device | ||
# and any future requests will fail since the encryption counters | ||
# will be out of sync. |
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.
We might be able to redo the pair verify and start over but I doubt devices handle that well so I think the safest thing to do is close and reopen to ensure good state
thanks. will push a release shortly if everything passes on 3.12 as well |
Only fixes the IP controller. BLE and coap likely have similar issues. I will fix BLE as well but I don't use coap so no way to test that one
home-assistant/core#97888