ZHA not working after upgrading SkyConnect to new firmware / using SiliconLabs Zigbee/OpenThread Multiprotocol Add-on

Hello you all,

I read that by installing SiliconLabs Zigbee/OpenThread Multiprotocol Add-on and upgrading my firmware I should be able to use Zigbee and Thread … so I did that. And now Zigbee is not working anymore.

ZHA finds the SkyConnect Multi-PAN in my integrations, but everytime I choose to start a new Zigbee network I get simply “Error” without any further information.

Problem is - I can’t go back to the previous firmware either, because I use HA OS in a VM (on Synology) and didn’t find a way yet, to install Universal Silicon Labs Flasher on my VM to actually be able to flash the stick.

So I’m stuck…

Does anybody have an idea what to do?

Greets
Schlichi83

1 Like

Hi @Schlichi83

I had the same issue last week and ended up having to re-flash the Skyconnect device. I’m running HA-OS.

You’ll need to enable SSH addon (with protection mode disabled) and then follow the following guide: Flash Silicon Labs radio firmware manually · NabuCasa/silabs-firmware Wiki · GitHub.

Note that on install of the universal-silabs-flasher I received a depreciation error for PIP. Once I upgraded that, I was able to install the flasher tool and flash the radio.

2 Likes

Thank you … do you mean the “Terminal & SSH Addon”? I have this installed already. However, I can not install anything in the terminal window. And where do you disable protection mode?

Hi @Schlichi83

You’ll need to install & Configure the SSH & Web terminal addon, launch an SSH Session and then perform the above guide for the universal-silabs-flasher.

→ See the screenshot for the protection mode switch.

→ Note that after you have flashed your Skyconnect successfully you should turn the protection switch off again.

THANK YOU! I did it …
I was using the wrong SSH addon. There is an official one and the community one. I used the official one, but you have to use the community one…
Now Zigbee works again. However - you also have no idea as to why the Multiprotocol Thing didn’t work, right? Do you suggest to just wait for a few weeks until there’s a newer version?

Great to hear!

There were issues identified in the December release with Skyconnect / multi-pan and it was later disabled.

The Feb release now looks to have multi-pan re-enabled but it is still experimental and may still have issues.

The experimental multi-pan feature has been enabled again. Allowing to run both Zigbee and Thread using the single radio found in both Home Assistant Yellow and Home Assistant SkyConnect.

Which firmware did you install 7.1.1.0?

I’m also experiencing problems with Zigbee devices after the 2023.2.1 upgrade. Just checked but seems multi-pan is still disabled on my HA install

I’m running 7.1.3 for my Skyconnect firmware.
Haven’t upgraded to latest HA-OS 2023.2.2 yet - will run that through my dev first :slight_smile:

Here the same problem and the suggested solution will not work.
Following the guide to 100%… i got this result:

… Probing… Gecko…
… Probing… CPC
… Probing… EZSP
Error: Failed to probe running application type

On:

Home Assistant 2023.2.5
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest

2 Likes

Same here, trying both the EmberZNet (EmberZNet/NabuCasa_SkyConnect_EZSP_v7.1.1.0_ncp-uart-hw_115200.gbl) , EmberZNetAndOpenThreadRCP firmware ( EmberZNetAndOpenThreadRCP/beta/NabuCasa_SkyConnect_EZSP_OpenThread_RCP_v4.1.3.0_ncp-uart-hw_230400.gbl),

FWIW, the “Silicon Labs Multiprotocol Zigbee and OpenThread multiprotocol add-on” dies in the similar way:

-----------------------------------------------------------
 Add-on: Silicon Labs Multiprotocol
 Zigbee and OpenThread multiprotocol add-on
-----------------------------------------------------------
 Add-on version: 1.0.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (amd64 / qemux86-64)
 Home Assistant Core: 2023.3.4
 Home Assistant Supervisor: 2023.03.1
-----------------------------------------------------------
 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
[12:06:08] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[12:06:08] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (baudrate 115200)
2023-03-14 12:06:09 homeassistant universal_silabs_flasher.flash[237] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version=<AwesomeVersion SemVer '4.2.1'>, ezsp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>)
2023-03-14 12:06:09 homeassistant universal_silabs_flasher.flasher[237] INFO Probing ApplicationType.GECKO_BOOTLOADER
2023-03-14 12:06:11 homeassistant universal_silabs_flasher.flasher[237] INFO Probing ApplicationType.CPC
2023-03-14 12:06:15 homeassistant universal_silabs_flasher.flasher[237] INFO Probing ApplicationType.EZSP
Error: Failed to probe running application type

