Help wanted - need to downgrade Z2M to 1.34 and SiLabs Multiprotocol to 2.3.2 - no backups

I stupidly deleted my backups thinking everything was working in my system, as I’d finally gotten my Z-wave dongle, Skyconnect, Z2M and multiprotocol working - then I stupidly decided to update the firmware on the Skyconnect and there have been some recentl updates to both addons so I’m getting tripped up.

Is there a repository and method availble to access and restore older versions in a case like this? I presume I could duplicate my backup and replace versions in the clone with the needed versions if I could get them, then do a partial restore (I don’t mind recreating my 5-6 Zigbee devices).

No there is no method that I know of to do this.

You should implement one of the methods listed in option 5 here to automate copying backups off your system so you can

a) keep them longer
b) use them in case of HA file system corruption.

Samba Backup is great if you have a NAS.

You’re absolutely right. I started on it yesterday and completed it this morning. Unfortunately a day late and a dollar short, as they say.

Can you downgrade the Skyconnect firmware?

https://www.home-assistant.io/blog/2023/02/08/state-of-matter-and-thread/#silabs-multi-flasher--sl-web-tools

I tried going back to 7.3.2 and it failed, though it worked fine to update me to 7.4 earlier so I guess maybe something won’t allow it. That said I tried to reflash 7.4 and it wouldn’t allow that either.

I re-read your message from earlier and realized I do have the Google Drive backup addon. It had a backup with the 2.3.2 multiprotocol addon, but unfortunately Z2M was still 1.3.5-01 and I’m still getting errors. Going to post the log as an issue on Github I guess.

s6-rc: info: service s6rc-oneshot-runner: starting
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
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service banner: starting

-----------------------------------------------------------
 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
[20:15:24] INFO: Starting universal-silabs-flasher with /dev/ttyUSB1 (bootloader baudrate 115200)
2024-01-06 20:15:26 core-silabs-flasher universal_silabs_flasher.flash[151] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.2', ezsp_version='7.3.2.0', ot_rcp_version=None, fw_type=<FirmwareImageType.NCP_UART_HW: 'ncp-uart-hw'>, baudrate=115200)
2024-01-06 20:15:26 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-01-06 20:15:28 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.EZSP at 115200 baud
2024-01-06 20:15:29 core-silabs-flasher bellows.ezsp[151] WARNING Protocol version 13 is not supported, using version 12 instead
2024-01-06 20:15:29 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected ApplicationType.EZSP, version '7.4.0.0 build 0' (7.4.0.0.0) at 115200 baudrate (bootloader baudrate None)
2024-01-06 20:15:30 core-silabs-flasher bellows.ezsp[151] WARNING Protocol version 13 is not supported, using version 12 instead
2024-01-06 20:15:30 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-01-06 20:15:30 core-silabs-flasher universal_silabs_flasher.flasher[151] INFO Detected bootloader version '2.1.1'
2024-01-06 20:15:30 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
[20:16:08] 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 stoppedtype or paste code here
1 Like