jjross
April 10, 2023, 9:44pm
1
I just noticed the following in my logs:
Zigbee channel 11 utilization is 92.06%!
If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.0
I have been having problems with my Zigbee mesh but I assumed that it was because I am using a Tasmota flashed ZBBridge (I wanted to switch to an ethernet bridge but haven’t yet).
How can I swap the channels ZHA is using and more importantly, how can I tell which channels might be more open than 11?
1 Like
jjross
April 10, 2023, 11:32pm
2
OK, so I figured this out. I used the radio migration feature to build a new ZHA network after I updated the configuration to set to channel 15.
It’s odd that my network was running on 11 as I never selected that channel and 15 is the default. Regardless, we’ll see how this goes. I did have to repair everything but that’s ok. It actually exposed some additional features in some devices that I had never seen before.
jjross
April 11, 2023, 1:38am
3
Well now I’m getting this:
* Zigbee channel 15 utilization is 87.33%!
* If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
* Zigbee channel 15 utilization is 85.82%!
* Zigbee channel 15 utilization is 84.16%!
* Zigbee channel 15 utilization is 80.38%!
So I guess I need to find a better channel but after all the work to swap to this one I might leave it for a little and see how things go.
Any reason my utilization would increase over time like that?
Hedda
(Hedda)
April 11, 2023, 8:47am
4
Believe that word ”utilization” is maybe a poor choice of word for that message since I understand that it is really only sensing the total amount of energy/power for that Zigbee channel as to indicate interference. See → Guide for Zigbee interference avoidance and network range/coverage optimization
jjross
April 11, 2023, 4:04pm
5
OK, understood. Odd because the interference seems to be rising:
Zigbee channel 15 utilization is 98.79%!
If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
Zigbee channel 15 utilization is 95.69%!
Zigbee channel 15 utilization is 97.39%!
Zigbee channel 15 utilization is 97.70%!
I don’t think I have an under utilized channel I can switch to.
Rofo
(Ro)
May 11, 2023, 2:59pm
6
I understand this new warning message turned up in 2023.4.x
I’m guessing that the threshold to display the message is 75%, because i never see it with a value lower than 75.96%, but often as high as 92%
However, it seems to be very inconsistent. Sometimes if I restart HA or ZHA, I get the error, and sometimes not at all, only a minute or two apart from each event, and with the coordinator in the same position, and nothing else physically changed in the environment.
Any ideas whats going on ?
Did you, by using migration, need to re-pair all your devices? Am also facing issues on default channel 11 and want to move all of it to channel 25, but would prefer not having to re-pair all devices in the house…
Hedda
(Hedda)
June 1, 2023, 6:19am
8
FYI, ZHA integration in the upcoming release version of Home Assistant will include a UI for changing Zigbee channel. It will still depend on your Zigbee Coordinator and your specific Zigbee devices if you need to repair some devices (especially battery-powered Zigbee devices are known to be bad at changing channels so some or all of those may need to be re-paired if you change the channel).
1 Like
Yardco
(Yardco)
June 1, 2023, 8:37am
9
Are you talking about 2023.6? Because its currently not mentioned in the beta release notes
Hedda
(Hedda)
June 1, 2023, 11:20am
10
Yes, see PRs, (they usually do not update Home Assistant release notes until just before the release).
This new experimental feature that puddly added now allows users of the ZHA integration to perform Zigbee channel migration directly from the UI for all supported radio types without the need to re-pair all devices or have any entities changed.
ZNP (Texas Instruments) based devices currently has the best implementation of Zigbee channel changing as it allows the Zigbee Coordinator to change Zigbee channels after having a few chances to send out the broadcast to all the devices. Other Zigbee Coordinator adapters (e.g. Silicon Labs EZSP and Dresden Elektronik’s deconz based radios) instead migrate/change the Zigbee channel almost immediately, giving Zigbee End Devices (e.i. battery-powered devices) a smaller window of receiving the channel change request broadcast, however, such devices still have a chance of finding the network again if they detect that they have been orphaned.
Modern mains-powered devices should normally all change channels without any problems. After waiting a while for all devices to change channels automatically the general recommendation is then to perform a power cycle of devices that did not automatically change channels (usually simply by removing and replacing the battery) before just re-pairing those devices in the ZHA integration.
“Currently, ZNP implements the best version of this API because it allows the coordinator to change channels after having a few chances to send out the broadcast. Other coordinators (EZSP and deCONZ) directly react to the loopback request and migrate almost immediately. This rudimentary version has been implemented in zigpy-cli for some time and has been used by a few people to migrate their networks. From what I can tell, if an end device does not react to the channel change broadcast, it definitely won’t with a unicast request. But it still might find the network again after detecting that it has been orphaned. ”
Before
After
home-assistant:dev
← puddly:puddly/20230501-zha-channel-changing-ui
opened 06:21PM - 02 May 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue or discussion
in the additional information section.
-->
Redesign the ZHA network settings section and incorporate a button and dialog to change the current channel:
### Before
<img width="506" alt="before" src="https://user-images.githubusercontent.com/32534428/235757898-14e6b56d-1d04-4594-b08e-c5e4aafa2aca.png">
### After
<img width="561" alt="after" style="width: 49%" src="https://user-images.githubusercontent.com/32534428/235718415-2a2bd858-8b9c-4127-bb6c-1acff7ff308e.png">
</div>
<img width="643" alt="image" src="https://user-images.githubusercontent.com/32534428/235751913-c7238046-b720-4f3d-bb8a-c14c924eee16.png">
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [x] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example configuration
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] There is no commented out code in this PR.
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
home-assistant:dev
← puddly:puddly/zha-channel-26-missing
opened 07:21PM - 06 Jun 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue or discussion
in the additional information section.
-->
https://github.com/home-assistant/frontend/pull/16381 accidentally omitted channel 26 from the list even though it is a valid channel.
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example configuration
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] There is no commented out code in this PR.
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
home-assistant:dev
← puddly:puddly/zha-channel-changing
opened 06:17PM - 26 Apr 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Exposes the ZHA channel changing API from #91969 as a websocket API.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
home-assistant:dev
← puddly:puddly/zha-deps-bump-20230424
opened 08:20PM - 24 Apr 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Bump ZHA dependencies:
- zigpy-deconz to [0.21.0](https://github.com/zigpy/zigpy-deconz/releases/tag/0.21.0)
- zigpy to [0.55.0](https://github.com/zigpy/zigpy/releases/tag/0.55.0)
- zigpy-xbee to [0.18.0](https://github.com/zigpy/zigpy-xbee/releases/tag/0.18.0)
- zigpy-zigate to [0.11.0](https://github.com/zigpy/zigpy-zigate/releases/tag/0.11.0)
- zigpy-znp to [0.11.1](https://github.com/zigpy/zigpy-znp/releases/tag/v0.11.1)
This implements channel migration for all radios and fixes a bug with energy scanning for ZiGate radios. A future PR will add this functionality to ZHA.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [x] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #91467, #91014
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
home-assistant:dev
← puddly:puddly/zha-api
opened 07:59PM - 21 Feb 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
ZHA has a websocket API to read network settings from a running coordinator, but it does not have an API to read network settings with Python alone. This PR implements the latter and includes a way to read network settings with a fallback to reading them from `zigbee.db`.
#### This PR appears large only because I renamed `zha/api.py` to `zha/websocket_api.py`.
The main addition is `async_get_network_settings`: if there is an active network, those settings are used. Otherwise, if ZHA is inactive but there is still ZHA state in the `/config/` folder, the database is used. Otherwise, `None` is returned.
`async_get_radio_type` and `async_get_radio_path` are also added to provide a public API to read this information from the ZHA config entry.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
zigpy:dev
← puddly:puddly/channel-changing
opened 05:31PM - 06 Apr 23 UTC
See #1185 (@dumpfheimer).
Currently, ZNP implements the best version of this … API because it allows the coordinator to change channels after having a few chances to send out the broadcast. Other coordinators (EZSP and deCONZ) directly react to the loopback request and migrate almost immediately.
This rudimentary version has been implemented in zigpy-cli for some time and has been used by a few people to migrate their networks. From what I can tell, if an end device does not react to the channel change broadcast, it definitely won't with a unicast request. But it still might find the network again after detecting that it has been orphaned.
Thoughts?
PS: You should however note that changing the Zigbee channel is not a magic bullet for reception/transceiving-related issues, so users probably want to refer to ZHA integration documentation’s new troubleshooting section on interference and range/coverage optimization tips as well as this related discussion → Guide for Zigbee interference avoidance and network range/coverage optimization
1 Like
I moved the first devices from ZHA channel 15 to Z2M channel 22 and am very satisfied with the result; no more devices going unknown and very fast respons of devices.
2 Likes
Yardco
(Yardco)
June 3, 2023, 9:08am
12
Upgraded my install to the beta to try out the Zha channel migration feature yesterday. The majority of my devices (apart from a handful of battery devices) automatically followed the coordinator to the new channel, pretty smooth switching experience imo!
1 Like
jjross
June 7, 2023, 4:55am
13
I did have to. I would wait for 2023.6 if I were you. Honestly, once I moved the channel I still got the message so not sure what I can do now.
@jjross are you still having this issue with the current version?
jjross
August 9, 2023, 4:05am
15
I am, yes. Seems all channels are full.
1 Like
niker
(Niker)
July 16, 2024, 11:24pm
16
Hello,
just dropping this here, because it may be useful to people on congested zigbee networks. This tool is like a DIY wifi scanner tool, it should help you decide which channel to use. It is experimental, any feedback is welcome.
beaj
(Brian Johnstone)
July 17, 2024, 5:50am
17
Further to niker’s post -
One of the challenges faced with creating a stable zigbee installation is potential channel interference in the crowded 2.4GHz band.
There is the often reference Metageek Zigbee-Wifi coexistence article which is helpful in understanding where channels sit within that band. If you have ZHA installed there is also the option to perform an energy-scan to get a rudimentary view of RF energy within each zigbee channel. This is useful but is just a point in time snapshot. There is also the zigpy-cli …
This will produce a sensor for each channel enabling a better view of utilisation over time.
~Brian