Here’s a log with some more verbosity… doesn’t really tell me much more, but just in case it does for someone else:

➜  silabs-firmware git:(main) universal-silabs-flasher -v -v --device /dev/ttyUSB0 --baudrate 115200 --bootloader-baudrate 115200 flash --allow-cross-flashing --firmware RCPMultiPAN/beta/NabuCasa_SkyConnect_RCP_v4.2.1_rcp-uart-hw-802154_115200.gbl
2023-03-14 12:50:19 a0d7b954-ssh asyncio[2154] DEBUG Using selector: EpollSelector
2023-03-14 12:50:19 a0d7b954-ssh universal_silabs_flasher.flash[2154] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version=<AwesomeVersion SemVer '4.2.1'>, ezsp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>)
2023-03-14 12:50:19 a0d7b954-ssh universal_silabs_flasher.flasher[2154] INFO Probing ApplicationType.GECKO_BOOTLOADER
2023-03-14 12:50:19 a0d7b954-ssh universal_silabs_flasher.common[2154] DEBUG Connection made: SerialTransport(<_UnixSelectorEventLoop running=True closed=False debug=False>, <universal_silabs_flasher.gecko_bootloader.GeckoBootloaderProtocol object at 0x7f3de1cc0490>, Serial<id=0x7f3de1cc0100, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=0, xonxoff=False, rtscts=False, dsrdtr=False))
2023-03-14 12:50:19 a0d7b954-ssh universal_silabs_flasher.common[2154] DEBUG Sending data b'3'
2023-03-14 12:50:21 a0d7b954-ssh universal_silabs_flasher.flasher[2154] INFO Probing ApplicationType.CPC
2023-03-14 12:50:21 a0d7b954-ssh universal_silabs_flasher.common[2154] DEBUG Connection made: SerialTransport(<_UnixSelectorEventLoop running=True closed=False debug=False>, <universal_silabs_flasher.cpc.CPCProtocol object at 0x7f3de1cc0580>, Serial<id=0x7f3de1cc0550, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=0, xonxoff=False, rtscts=False, dsrdtr=False))
2023-03-14 12:50:21 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-03-14 12:50:21 a0d7b954-ssh universal_silabs_flasher.common[2154] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-03-14 12:50:22 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 1 of 4)
2023-03-14 12:50:22 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-03-14 12:50:22 a0d7b954-ssh universal_silabs_flasher.common[2154] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-03-14 12:50:23 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 2 of 4)
2023-03-14 12:50:24 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-03-14 12:50:24 a0d7b954-ssh universal_silabs_flasher.common[2154] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-03-14 12:50:25 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 3 of 4)
2023-03-14 12:50:25 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-03-14 12:50:25 a0d7b954-ssh universal_silabs_flasher.common[2154] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-03-14 12:50:26 a0d7b954-ssh universal_silabs_flasher.cpc[2154] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 4 of 4)
2023-03-14 12:50:26 a0d7b954-ssh universal_silabs_flasher.flasher[2154] INFO Probing ApplicationType.EZSP
2023-03-14 12:50:26 a0d7b954-ssh bellows.ezsp[2154] DEBUG Resetting EZSP
2023-03-14 12:50:26 a0d7b954-ssh bellows.uart[2154] DEBUG Resetting ASH
2023-03-14 12:50:26 a0d7b954-ssh bellows.uart[2154] DEBUG Sending: b'1ac038bc7e'
2023-03-14 12:50:31 a0d7b954-ssh bellows.uart[2154] DEBUG Connection lost: None
2023-03-14 12:50:31 a0d7b954-ssh bellows.uart[2154] DEBUG Closed serial connection
Error: Failed to probe running application type

I don’t know if this will help, but a couple of users had success when they changed the baudrate. Note that they were doing a manual install trying to get back to the original EmberZNet stack but if this works you could do it for the “RCP Multipan” firmware:

In my case I think the issue was a mix of Proxmox USB forwarding (I’m running HA in a Proxmox VM with USB ports forwarded to the VM), and the initial firmware upgrade putting the SkyConnect stick in a weird state. After disconnecting the stick from a port on my VM host and then re-connecting it, I found it had already been successfully upgraded to the latest multi-protocol firmware and now could be used fine. But between the upgrade and disconnecting/reconnecting, it was in some sort of zombie state.

HTH someone!