-
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
Add support for encrypted notifications #197
Conversation
Codecov ReportBase: 69.63% // Head: 68.29% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #197 +/- ##
==========================================
- Coverage 69.63% 68.29% -1.35%
==========================================
Files 71 71
Lines 6152 6361 +209
==========================================
+ Hits 4284 4344 +60
- Misses 1868 2017 +149
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
It looks like these are widely supported I haven't been able to get anything to give up a key yet but I think I might need to turn at least one on first |
home-assistant/core#80733 to open up the filter |
Works well with dropped advertisements as well as the the next adv gets picked up and it makes a connection |
Found a race on first connection |
Tested with my Eve Motion first, it was just the first thing i pulled out my drawer:
Success! |
An
|
…ve been since it calls put_characteristics which is wrapped
verified its recovering ok when accessory isn't available at startup. |
We now try to get the char change via an encrypted notification instead of a disconnected
event when possible. This avoids the need to connect to the accessory for changes that
are made to it from outside of aiohomekit which drastically speeds up updates and frees
up BLE connection slots.