-
Notifications
You must be signed in to change notification settings - Fork 10
700 series Controller Firmware Updates (Linux)
This guide describes how to perform Over-The-Wire (OTW) firmware upgrades for Z-Wave 700-series (or later) controllers in a Linux environment, using freely available tools.
If using command line tools does not appeal to you, stop now and follow your vendor's official instructions, or contact them directly for support. See Disclaimer.
Other options:
- Temporarily relocate your USB controller to a Windows PC and use the Silicon Labs PC Controller software
-
zw_programmer: The Z/IP Gateway software includes this CLI utility to program the controller firmware. This requires obtaining access to the Z/IP Gateway SDK download and the ability to compile it, which will be difficult for most. -
zpc: Thezpcservice provided by the Silicon Labs Unify SDK has the ability to program the controller firmware. This requires obtaining access to a private GitHub project and the ability to compile it, which will be difficult for most.
The following hardware and software were used in the creation of this guide:
- Platform: Raspberry Pi4
- OS: Raspberry Pi OS 64-bit (Debian 10)
- Silicon Labs UZB7 USB controller (SLUSB001A)
- minicom version 2.7.1
- lrzsz version 0.12.21
Other Unix-like OS may work with this guide if they support USB serial devices, minicom, and lrzsz.
Confirmed to work with:
- Raspberry Pi4 and Ubuntu 20.04 64-bit [*]
- Raspberry Pi2 Model B and Raspberry Pi OS 32-bit
- Synology NAS with a Debian 10.9 Docker container [*]
Confirmed not working:
- Apple Silicon and MacOS, using homebrew installed lrzsz and minicom. Update seems to have no effect [*].
The latest certified release is 7.18.1.
Most controllers use stock firmware images distributed by Silicon Labs via the Z-Wave SDKs. Some vendors also distribute their own files, but usually these are identical to the Silicon Labs versions. Links to both files are provided when available. If in doubt, choose the vendor's file.
Select your product to continue:
- Aeotec Z-Stick 7 or Z-Pi 7
- Everspring SA370
- HomeSeer SmartStick+ G3
- Silicon Labs UZB-7
- Z-Wave.Me RaZberry 7
- Zooz ZST10 700
For other download options, see alternative downloads.
Missing a product? Let us know by submitting an issue.
The Z-Stick 7 and Z-Pi 7 controllers are a BRD4206A radio board (EFR32ZG14 chipset).
See Update Z-Stick 7 with Windows or Update Z-Stick 7 with Raspian OS / RPi for the official Aeotec update instructions.
MD5 checksum: abbc9a40ab1eaaef0b3cc4fa1daed366
The Zooz Everspring SA370 controller is the ZGM130S module but the radio board is currently unknown. It may be a BRD4202A or BRD4207A. Use those files at your own risk.
There are no official update instructions or downloads.
This section will be updated when the correct firmware files are known, and/or Everspring produces official instructions and downloads.
Refer to the 7.17.2 instructions otherwise.
The SmartStick+ G3 controller is a BRD4202A radio board (ZGM130S module).
See Updating SmartStick+ Firmware for the official HomeSeer update instructions.
The SmartStick+ G3 controller does not yet officially support the 7.18 firmware, but testing is in progress. Refer to this forum post for details. This section will be updated once the upgrade is out of testing.
Refer to the 7.17.2 instructions otherwise.
The UZB-7 controller is a BRD4206A radio board (EFR32ZG14 chipset).
See Z-Wave 700: OTW of Controller or Z-Wave 700: Programming UZB7 Controller Stick for official Silicon Labs update instructions.
- Download from Silicon Labs
MD5 checksum: abbc9a40ab1eaaef0b3cc4fa1daed366
The Zooz ZST10 700 controller is the ZGM130S module but the radio board is currently unknown. It may be a BRD4202A or BRD4207A. Use those files at your own risk.
See How to Perform an OTA Firmware Update on Your ZST10 700 Z-Wave Stick for the official Zooz update instructions.
This section will be updated when the correct firmware files are known, and/or Zooz produces updated instructions and downloads.
Refer to the 7.17.2 instructions otherwise.
If you know your device's radio board identifier you can download the file directory from Silicon Labs files on GitHub, from the gbl directory.
With the 7.18 SDK, firmware files are no longer designated by chipset or module identifiers. Instead, the files are specific to radio boards. There are a variety of chipsets and radio boards a manufacturer can choose from. Verify with the vendor which radio board and firmware file is correct for your controller.
Download the demo-applications.zip archive to download all firmware files at once.
All commands listed here are being executed as the root user, to avoid any problems with permissions.
-
Install minicom and file transfer utilities.
apt install -y minicom lrzsz
-
Determine the path to the Z-Wave controller's serial device. For a UZB7 and other 700-series USB controllers, this will typically be
/dev/ttyUSB0. -
Set an environment variable for the USB path. This is used in commands below for easy copy and paste.
export USBPATH=/dev/ttyUSB0 -
Create a minicom profile named
zwavethat configures the serial port for FW upload. This configures the following settings:- Set serial port speed.
- Disable hardware flow control.
- Hide all file transfer choices except xmodem upload.
cat << EOF > /etc/minicom/minirc.zwave # Machine-generated file - use "minicom -s" to change parameters. pu pname1 YUNYY pu pname2 YUNYY pu pname4 NDNYY pu pname5 NDNYY pu pname6 YDNYN pu pname7 YUYNN pu pname8 NDYNN pu pname9 YUNYN pu updir /tmp pu port $USBPATH pu baudrate 115200 pu bits 8 pu parity N pu stopbits 1 pu rtscts No EOF
This is a one time setting and isn't necessary for future upgrades. The profile settings are stored in
/etc/minicom/minirc.zwave. -
Download or copy the controller firmware file to
/tmp. -
Stop zwavejs2mqtt or other zwave-js application so it doesn't interfere. Some users have reported that this step isn't necessary.
All commands listed here are being executed as the root user, to avoid any problems with permissions.
-
Configure the serial port speed. minicom would normally do this, but we issue a couple commands from the shell.
stty 115200 cs8 -cstopb -F $USBPATH -
Soft-reset the controller and wait long enough for it to recover.
printf '\x01\x03\x00\x08\xf4' > $USBPATH && sleep 10
-
Drop the controller into the bootloader.
printf '\x01\x03\x00\x27\xDB' > $USBPATH && sleep 1
-
Start minicom to connect to the device console. Be sure to use the profile configured previously.
minicom -o zwave
-
Press ENTER (one or more times) and you'll see the bootloader prompt. Enter
1to upload the firmware. The letterCwill be printed repeatedly to indicate that the controller is waiting for an upload.Gecko Bootloader v1.5.1 1. upload gbl 2. run 3. ebl info BL > begin upload CCCC -
Enter
CTRL-A sto open the file upload dialog.xmodemwill be the only option, so select it. Navigate the menu so the firmware file is highlighted and select it with Spacebar, then press Enter to upload. -
When the upload finishes, select option
2in the bootloader menu to run the new firmware. Some garbage characters will appear, meaning the firmware is running. Exit minicom withCTRL-A qand selectYesto exit. -
Start zwavejs2mqtt or other zwave-js application. If for some reason you have soft-reset disabled in zwave-js (not recommended), be sure to issue a soft-reset prior to starting the application. Confirm the controller firmware has changed to the expected version.