Silicon Labs Multiprotocol is not starting after power outage

We had a power outage during the night and when I woke up, my ZHA isn’t working anymore because the “Silicon Labs Multiprotocol” addon won’t start anymore.

Log

[09:09:13] INFO: The otbr-web is disabled.
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
[09:09:13] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Apr  3 2024 12:22:03) starting
cont-init: info: /etc/cont-init.d/check-cpcd-shm.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: 2.4.5
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.2  (aarch64 / green)
 Home Assistant Core: 2025.10.1
 Home Assistant Supervisor: 2025.10.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
[09:09:18] INFO: The selected serial port is not a USB device.
[09:09:18] WARNING: No firmware found for the selected device, assuming firmware is installed.
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd-config: starting
[09:09:22] INFO: Generating cpcd configuration.
s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[09:09:23] INFO: Starting cpcd...
WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[09:09:23:471233] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4]
[09:09:23:471412] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch: 
[09:09:23:471417] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367
[09:09:23:471432] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[09:09:23:471480] Info : Reading cli arguments
[09:09:23:471492] Info : /usr/local/bin/cpcd 
[09:09:23:484715] Info : Reading configuration
[09:09:23:484740] Info :   file_path = /usr/local/etc/cpcd.conf
[09:09:23:484744] Info :   instance_name = cpcd_0
[09:09:23:484748] Info :   socket_folder = /dev/shm
[09:09:23:484750] Info :   operation_mode = MODE_NORMAL
[09:09:23:484753] Info :   use_encryption = false
[09:09:23:484756] Info :   binding_key_file = /etc/binding-key.key
[09:09:23:484759] Info :   stdout_tracing = false
[09:09:23:484761] Info :   file_tracing = false
[09:09:23:484764] Info :   lttng_tracing = false
[09:09:23:484766] Info :   enable_frame_trace = false
[09:09:23:484769] Info :   traces_folder = /dev/shm/cpcd-traces
[09:09:23:484771] Info :   bus = UART
[09:09:23:484774] Info :   uart_baudrate = 115200
[09:09:23:484777] Info :   uart_hardflow = true
[09:09:23:484779] Info :   uart_file = /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_82993388cf96ed118d6ebc98a7669f5d-if00-port0
[09:09:23:484783] Info :   fu_recovery_pins_enabled = false
[09:09:23:484786] Info :   fu_connect_to_bootloader = false
[09:09:23:484788] Info :   fu_enter_bootloader = false
[09:09:23:484791] Info :   restart_cpcd = false
[09:09:23:484794] Info :   application_version_validation = false
[09:09:23:484797] Info :   print_secondary_versions_and_exit = false
[09:09:23:484799] Info :   use_noop_keep_alive = false
[09:09:23:484801] Info :   reset_sequence = true
[09:09:23:484804] Info :   stats_interval = 0
[09:09:23:484807] Info :   rlimit_nofile = 2000
[09:09:23:484809] Info : ENCRYPTION IS DISABLED 
[09:09:23:484812] Info : Starting daemon in normal mode
[09:09:23:503631] Info : Connecting to Secondary...
[09:09:25:503907] Info : Failed to connect, secondary seems unresponsive

Last two lines repeated endlessly.

I have a Home Assistant Green with a Home Assistant SkyConnect from feb 2024.

  • Installation method: Home Assistant OS
  • Core: 2025.10.1
  • Supervisor: 2025.10.0
  • Operating System: 16.2
  • Frontend: 20251001.0

Silicon Labs Multiprotocol v2.4.5

I have tried powering off and moving the SkyConnect to another USB-port+cable. Without any luck.

I hope some of you have a suggestion, what I can do here?

I tried switching device in ZHA and got this:


Your device is running the wrong firmware and cannot be used with ZHA until the correct firmware is installed. A repair has been created with more information and instructions for how to fix this.
##

Zigbee adapter with multiprotocol firmware detected

Error · Reported by Zigbee Home Automation

Your Zigbee adapter was previously used with multiprotocol (Zigbee and Thread) and still has multiprotocol firmware installed: (CPC).

To run your adapter exclusively with ZHA, you need to install Zigbee firmware. Follow your Zigbee adapter manufacturer's instructions for how to do this.

I thought I had disabled multiprotocol when it got deprecated and that it also fixed the firmware.

Well, if anyone else runs into this.

I solved it by manually updating my SkyConnect v1.0’s firmware on my Linux PC following this guide:

I needed to run via sudo, but had installed the flasher in my user’s conda environment.
I used this command:

sudo $(which universal-silabs-flasher) --device /dev/serial/by-id/usb-Nabu_Casa_SkyConnect* flash --allow-cross-flashing --firmware EmberZNet/NabuCasa_SkyConnect_EZSP_v7.1.1.0_ncp-uart-hw_115200.gbl