Morteum9
commented
7 months ago I too would really love to find out how to flash the SkyConnect back to Zigbee only firmware. Thread / Matter devices failed me and I am leaning more into ZigBee now only to have the SkyConnect crash every other day or so now.
github-actions[bot]
Describe the issue you are experiencing
Trying to enable multiprotocol from the System->Hardware->Configure option results in a black box with simply Error: in it several seconds later.
Some backgroud is provided in a Silabs-flasher issue I opened here:
TL:DR; after migrating from my Conbee II to Skyconnect and having it working with Z2M, multiprotocol enabled, and my CP210N Z-wave dongle working well, I used those two addons to update the firmware. Saw the progress updates in the logs and no errors, appeared to be successful. Nothing Zigbee works anymore, apparently that is the case because of Z2M 1.3.5-01 and multiprotocol v2.4.2, but even deleting the addons and the related directories doesn't help. Even with it removed I cannot flash Zigbee or multiprotocol firmware to try to figure out what this "Error" is that the system shows. Nothing is showing in the logs.
An excerpt from the startup of the multiprotocol addon related to the firmware, which shows a different result from when I try the silabs-flasher directly:
s6-rc: info: service universal-silabs-flasher: starting [10:32:48] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa. [10:32:48] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 2024-01-07 10:32:49.435 hassio-direct.hagary.me universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version=None, ot_rcp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800) 2024-01-07 10:32:49.435 hassio-direct.hagary.me universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 10:32:51.455 hassio-direct.hagary.me universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud 2024-01-07 10:32:51.477 hassio-direct.hagary.me universal_silabs_flasher.flasher INFO Detected ApplicationType.CPC, version '4.4.0' at 460800 baudrate (bootloader baudrate None) 2024-01-07 10:32:51.478 hassio-direct.hagary.me universal_silabs_flasher.flash INFO Firmware version '4.3.1' does not match expected version '4.4.0' 2024-01-07 10:32:52.007 hassio-direct.hagary.me universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 10:32:53.038 hassio-direct.hagary.me universal_silabs_flasher.flasher INFO Detected bootloader version '2.1.1' 2024-01-07 10:32:53.039 hassio-direct.hagary.me universal_silabs_flasher.flasher INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.1.1' at 115200 baudrate (bootloader baudrate 115200) NabuCasa_SkyConnect_RCP_v4.3.1_rcp-uart-hw-802154_460800.gbl s6-rc: info: service universal-silabs-flasher successfully started s6-rc: info: service cpcd-config: starting [10:33:14] INFO: Using known baudrate of 460800 for cpcd! [10:33:14] INFO: Generating cpcd configuration. s6-rc: info: service cpcd-config successfully started s6-rc: info: service cpcd: starting [10:33:14] INFO: Starting cpcd...What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Silicon Labs Multiprotocol
What is the version of the add-on?
2.4.2
Steps to reproduce the issue
System Health information
Zigbee radio with multiprotocol firmware detected
Your Zigbee radio was previously used with multiprotocol (Zigbee and Thread) and still has multiprotocol firmware installed: (CPC). To run your radio exclusively with ZHA, you need to install Zigbee firmware. Follow your Zigbee radio manufacturer's instructions for how to do this.
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response