-
Notifications
You must be signed in to change notification settings - Fork 18
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
Channel energy scan #149
Channel energy scan #149
Conversation
The energy scanning API is expected to return a number between 0 and 255, with 0 being "low" and 255 being "high". This is to make values comparable across radios, since all others return a number 0-255. In bellows, I implemented it like so: https://github.com/zigpy/bellows/blob/58f8a8079a6fa1d25fe536e5d9e3fcfcbf41389c/bellows/zigbee/util.py#L105-L132. |
Thanks! Will update the code. |
Fixed.
|
Rebased and added tests |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #149 +/- ##
==========================================
+ Coverage 98.86% 99.13% +0.26%
==========================================
Files 6 6
Lines 793 807 +14
==========================================
+ Hits 784 800 +16
+ Misses 9 7 -2
☔ View full report in Codecov by Sentry. |
Add support for per-channel energy detect for XBee coordinators.
Logs:
Prtially implements #112 though it is not a stand-alone tool.