Thread with Open Thread Border Router will only use channel 21

[HaydnIngram]

The problem

Using an OTBR port for OpenWrt. It is a rather unorthodox setup with many required work-rounds. I am confident that this alone is not causing the issue here since there are no similar problems found when using CHIP tool for commissioning Matter devices.

I saw that in the information pulled from the OTBR's REST API inside the Thread integration will always have "channel" attribute recorded as 21 (that is viewed by pressing the (i) info button). This often differed from what the OTBR used itself, and can be seen by using the API myself. After repeatedly restarting my OTBR agent until it had the channel of 21, I finally had success when trying to commission Matter devices over Thread on HA.

Since it is down luck whether the channels match, I doubt I have been lucky enough to avoid this for so long. This leads me to believe the problem has been introduced in a fairly recent update somewhere.

This could either be a problem with Thread or OpenThread integration. Perhaps, if no one else has experienced this, it has something to do with my setup and unorthodox OTBR implementation instead.

I am unsure what logs to provide, there isn't any crashing. I am fairly new here too and I am unsure on what resources can help with replication. I am more than happy to retrieve logs / resources upon request.

I apologise if this turns out to be an error unique to only my setup. Thought it would be best to play it safe and create this issue.

Screenshot of described information button. Channel attribute is always 21, regardless of what the actual OTBR uses.

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Thread

Link to integration documentation on our website

https://www.home-assistant.io/integrations/thread/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (thread) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `thread` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign thread` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

thread documentation thread source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.