Open Teagan42 opened 1 month ago
I received the same error (Platform------: Init() at spinel_driver.cpp:82: Failure
) when running natively on an RPI (tried with both RPI3 and RPI4) with linux when using the SkyConnect stick flashed with the OTBR firmware (i.e. not on Home Assistant) . So I suspect the issue might be the firmware on the stick rather than something HA side
Was there a new version of the firmware released recently? It could be a firmware bug if its not OS specific - I'd be happy to load an old version of the firmware and give it a try if you give me a link to where I can download it
I have the same issue, but I'm using OTBR in docker
I have this issue since today too. All my Matter devices are offline
I have the same issue. I use a SLZB-06M [Kernel Version: 2.3.6 | Radio Version: 20241105 | Matter-over-Thread (Beta)]
----------------------------------------------------------- Add-on: OpenThread Border Router OpenThread Border Router add-on ----------------------------------------------------------- Add-on version: 2.9.0 You are running the latest version of this add-on. s6-rc: info: service socat-otbr-tcp successfully started System: Home Assistant OS 12.4 (amd64 / qemux86-64) Home Assistant Core: 2024.7.3 Home Assistant Supervisor: 2024.06.2 ----------------------------------------------------------- Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat. ----------------------------------------------------------- s6-rc: info: service banner successfully started s6-rc: info: service universal-silabs-flasher: starting [15:23:02] INFO: Flashing firmware is disabled s6-rc: info: service universal-silabs-flasher successfully started s6-rc: info: service otbr-agent: starting [15:23:02] INFO: Starting otbr-agent... tiocmget: Inappropriate ioctl for device [NOTE]-AGENT---: Running 0.3.0-41474ce-dirty [NOTE]-AGENT---: Thread version: 1.3.0 [NOTE]-AGENT---: Thread interface: wpan0 [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800 [NOTE]-AGENT---: Radio URL: trel://enp2s1 [NOTE]-ILS-----: Infra link selected: enp2s1 [INFO]-NCP-----: OpenThread log level changed to 5 53d.19:34:45.686 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET 53d.19:34:45.686 [D] P-SpinelDrive-: Waiting response: key=0 53d.19:34:47.688 [W] P-SpinelDrive-: Wait for response timeout 53d.19:34:47.688 [I] P-SpinelDrive-: co-processor self reset successfully 53d.19:34:47.688 [D] P-SpinelDrive-: Waiting response: key=1 53d.19:34:49.690 [W] P-SpinelDrive-: Wait for response timeout 53d.19:34:49.690 [D] P-SpinelDrive-: Waiting response: key=1 53d.19:34:51.692 [W] P-SpinelDrive-: Wait for response timeout 53d.19:34:51.692 [C] Platform------: Init() at spinel_driver.cpp:82: Failure 53d.19:34:51.692 [D] P-SpinelDrive-: Waiting response: key=1 53d.19:34:53.694 [W] P-SpinelDrive-: Wait for response timeout [15:23:10] WARNING: otbr-agent exited with code 1 (by signal 0). [15:23:10] INFO: OTBR firewall teardown completed. s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died s6-rc: warning: unable to start service otbr-agent: command exited 1 s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service universal-silabs-flasher: stopping s6-rc: info: service socat-otbr-tcp: stopping s6-rc: info: service mdns: stopping /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service universal-silabs-flasher successfully stopped s6-rc: info: service banner: stopping 2024/07/23 15:23:10 socat[74] W exiting on signal 15 Default: mDNSResponder (Engineering Build) (Jul 2 2024 09:04:20) stopping s6-rc: info: service socat-otbr-tcp successfully stopped s6-rc: info: service banner successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped [15:23:10] INFO: mDNS ended with exit code 4 (signal 0)... s6-rc: info: service mdns successfully stopped`
So after digging through the manufacturer documentation, I think I figured it out!
When the baud rate is set to the default, I get this error. After updating it to 460800, the error resolved itself
So after digging through the manufacturer documentation, I think I figured it out!
When the baud rate is set to the default, I get this error. After updating it to 460800, the error resolved itself
didnt help for me
So after digging through the manufacturer documentation, I think I figured it out!
When the baud rate is set to the default, I get this error. After updating it to 460800, the error resolved itself
me neither
I have the same issue and proposed solution didn't help
I have the same error!
Is there any way to downgrade to 2.8.0. without a backup? Sadly I just did a fresh installation of HA.
I just wanted to throw this here because I came across the same thing running the openthread container with the nrf52840 MDK. The fix for me was to add "uart-baudrate=1000000&uart-flow-control". Credit goes to this issue: https://github.com/openthread/openthread/issues/10538.
I also tried using a spare SkyConnect dongle (configured the add-on to flash firmware), which resulted in the same errors.
SkyConnect requires you enable flow control. It appears that nRf dongle may also require this.
The fix for me was to add "uart-baudrate=1000000&uart-flow-control"
For those using the addon, just enable the flow control button in configuration.
As of recently, I found myself in the same situation after it has been working fine for a while.
After a reboot of my Synology NAS, the serial USB driver for a ZBT-1 is correctly loaded:
$ dmesg | grep -Fi usb
[52258.716119] usb 1-3: cp210I x converter now attached to ttyUSB0
$ lsusb -cui
|__usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (Linux 4.4.302+ xhci-hcd xHCI Host Controller 0000:09:00.3) hub
|__1-1 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (Synology DiskStation 650026E98013F214)
1-1:1.0 (IF) 08:06:50 2EPs () usb-storage host7 (synoboot)
|__1-3 10c4:ea60:0100 00 2.00 12MBit/s 100mA 1IF (Nabu Casa SkyConnect v1.0 8eb63fd4089bed1184547708a8669f5d)
1-3:1.0 (IF) ff:00:00 2EPs () cp210x ttyUSB0
This device is attached to a virtual machine running HAOS with the otbr addon.
When I start OTRB, I get the Init() at spinel_driver.cpp:82: Failure
error:
[13:55:48] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-08-16 13:55:48.915 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.0', ezsp_version=None, ot_rcp_version='SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0), cpc_version=None, fw_type=<FirmwareImageType.OT_RCP: 'ot-rcp'>, baudrate=460800)
2024-08-16 13:55:48.915 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-08-16 13:55:50.958 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2024-08-16 13:55:50.999 homeassistant universal_silabs_flasher.flasher INFO Detected ApplicationType.SPINEL, version 'SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0) at 460800 baudrate (bootloader baudrate None)
2024-08-16 13:55:50.999 homeassistant universal_silabs_flasher.flash INFO Firmware version 'SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[13:55:51] INFO: Setup OTBR firewall...
[13:55:51] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-41474ce-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=115200&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://enp0s3
[NOTE]-ILS-----: Infra link selected: enp0s3
49d.20:26:11.560 [W] P-SpinelDrive-: Wait for response timeout
49d.20:26:13.562 [W] P-SpinelDrive-: Wait for response timeout
49d.20:26:15.565 [W] P-SpinelDrive-: Wait for response timeout
49d.20:26:15.565 [C] Platform------: Init() at spinel_driver.cpp:82: Failure
49d.20:26:17.567 [W] P-SpinelDrive-: Wait for response timeout
[13:55:59] WARNING: otbr-agent exited with code 1 (by signal 0).
This seems to cause a USB disconnect:
$ dmesg | grep -Fi usb
[52300.582799] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
And the serial module is no longer used for the ZBT-1 (changed to usbfs
):
$ lsusb -cui
|__usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (Linux 4.4.302+ xhci-hcd xHCI Host Controller 0000:09:00.3) hub
|__1-1 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (Synology DiskStation 650026E98013F214)
1-1:1.0 (IF) 08:06:50 2EPs () usb-storage host7 (synoboot)
|__1-3 10c4:ea60:0100 00 2.00 12MBit/s 100mA 1IF (Nabu Casa SkyConnect v1.0 8eb63fd4089bed1184547708a8669f5d)
1-3:1.0 (IF) ff:00:00 2EPs () usbfs
I was able to work around the issue by setting autoflash_firmware: false
.
Describe the issue you are experiencing
I have been successfully utilizing a nrf52840 MDK USB dongle, flashed with OTBR RPC firmware using west/zephyr as described by NRF52/openthread.io documentation https://openthread.io/codelabs/openthread-hardware#1, for the last year. Upon upgrading the OTBR addon to 2.9.0, the OTBR agent fails to start due to spinel_driver error/timeout (see addon logs). I was able to work around this breaking change by downloading the 2.8.0 OTBR addon and installing it as a local addon.
I also tried using a spare SkyConnect dongle (configured the add-on to flash firmware), which resulted in the same errors.
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.9.0
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4999 Installed Version | 1.34.0 Stage | running Available Repositories | 1398 Downloaded Repositories | 52 HACS Data | okHome Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.4 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.2 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 110.5 GB disk_used | 52.2 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | Whisper (2.1.2), Piper (1.5.0), Advanced SSH & Web Terminal (18.0.0), ESPHome (2024.6.6), Studio Code Server (5.15.0), openWakeWord (1.10.0), Matter Server (6.2.1), EMQX (0.6.0), OpenThread Border Router (2.8.0)Dashboards
dashboards | 6 -- | -- resources | 34 views | 15 mode | storageRecorder
oldest_recorder_run | June 5, 2024 at 5:41 PM -- | -- current_recorder_run | July 6, 2024 at 2:33 AM estimated_db_size | 8841.11 MiB database_engine | postgresql database_version | 16.2Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
No response