#Silicon Labs Multiprotocol - No firmware found for the selected device, assuming firmware is install

1 messages · Page 1 of 1 (latest)

hallow lotus
#

Device: Sky Connect, purchased January 2025. Model HASKYCONCT FCC ID 2A8ZEO1)

Setup: Using the multiprotocol firmware for both zigbee and thread.

Problem: Everything was working flawlessly for the past 6 months. This morning, all ZigBee and Thread devices stopped working. I have not made any recent changes to Home Assistant, networking or the Unraid server that hosts Home Assistant. Concerted my Sky Connect went bad. If not that, I am at a loss for how to fix this.

Troubleshooting: I restored home assistant to a backup from 1 week ago just to be sure there were no updates I forgot about. Shutdown Home Assistant. Shutdown unraid server. Start unraid server. Start Home Assistant VM. Check Devices and Services for errors, found ZHA and OTBR services failed setup. Check addons an Silicon Labs Multiprotocol is erroring. I have attached a log, but the lines that stick out to me are below. Attempted multiple reboot sequences and restarting addons, all producing the same error.

[11:33:00] INFO: The selected serial port is not a USB device.
[11:33:00] WARNING: No firmware found for the selected device, assuming firmware is installed.

[11:33:09:331605] Info : Failed to connect, secondary seems unresponsive
[11:33:09:331608] Info : Connecting to Secondary...
[11:33:09:331639] Core : txd transmit completed
[11:33:09:331641] Core : Endpoint #0: frame transmit submitted
[11:33:09:331642] System : Submitted command_id #3 command_seq #4
[11:33:09:331658] System : property-set (id #3) sent with property #514
[11:33:09:331659] Reset Sequence : Reboot mode sent
[11:33:09:331741] Driver : 21 bytes left in the UART char driver

📎 error_log
golden chasm
hallow lotus
#

Were you able to get multiprotocol working again or did you have to choose between Thread and Zigbee? I was hoping to just be able to continue using the unsupported multiprotocol option as it has been working great for me.

golden chasm
#

No was not. I have ditched multiprotocol as it seems it will now ultimately fail in latest update sooner or later.
Multiprotocol was also working great for me until now, but I did not have Matter-over-Thread Devices until recently (Tado Thermostat X) but the described solution worked exactly like stated. I am now planning to get a seperate Thread Border Router

hallow lotus
#

I ended up choosing to use Thread on the SkyConnect. Pretty easy process to switch over. Although, I was unable to use the companion app on my Android to re-pair a devices. Fortunately I still had an old iPhone laying around and successfully paired with that.