-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
OTBR with SkyConnect non-functional with error:InvalidArgs, quits unexpectedly #3447
Comments
Same here. |
Same issue here, same errors, and not able to commission a Eve Smart Plug with Thread support. |
I've found anything above 2.4.3 drops the whole system. I'd downgrade for now. |
How can I downgrade the addon to a specific version? |
Can reproduce still: otbr-agent[181]: 00:00:07.822 [N] RouterTable---: Allocate router id 19 |
The
However, the radio tx timeout is though:
@therealmrfox thee latest OTBR add-on 2.4.6 should properly shutdown. If you enable the watchdog functionality, this will restart the add-on automatically. Now of course this is more of a work around, but might help in your case. Do the
You probably have to sync the Thread credentials first. See the our integration documentation of Turning Home Assistant into a Thread border router (specifically Case 1: Making Home Assistant your first Thread network). |
@marbon87 only through backups. Normally when upgrading a partial backup is being made. You can restore that particular backup. @Jordenjj do you have the same @Callum6677 the |
@agners I tried iOS app versions 2024.1 (2024.535) and 2024.2 (2024.545). |
@rolf-tx transfering the Thread credentials into iOS is not yet supported, but should soon follow. Currently you can only join an existing Thread network, e.g. when you have an Apple Thread Border router already. |
Well do I feel like an idiot. Sure enough - this was my problem. I completely missed this step. Happy to report that I can now commission Matter devices! It does seem odd that these
No, it happens randomly after a couple of hours. Haven't observed it with 2.4.6 yet, will report here if I do.
Restarting OTBR seems to make some - though strangely, not all - Matter devices unresponsive without also restarting the Matter server. In particular an Eve motion sensor becomes inoperable after a OTBR restart; Aqara door sensors don't mind. Could probably set up some automation to restart Matter as a band aid. Thank you @agners for looking into this - very much appreciated! |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the issue you are experiencing
OTBR configured with SkyConnect in Thread-only mode never gets into a functional state.
Installed OTBR add-on, Thread and OTBR integrations were added to HA, and
homeassistant.local
shows up as the preferred (and only) network in the Thread integration. When attempting to commission a device (Android companion app) the process fails with “Your device requires a Thread border router”.I suspect this is because the OTBR add-on fails to properly start. The log is full of errors such as
The add-on (perhaps not directly related to the first issue?) also after a few hours quits with the following error:
Both issues are consistently reproducible. I started with a clean slate (SkyConnect fresh out of the box, never had zigbee or multiprotocol installed). Rebooted a gogo, Deleted and reinstalled OTBR add-on, thread integration, and OTBR integration several times with the same outcome.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
OpenThread Border Router
What is the version of the add-on?
2.4.5
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
HAOS is running on an RPi 3. IPv6 is enabled (SLAAC) and working fine.
Similar issues:
Related forum discussions:
The text was updated successfully, but these errors were encountered: