addons: OpenThread/Multi-Protocol addon starts erroring and bootlooping after a couple days

Not entirely sure of the root cause, just had everything working last night, woke up and it’s all broken. 3rd time this has happened now and the only solution I’ve found is a full power down (even rpi reboot doesn’t help). Here are the addon logs from a fresh addon restart. It just repeats the last two times over and over until the watchdog restarts it continually.

Full log after a fresh restart:

s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mdns successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/check-cpcd-shm.sh
[15:18:59] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 12 2023 14:23:29) starting
Default: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
cont-init: info: /etc/cont-init.d/check-cpcd-shm.sh exited 0
cont-init: info: running /etc/cont-init.d/config.sh
[15:19:00] INFO: Generating cpcd configuration.
cont-init: info: /etc/cont-init.d/config.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service banner: starting
-----------------------------------------------------------
 Add-on: Silicon Labs Multiprotocol
 Zigbee and OpenThread multiprotocol add-on
-----------------------------------------------------------
 Add-on version: 0.11.4
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.4  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.1.7
 Home Assistant Supervisor: 2023.01.0
-----------------------------------------------------------
 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:19:03] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd: starting
[15:19:03] INFO: Starting cpcd...
WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #188 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[15:19:03:992] Info : [CPCd v4.2.0.0] [Library API v3] [RCP Protocol v3]
[15:19:03:992] Info : Git commit: 2036da8fa5aa7bd42b127b5bb603cab7a49e6fcd / branch: 
[15:19:03:992] Info : Sources hash: 5454a76205641ee86fd40f458cb0920c0d010fec5702a25faa3c902b7e119596
[15:19:03:992] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #188 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[15:19:03:992] Info : Reading cli arguments
[15:19:03:992] Info : /usr/local/bin/cpcd 
[15:19:03:998] Info : Reading configuration
[15:19:03:998] Info : file_path = /usr/local/etc/cpcd.conf
[15:19:03:998] Info : instance_name = cpcd_0
[15:19:03:998] Info : socket_folder = /dev/shm
[15:19:03:998] Info : operation_mode = MODE_NORMAL
[15:19:03:998] Info : use_encryption = false
[15:19:03:998] Info : binding_key_file = /etc/binding-key.key
[15:19:03:998] Info : binding_key_override = false
[15:19:03:998] Info : binding_method = 
[15:19:03:998] Info : stdout_tracing = false
[15:19:03:998] Info : file_tracing = false
[15:19:03:998] Info : lttng_tracing = false
[15:19:03:998] Info : enable_frame_trace = false
[15:19:03:998] Info : traces_folder = /dev/shm/cpcd-traces
[15:19:03:998] Info : bus = UART
[15:19:03:998] Info : uart_baudrate = 115200
[15:19:03:998] Info : uart_hardflow = true
[15:19:03:998] Info : uart_file = /dev/ttyUSB2
[15:19:03:999] Info : spi_file = /dev/spidev0.0
[15:19:03:999] Info : spi_bitrate = 1000000
[15:19:03:999] Info : spi_mode = SPI_MODE_0
[15:19:03:999] Info : spi_bit_per_word = 8
[15:19:03:999] Info : spi_cs_chip = gpiochip0
[15:19:03:999] Info : spi_cs_pin = 8
[15:19:03:999] Info : spi_irq_chip = gpiochip0
[15:19:03:999] Info : spi_irq_pin = 22
[15:19:03:999] Info : fu_reset_chip = gpiochip0
[15:19:03:999] Info : fu_spi_reset_pin = 23
[15:19:03:999] Info : fu_wake_chip = gpiochip0
[15:19:03:999] Info : fu_spi_wake_pin = 24
[15:19:03:999] Info : fu_recovery_enabled = false
[15:19:03:999] Info : fu_connect_to_bootloader = false
[15:19:03:999] Info : fu_enter_bootloader = false
[15:19:03:999] Info : fu_file = 
[15:19:03:999] Info : fu_restart_daemon = false
[15:19:03:999] Info : board_controller_ip_addr = 
[15:19:03:999] Info : application_version_validation = false
[15:19:03:999] Info : print_secondary_versions_and_exit = false
[15:19:03:999] Info : use_noop_keep_alive = false
[15:19:03:999] Info : reset_sequence = true
[15:19:03:999] Info : uart_validation_test_option = 
[15:19:03:999] Info : stats_interval = 0
[15:19:03:999] Info : rlimit_nofile = 2000
[15:19:03:999] Info : ENCRYPTION IS DISABLED 
[15:19:03:999] Info : Starting daemon in normal mode
[15:19:04:017] Info : Connecting to Secondary...
[15:19:06:018] Info : Failed to connect, secondary seems unresponsive
[15:19:06:018] Info : Connecting to Secondary...
[15:19:08:018] Info : Failed to connect, secondary seems unresponsive
[15:19:08:018] Info : Connecting to Secondary...
[15:19:10:018] Info : Failed to connect, secondary seems unresponsive
[15:19:10:018] Info : Connecting to Secondary...

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 29

Most upvoted comments

I switched my SkyConnect to the Thread only firmware and now the OTBR works fine. Now I have IPv6 issues 😃

I have similar issues with SONOFF Zigbee 3.0 USB Dongle V2. Physically disconnecting the dongle and reconnecting seems to fix the problem for a few days.

 Add-on: Silicon Labs Multiprotocol
 Zigbee and OpenThread multiprotocol add-on
-----------------------------------------------------------
 Add-on version: 2.3.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.2  (amd64 / qemux86-64)
 Home Assistant Core: 2023.12.3
 Home Assistant Supervisor: 2023.12.0

There is a similar discussion on the HA forum https://community.home-assistant.io/t/messed-up-ha-by-installing-sonoff-zigbee-3-0-usb-dongle-plus-e-and-silicon-labs-multiprotocol/625826

Pfff, I just noticed a document of Silicon Labs mentioning an incompatability of Bluetooth devices with Thread. I removed my USB passtrough from my Home Assistant VM running in ESXi 7 U3o and rebooted the Sillion Labs multiprotocol addon. Error is gone… so this is not a ‘fix’, but this might get us in the right direction.

Disabling bluetooth on my pi4 did not help

Yeah, did not last very long for me either. Think I just had some brief luck…

Edit: I think this part may be because I had the auto firmware updater shut off? A better error message might be helpful there.

I’d leave it at the default value. Allowing auto-flashing to be disabled is really there for debugging purposes or if you run the multi-PAN addon with another Zigbee stick that needs its own firmware.