Bootloader upgrade to 02.04.0005 fails with CRC error

[GregN]

Hi,

I have a RaZberry 7 Pro:

Code: Select all

Hardware
Vendor:	RaZberry by Z-Wave.Me
Vendors Product ID:	1025 / 257
Z-Wave Chip:	ZW0700
Firmware
Library Type:	Static Controller
SDK Version:	7.21.00
Serial API Version:	07.42

The current firmware version is: 7.42 [Bootloader: 1766938484] and I am using Z-Way 4.1.4.

In the Z-Way firmware update page for the controller I am offered an upgrade to bootloader 02.04.0005 (dated 2024-07-15). However, the upgrade fails with a CRC error as shown in the log file:

Code: Select all

[2025-05-30 14:58:29.399] [I] [zway] Adding job: Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip
[2025-05-30 14:58:29.406] [D] [zway] SENDING (cb 0x83): ( 01 04 00 F4 83 8C )
[2025-05-30 14:58:29.409] [D] [zway] RECEIVED ACK
[2025-05-30 14:58:29.410] [D] [zway] RECEIVED: ( 01 04 01 F4 01 0F )
[2025-05-30 14:58:29.410] [D] [zway] SENT ACK
[2025-05-30 14:58:29.410] [I] [zway] Job 0xf4 (Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip): Wrong checksum
[2025-05-30 14:58:29.410] [D] [zway] Job 0xf4 (Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip): fail
[2025-05-30 14:58:29.410] [I] [zway] Removing job: Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip

It has been like this for a while now.

I'm slightly confused as I thought that this would be a 7th generation Z-Wave chip, but perhaps "5th generation" isn't referring to the Z-Wave side of things?

Can the file be fixed or does someone have a correct version of the bootloader file (bootloader_ZGM13_RAZ_02040005.bin) that I can use?

Thanks,

Greg

[seattleneil]

Your system is on the most recent bootloader, firmware and Z-Way version. It sounds like there's a problem with the Z-Way firmware update page offering you an invalid upgrade. Ignore the upgrade offer.

[GregN]

Hi seattleneil,

Thanks for your reply and sorry for not responding sooner but for some reason I wasn't notified of your reply.

You may well be right, but https://service.z-wave.me/expertui/uzb- ... ith_hidden does show a version 7.46 with my current (and other versions of the) bootloader. So I'm also not sure why it doesn't just offer the upgrade using my current bootloader, but I do find that service page very confusing.

Greg.

[piet66]

It's right, the bootloader update is offered for Razberry 7 with different version number 17367041>33816581, also without token 'all':
https://service.z-wave.me/expertui/uzb/ ... n=17367041

Code: Select all

{

      "data": [
            {
                  "id": "1193",
                  "baseid": "",
                  "enabled": "enabled",
                  "type": "bootloader",
                  "file": "bin",
                  "vendorID": "327",
                  "org_family": "745516882",
                  "fw_family": "0",
                  "chip_family": "0",
                  "chip_id": "2",
                  "bootloaderCRC": null,
                  "bootloaderVersion": null,
                  "appVersionMajor": "7",
                  "appVersionMinor": "42",
                  "target_fw_family": "0",
                  "targetBootloaderCRC": null,
                  "targetBootloaderVersion": "33816581",
                  "targetAppVersionMajor": null,
                  "targetAppVersionMinor": null,
                  "fileURL": "bootloader_ZGM13_RAZ_02040005.bin",
                  "released": "2024-07-15",
                  "comment": "Bootloader upgrade to 02.04.0005",
                  "position": "0",
                  "version": "7.42"
            }
      ]

}

Can't see if there's anything wrong.
@seattleneil: Where do you know, that the current bootloader is up-to-date?

[seattleneil]

@seattleneil: Where do you know, that the current bootloader is up-to-date?

The response to remain at 7.42 was to avoid breaking something that's working. Yes, the version graph at the following link shows a newer bootloader and firmware version are available.

Code: Select all

https://service.z-wave.me/expertui/uzb-stats/versions-graph.html?hw=327 

However, @PoltoS has not made an announcement and given the z-way-server.log file provided by the OP, it looks like more testing is needed. It would be great if someone was willing to install the new bootloader and firmware and share the results. You can see the new bootloader and firmware info using the following query:

Code: Select all

https://service.z-wave.me/expertui/uzb/?vendorId=327&appVersionMajor=7&appVersionMinor=42&bootloaderCRC=1712486286&zway=v4.1.4&uuid=3ee2ae665472c308303362202350403c'

Code: Select all

{
  "data": [
    {
      "id": "1193",
      "baseid": "",
      "enabled": "enabled",
      "type": "bootloader",
      "file": "bin",
      "vendorID": "327",
      "org_family": "745516882",
      "fw_family": "0",
      "chip_family": "0",
      "chip_id": "2",
      "bootloaderCRC": null,
      "bootloaderVersion": null,
      "appVersionMajor": "7",
      "appVersionMinor": "42",
      "target_fw_family": "0",
      "targetBootloaderCRC": null,
      "targetBootloaderVersion": "33816581",
      "targetAppVersionMajor": null,
      "targetAppVersionMinor": null,
      "fileURL": "bootloader_ZGM13_RAZ_02040005.bin",
      "released": "2024-07-15",
      "comment": "Bootloader upgrade to 02.04.0005",
      "position": "0",
      "version": "7.42"
    },
    {
      "id": "1185",
      "baseid": "",
      "enabled": "enabled",
      "type": "firmware",
      "file": "bin",
      "vendorID": "327",
      "org_family": "745516882",
      "fw_family": "0",
      "chip_family": "0",
      "chip_id": "2",
      "bootloaderCRC": "1712486286",
      "bootloaderVersion": "33816581",
      "appVersionMajor": "7",
      "appVersionMinor": "42",
      "target_fw_family": "0",
      "targetBootloaderCRC": null,
      "targetBootloaderVersion": null,
      "targetAppVersionMajor": "7",
      "targetAppVersionMinor": "46",
      "fileURL": "Razberry07.21.03.12.gbl",
      "released": "2024-07-25",
      "comment": "Update firmware from 7.42 to 7.46 (SDK 7.21.3)",
      "position": "53",
      "version": "7.42"
    }
  ]
}

My concern is that Z-Wave.Me hardware is no longer under active development and if an unannounced/unofficial bootloader and firmware upgrade bricks the controller, recovery may not be possible. Support is gone. Why take the risk? Keep in mind, even if upgrading to SDK 7.21.3 is successful, recognize Silicon Labs continues to release new SDK versions of the 700-series hardware and is currently up to version 7.21.6, with release notes at the following link:

Code: Select all

https://www.silabs.com/documents/public/release-notes/SRN14930-7.21.6.0.pdf

My personal perspective is to climb the Home Assistant learning curve with Zooz 800-series controllers. What are your thoughts?

[piet66]

You're right, you should always consider what risk you're taking. I only upgrade myself if I have a special reason to do so. And wait until others have successfully installed the upgrade.

On the other hand, this upgrade is offered in ExpertUi, and therefore officially. In such a case, you should report the issue in the hope that it will be fixed after all. Other users should not run into this problem as well.
The warning ‘You should only perform an upgrade if asked by support.’ is often overlooked.

My personal perspective is to climb the Home Assistant learning curve with Zooz 800-series controllers. What are your thoughts?

This is probably a good suggestion.
My problem, unfortunately, is that I don't know Home Assistant or what the Zooz 800-series controllers are. And the Silabs documentation is very unclear for me.
I also don't have time to familiarize myself. It would be great if anyone could find a helpful guide on how to proceed specifically. Many users will certainly be in the same situation.

[seattleneil]

My reply is off the original topic of bootloader issues, but may be helpful...

My problem, unfortunately, is that I don't know Home Assistant or what the Zooz 800-series controllers are. And the Silabs documentation is very unclear for me.
I also don't have time to familiarize myself. It would be great if anyone could find a helpful guide on how to proceed specifically. Many users will certainly be in the same situation.

Z-Wave.Me has kindly provided 2 years for users to figure out what to do. After 2 years, there's no commitment that Z-Way's cloud-dependent services will be available. Who knows, perhaps Trident IoT will keep continue to operate the cloud services or some other entity will support the cloud services. Note that users who don't rely on remote access, cloud backups or apps such as Amazon Alexa or Google Home, the impact of Z-Wave.Me shutting down Z-Way's cloud services may not get noticed.

For users that will be impacted, the first decision is whether a new hardware controller will be installed or if the existing Z-Wave.Me hardware will continue to be used. For the first case, the likely path is to "start over", with new hardware and a new home automation solution that supports Z-Wave such as Home Assistant. There are other perfectly good home automation solutions such as Domoticz. This path requires all Z-Wave devices to be excluded and then re-included with a new network ID and security keys. The other case (continuing to use Z-Wave.Me hardware), has 2 branches. You can continue to use Z-Way as a Home Assistant integration, or you can switch to Z-Wave JS UI. Switching to Z-Wave JS UI should not require excluding/re-including non-S2 security devices (i.e., a complete "start over"), but it will require re-interviewing all of the devices, so it's more complicated than using Z-Way as a Home Assistant integration. I don't think there's a right answer or a wrong answer - there are pros and cons to the various options.

One factor for continuing with Z-Way is that works on a Raspberry Pi 2 or 3 whereas other solutions such as Home Assistant have higher hardware requirements (Raspberry Pi 4 with 2GB of RAM or better).

As for a new hardware controller, there are multiple vendors. I'm familiar and happy with Zooz hardware which can be purchased here: https://www.thesmartesthouse.com/collec ... ontrollers

Please don't be concerned about understanding Silabs documentation - end users are not the intended audience. The main takeaway is that Silabs continues to release new versions of their SDK to fix bugs and add new features. Since Z-Wave.Me development has stopped, the firmware on their hardware has fallen behind the most recent Silabs SDK. Strictly speaking, Z-Wave.Me hardware has also fallen behind since it's based on 700-series chips which is end-of-life with the release of 800-series chips. Of course, if you're not encountering any firmware or hardware issues, then chasing the latest and greatest SDK version or chip has no meaningful benefit.

Regarding Home Assistant - it can be approached at multiple levels of technical proficiency. See: https://www.home-assistant.io/installation/
Regardless of how you install Home Assistant, there's definitely a learning curve. Fortunately, everything that I do Z-Way can be done with Home Assistant - it's a matter of having the time and interest in learning a new home automation environment.