Closed burntoc closed 10 months ago
puddly
commented
10 months ago According the log, both flashed without any issues.
We have multiprotocol, normal Zigbee, ZHA, and Z2M mixed together here. Its a little hard to tell what exactly is running.
What happens if you disable multiprotocol, disable Z2M, flash ZigBee firmware, and start ZHA? Make sure you're running 2024.1.x, as the latest firmware only works with recent versions.
burntoc
commented
10 months ago So I followed your steps and ZHA does start successfully. Maybe this is just a Z2M and multiprotocol version thing and the firmware flashing is working but I can't tell? Here's the logs from Silabs-core when I flash 7.4:
s6-rc: info: service banner successfully started s6-rc: info: service universal-silabs-flasher: starting [11:43:18] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 115200) 2024-01-07 11:43:19 core-silabs-flasher universal_silabs_flasher.flash[150] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.0', ezsp_version='7.4.0.0', ot_rcp_version=None, fw_type=<FirmwareImageType.NCP_UART_HW: 'ncp-uart-hw'>, baudrate=115200) 2024-01-07 11:43:19 core-silabs-flasher universal_silabs_flasher.flasher[150] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 11:43:21 core-silabs-flasher universal_silabs_flasher.flasher[150] INFO Probing ApplicationType.EZSP at 115200 baud 2024-01-07 11:43:26 core-silabs-flasher universal_silabs_flasher.flasher[150] INFO Probing ApplicationType.CPC at 460800 baud 2024-01-07 11:43:26 core-silabs-flasher universal_silabs_flasher.flasher[150] INFO Detected ApplicationType.CPC, version '4.4.0' at 460800 baudrate (bootloader baudrate None) 2024-01-07 11:43:26 core-silabs-flasher universal_silabs_flasher.cpc[150] WARNING Failed to parse buffer bytearray(b'\x00'): ValueError('Invalid flag') 2024-01-07 11:43:26 core-silabs-flasher universal_silabs_flasher.cpc[150] WARNING Failed to parse buffer bytearray(b'\x80'): ValueError('Invalid flag') 2024-01-07 11:43:26 core-silabs-flasher universal_silabs_flasher.cpc[150] WARNING Failed to parse buffer bytearray(b'\x00'): ValueError('Invalid flag') 2024-01-07 11:43:27 core-silabs-flasher universal_silabs_flasher.flasher[150] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 11:43:27 core-silabs-flasher universal_silabs_flasher.flasher[150] INFO Detected bootloader version '2.1.1' 2024-01-07 11:43:27 core-silabs-flasher universal_silabs_flasher.flasher[150] INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.1.1' at 115200 baudrate (bootloader baudrate 115200) firmware.gbl [11:44:05] INFO: universal-silabs-flasher-up script exited with code 0 s6-rc: info: service universal-silabs-flasher successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service universal-silabs-flasher: stopping s6-rc: info: service universal-silabs-flasher successfully stopped s6-rc: info: service banner: stopping s6-rc: info: service banner successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped`
When I flashed before, I could refresh repeatedly and see the progress percent increase. I believe it also gave a success message IIRC. All I get how when I run it is a long pause after the GECKO_BOOTLOADER line and then the "INFO: universal-silabs-flasher-up script exited with code 0". I guess since that is an INFO message and not an ERROR it indicates the flash was successful? Just hard for me to reconcile as well considering I'd done this and ZHA was still reporting a multiprotocol firmware anyway. At least I'm beyond that at the moment.
burntoc
commented
10 months ago UPDATE - added ZHA and it's showing that 7.3.2 is installed as of my latest attempt,
burntoc
commented
10 months ago UPDATE - added ZHA and it's showing that 7.3.2 is installed as of my latest attempt, so I guess the flash is working. That doesn't explain the inconsistent messages and Error popups, but closing for now as there are other open issues that speak more directly to those I think.
Describe the issue you are experiencing
Had my Skyconnect briefly working with Z2M and the multiprotocol firmware. Used silabs-flasher in Hassio to update the firmware successfully. Now the addons fail, apparently something related to Gecko 4.4 or other issues between versions after Z2M 1.34 and Multiprotocol addon 2.3.2.
Trying to flash back to any firmware, multiprotoc l or otherwise presents an error - regardless of baudrate settings. Trying Zigbee firmware results in: ` Add-on: Silicon Labs Flasher Silicon Labs firmware flasher add-on
Add-on version: 0.2.0 You are running the latest version of this add-on. System: Home Assistant OS 11.3 (amd64 / qemux86-64) Home Assistant Core: 2024.1.2 Home Assistant Supervisor: 2023.12.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 [10:01:55] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa. [10:01:55] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 115200) 2024-01-07 10:01:56 core-silabs-flasher universal_silabs_flasher.flash[151] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version='7.3.1.0', ot_rcp_version=None, fw_type=<FirmwareImageType.NCP_UART_HW: 'ncp-uart-hw'>, baudrate=115200) 2024-01-07 10:01:56 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 10:01:58 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.EZSP at 115200 baud 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.CPC at 460800 baud 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected ApplicationType.CPC, version '4.3.1' at 460800 baudrate (bootloader baudrate None) 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.cpc[151] WARNING Failed to parse buffer bytearray(b'\x00'): ValueError('Invalid flag') 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.cpc[151] WARNING Failed to parse buffer bytearray(b'\x80'): ValueError('Invalid flag') 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.cpc[151] WARNING Failed to parse buffer bytearray(b'\x00'): ValueError('Invalid flag') 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected bootloader version '2.1.1' 2024-01-07 10:02:03 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.1.1' at 115200 baudrate (bootloader baudrate 115200) NabuCasa_SkyConnect_EZSP_v7.3.1.0_ncp-uart-hw_115200.gbl [10:02:41] INFO: universal-silabs-flasher-up script exited with code 0 s6-rc: info: service universal-silabs-flasher successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service universal-silabs-flasher: stopping s6-rc: info: service universal-silabs-flasher successfully stopped s6-rc: info: service banner: stopping s6-rc: info: service banner successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped`
Removed all my other addons beforehand so as to ensure no conflict. Rebooted the server several times. If I try to flash the multiprotocol firmware, similar result: ` Add-on version: 0.2.0 You are running the latest version of this add-on. System: Home Assistant OS 11.3 (amd64 / qemux86-64) Home Assistant Core: 2024.1.2 Home Assistant Supervisor: 2023.12.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 [10:06:26] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0 (bootloader baudrate 115200) 2024-01-07 10:06:26 core-silabs-flasher universal_silabs_flasher.flash[151] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.0', ezsp_version=None, ot_rcp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800) 2024-01-07 10:06:26 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 10:06:28 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.CPC at 460800 baud 2024-01-07 10:06:33 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.CPC at 115200 baud 2024-01-07 10:06:37 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.CPC at 230400 baud 2024-01-07 10:06:41 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.EZSP at 115200 baud 2024-01-07 10:06:43 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected ApplicationType.EZSP, version '7.3.1.0 build 176' (7.3.1.0.176) at 115200 baudrate (bootloader baudrate None) 2024-01-07 10:06:44 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud 2024-01-07 10:06:44 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected bootloader version '2.1.1' 2024-01-07 10:06:44 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.1.1' at 115200 baudrate (bootloader baudrate 115200) firmware.gbl [10:07:04] INFO: universal-silabs-flasher-up script exited with code 0 s6-rc: info: service universal-silabs-flasher successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service universal-silabs-flasher: stopping s6-rc: info: service universal-silabs-flasher successfully stopped s6-rc: info: service banner: stopping s6-rc: info: service banner successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped`
I even tried going to ZHA to see if that helped and it says my system is running a multiprotocol firmware. Could really use some help - starting to hate my decision to buy and update this SkyConnect.
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 Flasher
What is the version of the add-on?
.0.2.0
Steps to reproduce the issue
1.Receive errors trying to start Z2M or ZHA addons. 2.Attempt to flash https://github.com/NabuCasa/silabs-firmware/raw/main/RCPMultiPAN/beta/NabuCasa_SkyConnect_RCP_v4.4.0_rcp-uart-hw-802154_460800.gbl or https://github.com/NabuCasa/silabs-firmware/raw/main/EmberZNet/beta/NabuCasa_SkyConnect_EZSP_v7.4.0.0_ncp-uart-hw_115200.gbl
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