home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.18k stars 31.14k forks source link

Allow configuration of Thread channel for OTBR #91475

Open jhbruhn opened 1 year ago

jhbruhn commented 1 year ago

The problem

When creating a Thread network using HA Yellow or SkyConnect and the Silabs Multiprotocol Plugin, Thread channel 15 is chosen when using a Zigbee Coordinator which is not ZHA (e.g. Zigbee2MQTT). This leads to unstable networks.

If there is no possibility of detecting the Zigbee Channel automatically, allow the user to specify a channel number manually, for example when resetting the OTBR.

What version of Home Assistant Core has the issue?

core-2023.4.4

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

OTBR

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

See related issue https://github.com/home-assistant/addons/issues/2974

home-assistant[bot] commented 1 year ago

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

Code owner commands Code owners of `otbr` 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 otbr` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


otbr documentation otbr source (message by IssueLinks)

issue-triage-workflows[bot] commented 1 year ago

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.

jhbruhn commented 1 year ago

Still not resolved.

Cursed stale bot doing cursed things.

issue-triage-workflows[bot] commented 1 year ago

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.

jhbruhn commented 1 year ago

afaik not yet resolved

baylf2000 commented 1 year ago

@jhbruhn Thread in HA doesn't seem to be getting much love at the moment. The OTBR integration hasn't had an update in months.

imkermichel commented 1 year ago

OTBR channel is set in Thread. go to thread in devices, klick configure, klick 3 dots.

0x556c79 commented 1 year ago

@imkermichel Unfortunately this does not work. At least with me. If I look at the otbr log, something happens when I change the channel and after 5 minutes something is reconfigured but the channel remains at 15.

Is it possible to use SkyConnect with the Tread only firmware for Tread and Rasbeen II for ZigBee via ZHA?

IIAIronWolf commented 10 months ago

I just bought an nRF52840 to use with the OpenThread add-on as a Thread Border Router, and the add-on documentation has a link for updating the dongle that no longers works. Really wish this add on would get more attention.

magicmatt007 commented 9 months ago

I also have an RF52480 USB dongle. As the link provided in the add-on for updating the FW doesn't work, I followed the instructions for "Configuring a radio co processor" on https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/thread/tools.html#ug-thread-tools-tbr-rcp

To test the FW, I then followed "Running OTBR using Docker" on my Linux desktop. The USB stick seems to work with it.

However, if I use that USB stick with the HA OTBR add-on, it doesn't work....

Notes:

Any advise?

issue-triage-workflows[bot] commented 6 months ago

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.

akarabach commented 6 months ago

still a problem

issue-triage-workflows[bot] commented 3 months ago

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.

akarabach commented 3 months ago

still a problem

issue-triage-workflows[bot] commented 1 week ago

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.

akarabach commented 1 week ago

still a problem