-
|
See in #1357 that support to configure RF region and TX power level for Silabs Z-Wave 700 Controller hardware has been added in #2500 This should mean that Silicon Labs UZB-7 USB Stick (SLUSB001A / SLUSB7000A) is the least expensive Z-Wave 700 Controller for Z-Wave JS. https://www.silabs.com/documents/public/user-guides/ug516-uzb-7-users-guide.pdf This SLUSB001A / SLUSB7000A is Silabs official Z-Wave 700 Controller reference hardware which can be found worldwide for less than $20. https://www.google.com/search?q=SLUSB001A As I understand it, other than not shipping pre-flashed with the firmware image you will need for Z-Wave JS out-of-the-box (making it a little less user-firendly), the main downside compared to other dongles is a global variant that does not have an RF region-optimized antenna. Other than that the only other downsides I noticed so far is no external antenna and its USB-to-UART chip EEPROM does not come preprogrammed with a unique USB "Product Description ID" and as such application can not use USB discovery to automatically detect this specific product. See:
Any tips on which firmware version is recommended for this "Silicon Labs Z-Wave 700 UZB-7 USB Stick" for use with zwave-js? https://www.silabs.com/documents/public/data-sheets/DSH14483.pdf https://www.silabs.com/documents/public/schematic-files/PHD14501.zip https://fccid.io/2ADB9-UZB-7/External-Photos/External-Photos-4144374.pdf https://fccid.io/2ADB9-UZB-7/Internal-Photos/Internal-Photos-4144376.pdf https://fccid.io/2ADB9-UZB-7/Label/ID-Label-Location-Info-4144377.pdf Does one have to download and install Silabs Simplicity Studio to upgrade Silcon Labs UZB7 SLUSB001A / SLUSB7000A dongle? By the way, note the comment for upgrading OTW firmware via Silabs Simplicity Studio: "Also be aware that for Z-Wave 700 series OTW/OTA, the firmware .gbl file must have a newer version number than that the device being upgraded is running, that is, you will need to select a SerialAPI controller firmware .gbl file from a newer SDK release when performing OTW." Or is it best to just upgrade GPL firmware files via the mentioned Silicon Labs "Z-Wave PC Controller" application in Simplicity Studio.? https://www.silabs.com/wireless/z-wave#software Or should one just upgrade firmware via bootloader boot mode XMODEM binary transfers using any Terminal program (like ex. Tera Term)? https://community.silabs.com/s/article/z-wave-700-programming-uzb7-controller-stick?language=en_US This Z-Wave 700 stick is based on EFR32ZG14 Zen Gecko Z-Wave + CP2102N-A02-GQFN28 so requires CP210x USB to UART Bridge VCP Drivers. https://www.silabs.com/documents/public/schematic-files/PHD14501.zip https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers Silabs community says that this UZB7 stick is backwards compatible with UZB3 for Z-Wave 500 / Z-Wave Plus but looking to buy it now for it to be forward compatible and looking forward to the day to use it in Z-Wave 700 mode to test Z-Wave Gen7 devices. This same dongle is the official Z-Wave 700 reference design from Silicon Labs Z-Wave 700 Wireless Starter Kit (SLWSTK6050A): https://www.silabs.com/development-tools/wireless/z-wave/z-wave-700-starter-kit https://www.silabs.com/development-tools/wireless/z-wave/z-wave-long-range-700-starter-kit Surprisingly the SLUSB001A / SLUSB7000A UZB-7 looks like the most affordable Z-Wave 700 USB adapters readily available today: https://www.google.com/search?q=SLUSB001A
|
Beta Was this translation helpful? Give feedback.
Replies: 41 comments 224 replies
-
Probably the latest one. Early versions had some problems with network healing.
I think that's one level too low. You can perform an OTW upgrade with the Silabs PC Controller application. |
Beta Was this translation helpful? Give feedback.
-
|
I feel silly for having to ask this but where do you get the firmware for the "Silicon Labs Z-Wave 700 UZB-7 USB Stick". I've downloaded and installed simplicity studio, and the zwave sdk, but still cannot figure out where the firmware is? |
Beta Was this translation helpful? Give feedback.
-
|
Hmm well I think I found it in 'SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.1\protocol\z-wave\Apps\bin\gbl' |
Beta Was this translation helpful? Give feedback.
-
Little late but for others that see this, check out bove solution post -> #2544 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Note! You first need to update firmware to a later GA (General Availability) version of firmware before using UZB-7 as a commercial product. Official firmware for zwave_ncp_serial_api_controller_BRD4206A firmware images that Silicon Labs UZB-7 (SLUSB001A) needs found here: https://github.com/SiliconLabs/gecko_sdk Link example for Silicon Labs Gecko SDK (GSDK) Version 4.1.6 (which contains Z-Wave and Z-Wave Long Range 700/800 SDK 7.18.8.0, see): https://github.com/SiliconLabs/gecko_sdk/tree/v4.1.6/protocol/z-wave/Apps/bin/gbl Note! It is important to first update to 7.18.8 first before updating to 7.20.X or later! Update: "Z-Wave Controller firmwares based on Z-Wave SDK 7.19.3 have a bug that causes the controller to randomly hang during transmission until it is restarted. It is currently unclear if this bug is fixed in a later firmware version." though Silabs have said they plan to have a fix for this lockup in 7.21.2 which is scheduled for mid April of 2024. kpine had summarized links and firmware upgrade procedure here: Tip! You can perform local firmware upgrade using OTW (Over The Wire) on UZB7 USB stick using Z-Wave 700 Serial API firmware GBL XModem file via the "OTW Firmware Upgrade" option in Silabs "Z-Wave PC Controller" tool that gets installed with Simplicity Studio. Update! AlCalzone now also added a OTW flasher to node-zwave-js -> #2545 Firmware can be upgraded using the below directions:
Quick Start-Up Guide to flash Silabs UZB-7 USB stick with the latest firmware with Silicon Labs Simplicity Studio on WindowsHere is a quick start-up guide on how to perform OTW Firmware Upgrade on UZB-7 using "Z-Wave PC Controller" tool in Simplicity Studio. Prerequisites: To actually get/download the latest firmware file for Z-Wave 700 USB stick you need to register for a free Silicon Labs Community account at https://community.silabs.com/SL_CommunitiesSelfReg and install Simplicity Studio v5 for your operating system, start it and login to install + update the Z-Wave technology type SDK package inside Simplicity Studio. See https://www.silabs.com/developers/simplicity-studio
FYI, if use default directories for Simplicity Studio + the Z-Wave technology type package GBL firmware binary files should after install be in: C:\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.2\protocol\z-wave\Apps\bin\gbl Note that this version might not be the correct or latest versions that are available online via the GitHub repository listed above. Silabs UZB-7 USB Stick uses an EFR32ZG14 SoC so you need to select the latest ZW SerialAPI Controller firmware for it and your RF region. So for example, currently, currently the latest firmware file (Version 7.16.2.0 / Version 7.16 Build 267) for the UZB7 USB sticks for Europe (RF region) is: "ZW_SerialAPI_Controller_7.16.2_267_EFR32ZG14_REGION_EU.gbl" Respectively, currently, the latest firmware file (Version 7.16.2.0 / Version 7.16 Build 267) for the UZB7 USB sticks for the United States / North America (RF region) is: "ZW_SerialAPI_Controller_7.16.2_267_EFR32ZG14_REGION_US.gbl" PS: Move information is available in INS13114 Z-Wave PC based Controller v5 User Guide from Silicon Labs: |
Beta Was this translation helpful? Give feedback.
-
|
Silabs has released a new version today of zwave sdk (7.18) however the naming schema for the gbl files has changed, it's not clear to me which file to choose (if any) to upgrade my Zooz stick. Any thoughts? https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.1/protocol/z-wave/Apps/bin/gbl |
Beta Was this translation helpful? Give feedback.
-
|
Silabs upgraded their latest release (4.1.1 -> Zwave 7.18.1) as a GA https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.1.1 It has a number of fixes/improvements. Mine has been working fine on the prior version, but, has anyone successfully upgraded their 700 series stick? |
Beta Was this translation helpful? Give feedback.
-
|
Not me. I don't typically upgrade my controller unless there are actual issues I am running into, or new features I really want. I have no need to be on the bleeding edge if everything is working on my network. |
Beta Was this translation helpful? Give feedback.
-
|
I flashed 7.18.3 and had no issues. Used file "zwave_ncp_serial_api_controller_BRD4206A.gbl". Only thing that I cannot do is set Region. It just shows "unknown". Tried setting it with PC Controller software (tool in Simplicity Studio) but it errors out and retains the "unknown". However, it is working fine here in the US. |
Beta Was this translation helpful? Give feedback.
-
Can u tell me what program u used to make your upgrade, also, your problem with region is gone? |
Beta Was this translation helpful? Give feedback.
-
FYI; blhoward2 confirmed OTW firmware upgrade bootloader + xmodem procedure in Linux on an UZB-7 stick as he posted this in #2545
|
Beta Was this translation helpful? Give feedback.
-
|
FYI, kpine in #2545 (comment)_ also posted link to his alternative guide -> https://gist.github.com/kpine/f7206cfc5625b4c2c54a8f6ceb6aa2ca OverviewThis guide describes how to upgrade the firmware for a Z-Wave 700-series controller. Equipment used:
All commands are executed as the Preparation
$ apt install -y minicom lrzsz
$ export USBPATH=/dev/ttyUSB0
$ 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
EOFThis is a one time setting and isn't necessary for future upgrades. The profile settings are stored in
Installation
$ stty 115200 cs8 -cstopb -F $USBPATH
$ printf '\x01\x03\x00\x08\xf4' > $USBPATH && sleep 10If you have other USB devices then the soft-reset might change the USB path. Adjust
$ printf '\x01\x03\x00\x27\xDB' > $USBPATH && sleep 1
$ minicom -o zwave
Gecko Bootloader v1.5.1
1. upload gbl
2. run
3. ebl info
BL >
begin upload
CCCC
$ printf '\x01\x03\x00\x08\xf4' > $USBPATH && sleep 10
|
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: I tried the instructions on a RPi 4 running Ubuntu 20.04 64bit, and it does work! I am trying this method using Ubuntu, but without luck so far. I did find the firmware here. But at step 6, it does not upload the firmware, and instead waits for awhile on |
Beta Was this translation helpful? Give feedback.
-
|
Anyone using the 7.17.0 firmware yet? Didn't see much in the changelog that made me think it was a "must have", but thought I would ask. Looked like mostly zwave 800 stuff, which I don't care about as I don't have any applicable hardware. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I just bought a Z-Wave controller and wanted to flash the newest firmware. I was struggling a bit because SiLabs changed some essential parts and did not manage to add a functioning link on their website to the release notes. To set the RF region, start the Z-Wave PC Controller -> Transmit Settings -> RF region. Yet, I am hoping for a soon release of version 7.17.0.1 as the current version is marked as beta version. |
Beta Was this translation helpful? Give feedback.
-
|
How does one find the firmware using linux? It doesn't appear to be in the tar file they provide, and the simplicity studio fails to download any SDKs or packages. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know. Even though I mainly use linux, I run Simplicity Studio under Windows as the PC Controller is only available in the Windows version and I need it sometimes. |
Beta Was this translation helpful? Give feedback.
-
|
FYI, Silicon Labs now look to have at least posted Gecko SDK (GSDK) version 4.0.0 in a publicly available repository on GitHub for reference: https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.0/protocol/z-wave/Apps/bin/gbl On Windows go to the directory/folder and do the following commands for git remote and git pull (check out this guide and also this guide): git remote set-url origin https://github.com/SiliconLabs/gecko_sdk/
git pullLooks like same get under \SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v4.0\ when install the latest Simplicity Studio 5. Otherwise, you can get all the same files by downloading and installing the latest version of Simplicity Studio 5 for Linux, Mac, or Windows: https://www.silabs.com/developers/simplicity-studio Not sure if Silabs plan to keep updating that public GitHub repo with newer versions of their Gecko SDK or not. https://github.com/SiliconLabs/gecko_sdk/releases At least it looks like it was released publicly on purpose. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that it works for Linux. If you try, then it tells you at the end that it works on windows only. |
Beta Was this translation helpful? Give feedback.
-
|
I am getting the error (Windows 10) -- "Firmware update failed: can't open XModem session" |
Beta Was this translation helpful? Give feedback.
-
|
I am in the same boat. How did you resolve your issue? I tried a different driver and no dice. Zooz USB S2 700 Getting the same I am getting the error (Windows 10) -- "Firmware update failed: can't open XModem session" |
Beta Was this translation helpful? Give feedback.
-
|
@barrios35 we're currently adding support for OTW firmware updates. Z-Wave JS UI will have it soon. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome!!! Thanks @AlCalzone |
Beta Was this translation helpful? Give feedback.
-
|
@AlCalzone: That is very awesome. Thanks so much. |
Beta Was this translation helpful? Give feedback.
-
|
Silicon Labs UZB-7 uses a CP2102N USB-to-Serial Converter chip so require CP210x USB to UART Bridge VCP Drivers on Windows: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers Note that rebooting/restarting of Windows operating-system is normally needed when installing drivers for serial devices. Then follow: https://community.silabs.com/s/article/z-wave-700-programming-uzb7-controller-stick?language=ja Or try "OTW Firmware Update" (Over-The-Wire) option in "Z-Wave PC Controller" tool from latest Silicon Labs Simplicity Studio: https://help.aeotec.com/support/solutions/articles/6000252296-update-z-stick-7-with-windows |
Beta Was this translation helpful? Give feedback.
-
|
FYI, here is direct links for EU and US regions to 7.17.2 firmware image download for Silicon Labs UZB-7 (Silabs SKU: SLUSB001A/SLUSB7000A) (based on EFR32ZG14): As mentioned before, Silicon Labs are now releasing on GitHub so other regions and different chips can also be found by selecting "Go to file" on https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.0/protocol/z-wave/Apps/bin/gbl and then entering " |
Beta Was this translation helpful? Give feedback.
-
|
Anyway to perform OTW downgrade firmware version or to do OTW flash with different region firmware of the same version? Reason is that I screwed up and flashed the US instead of the EU version of 7.17.2 firmware in my production Z-Wave network. |
Beta Was this translation helpful? Give feedback.
-
|
I have now changed the region using the Z-Wave PC Controller tool from Silicon Labs Simplicity Studio SDK: https://community.silabs.com/s/article/z-wave-700-how-to-change-the-region-on-controller-devices That does however not answer the question about the possibility of flashing older firmware to downgrade. |
Beta Was this translation helpful? Give feedback.
-
|
Silicon Labs Gecko SDK (GSDK) 4.1.0 has now been released with Z-Wave and Z-Wave Long Range 700/800 SDK 7.18.0.0 https://github.com/SiliconLabs/gecko_sdk/releases https://www.silabs.com/documents/public/release-notes/SRN14889-7.18.0.0.pdf Yeah wondering which prebuilt firmware image to use for EFR32ZG14 based dongles like Silicon Labs UZB-7, Aeotec Z-Stick 7, Zooz USB 700 Series Z-Wave Plus S2 Stick ZST10? https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.1/protocol/z-wave/Apps/bin/gbl Guessing it is either "BRD4201A" or "BRD4206A" based on these hardware kit/board configurations? https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.1/hardware/kit https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.1/hardware/board/component/ Also, look like Silabs slightly changed Z-Wave firmware naming convention/terminology by now calling it a "ZWave NCP Serial API Controller"? Guess it "zwave_ncp_serial_api_controller_......gbl" but wonder which version? And seems there no more prebuilt region specific firmware image files? Maybe "zwave_ncp_serial_api_controller_BRD4201A" or perhaps "zwave_ncp_serial_api_controller_BRD4206A" or other? |
Beta Was this translation helpful? Give feedback.
-
|
Well, for 7.17.2 on my US Aeotec Z-Stick 7, I used: ZW_SerialAPI_Controller_7_17_2_406_EFR32ZG14_REGION_US.gbl. I believe the BRD part numbers are the development boards themselves. If I go to the gbl link you posted above and then switch to the 4.0 branch, notice the number of files in that directory goes from a bajillion down to just the BRD partnumbers. Perhaps they haven't published or finished the non-dev board firmwares yet? |
Beta Was this translation helpful? Give feedback.
-
|
Silicon Labs has a new OTW article for 700/800 controllers that confirms the board P/Ns, their chipsets, and the corresponding firmware files.
|
Beta Was this translation helpful? Give feedback.
-
|
Note that there is not always a one-to-one mapping of chipset to board number. I would contact your stick's vendor for the correct file prior to upgrading. The Aeotec (EFR32ZG14) is using BRD4206A, while Homeseer (ZGM130S) is using BRD4202A (not BRD4207A). |
Beta Was this translation helpful? Give feedback.
-
|
have you figured out yet which one applies to |
Beta Was this translation helpful? Give feedback.
-
|
I don't claim to have any special knowledge of the specifics, but short version is there doesn't appear to be a correct choice for a UZB-7 there yet (it is also EFR32ZG14 like the Aeotec Z-Stick 7s I have). All of the part numbers shown are for the development kit boards. For example, I purchased a a 1st-gen Z-Wave 700 Starter Kit (SLWSTK6050A) and it came with two dev boards. The board itself is part number BRD4001A, the radio board is BRD4202A. And you can see in that folder in tag v4.1.0, there's plenty of BRD4202A options, but nothing for EFR32ZG14. So unless they've moved the non-dev board stuff to a different folder, I guess we wait for v4.1.1 to show up in github with more stuff. :) EDIT: In tag v4.0.2, there's a total of 1040 gbl files in the repo. In tag v4.1.0, there's only 132. |
Beta Was this translation helpful? Give feedback.
-
|
Well now I'm wondering if BRD4206A could be used ... It appears that BRD4206A is functionally an EFR32ZG14, according to these Z-Wave 7.18.0 release notes: I'll try this out and see what happens. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, confirmed -- I was able to use PC Controller to update an Aeotec Zstick 7 (EFR32ZG14) from 7.17.2 to 7.18.0 by using image zwave_ncp_serial_api_controller_BRD4206A.gbl. I'm successful interacting with other nodes (Node Info, Get Version, etc) from PC Controller. Nothing beyond that. |
Beta Was this translation helpful? Give feedback.
-
|
Any benefits to upgrading? |
Beta Was this translation helpful? Give feedback.
-
|
@Hedda SiLabs Gecko SDK v4.1.1 was released [https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.1.1] the naming convention remains different, not sure what, if any I should upgrade to for my Zooz 700 series stick. [https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.1/protocol/z-wave/Apps/bin/gbl] |
Beta Was this translation helpful? Give feedback.
-
|
Since I need to update my new Z-stick 7, should I go with 7.18.0 or stay on 7.17.2? 7.18.0 is "pre-certified", whereas 7.17.x has been certified externally, if I understand the documentation correctly. |
Beta Was this translation helpful? Give feedback.
-
|
If it is used for a critical production system for you then it is probably best to wait until more people confirm that is works as good or better as I understand that it is currently not possible to downgrade to older version, only upgrade to a newer version. |
Beta Was this translation helpful? Give feedback.
-
Unless there is a specific bug you are experiencing in the GA release, or are a developer testing a new feature only present in the pre-GA, then always stick with the GA release. Newer is NOT always better, and that has been true multiple times in the zwave firmware release chains. So for now, stay on 7.17.2. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, it's what I thought. Unfortunately, the Z-Stick has the same (apparently) transmit power issues that plagued the first one. And it looks like other people have the same problem: https://siliconlabs.force.com/community/s/question/0D58Y00008GEzWtSAL/hellois-it-possible-to-improve-power-of-new-z-stick-700-or-do-something-with-it-i-replaced-the-z-stick-500-but-from-that-moment-some-devices-turn-dead-each-time-and-then-come-back-again |
Beta Was this translation helpful? Give feedback.
-
|
Small update. UZB7 set to EU 7.19.1 issue
I think this is interesting as two loads of the exact same firmware image different results. While the power and region is fine, device control and adding is still terrible. Possibly indicates the conversion of the memory can fail between versions. If I can workout how to do a build that flashes I will dig deeper. **Update **. Have working build so I can start digging. Worked out that the Bootloader folder with the sample keys had moved to a new location. Used the controller keys and GBL flashed with PC Controller. If anyone is trying and having issues packaging a working sample I am happy to share the little knowledge I have. Initial testing indicates all working. Node added fine and range very good. Security working etc. I am not sure what I conclude from this other than the initial flash did not work but after a few flashes it started to work. Possibly it is the memory reconfiguration conversion can fail but a few tries pushes it through. All I can suggest to those having issue in EU is keep flashing the stick and see if the issue clears. I have not done anything different as the new version I built will be identical to the one you can download. |
Beta Was this translation helpful? Give feedback.
-
Thanks for providing the files. Using PC Controller, from 7.19.1, I was able to flash nolimit. Thereafter, PC Controller no longer recognized the stick. I then used xmodem to flash to 7.17.1 (I now see what you mean by "run it"). At this point, PC Controller showed no region and I was not able to set it. I then updated to 7.18.1 and was able to set the region and Z-Wave JS UI properly displayed the region. That's where I stopped. I will stay back before 7.19 gets sorted out. I see you posted 7.18.4 so I will update to that. Hopefully everything stays alive... Thanks for all your work. Thank you @AlCalzone too for the help. |
Beta Was this translation helpful? Give feedback.
-
|
The NVM reconfiguration code has a lot going on. I am not surprised going back versions gives odd results or that it is possible to have odd behaviour with some upgrades. so if the file sys is not reconfigured it throws an assertion so could leave the settings in the wrong state If anyone has a 7.19.1 that is not happy and has a 7.17.1 backup or before but not before 7.15.3 and are willing to take the risk of loading it then they might fix their issues. The conversion from 7.15.3 file system is called if the file version is less than the current version when the file system is initialised. No guarantees. |
Beta Was this translation helpful? Give feedback.
-
So none of the configurations are set in the version of the bootloader. As to signed, the sample signing key is public so anyone can build a GBL to do bad things. Even with the locked bootloader the risk is the same. |
Beta Was this translation helpful? Give feedback.
-
|
Were you ever able to create a version which verified signed upgrades? If not its OK. Im going to roll with the unlocked bootloader. Ive gotten myself onto version 7.21.0 of the BD4206A version which has destroyed my signal. Having just deployed some LR devices I would like to get back to version 7.18.8 and the only way to do so besides buying a new UZB7 is to use your bootloader. Thank you for your work and making this possible. |
Beta Was this translation helpful? Give feedback.
-
|
The unlocked bootloader allowed me to roll back the controller firmware. This ulitmately allowed to to get a "stable" version installed. |
Beta Was this translation helpful? Give feedback.
-
|
I updated yesterday my SLUSB7000A from 7.11 to 7.19.1 using BRD4206A.gbl, not knowing that 7.19.1 was actually a very recent release (Just took what was linked here). However, when I updated, my region was reset to EU. Z-Wave JS UI doesn't seem to be able to set the region on that version, as of today, so I loaded the PC Controller software and managed to update my region there.
However, the range of my device tanked to almost nothing compared to what it was. Debug data from Z-Wave JS told me that the RSSI of the messages I was receiving were close to -100dBm, which really doesn't make sense for a device close to the controller. I was sure something was wrong and saw people talking about a wrong SAW pin output causing issues with the EU region. I checked my SAW pin outputs and both are low, even if my region is set to US. I wanted to make sure that it was indeed that making it that bad, so I shorted TP13 (S2) to 3.3V (VDD) while doing a Polling test on PC Controller. Unsurprisingly, as soon as I shorted that, the poll requests would work, and stop as soon as I removed the short. Took a short video that demonstrate it. Video-Mon-Feb-06-2023-12-14-39.webmSo there seems to still be a GPIO issue for the SAW, but now for the US region, or my UZB-7 just died exactly when that update happened. Edit : Forgot to also say - I also noticed a weird behavior sometime, where the SAW GPIOs seems to flap to ~0.5v and die back down every ~2s, like if the GPIO was tripping on overcurrent protection or something. The thing is that it happens on both SAW pins, which is still inconsistent with the fact that it should only try to put S2 high, and not S1, while I'm seeing the same flapping on both while the region is set to US. |
Beta Was this translation helpful? Give feedback.
-
|
Try setting the TX power level normal to 140. If the flash to 7.19.1 is good the SAW setting does work. |
Beta Was this translation helpful? Give feedback.
-
In my case, TX is not the issue, it's RX. I've used level 127 and measured -33 with a little more success, but really poor still. The fact that shorting that pin fixes it clearly shows the GPIO state not being correct. Per the XMSSJE3G0PA-002 IC specs, a pin high would be > 1.3-1.8v and It's clearly not that on both S1 and S2. |
Beta Was this translation helpful? Give feedback.
-
|
That is what I had first time I flashed but same version now works. Update that is with my own build targeting 4201 board. |
Beta Was this translation helpful? Give feedback.
-
|
I did a solder job to permanently tie S2 to VDD and now it's working like before. I knocked a poor capaciter off but it seems like everything is still working as expected so I won't complain too much. Most likely will replace the stick with a Z Wave 800 eventually. |
Beta Was this translation helpful? Give feedback.
-
|
Are these TX/RX/region reset/GPIO issues with 7.19/7.19.1, and is it pervasive on all SL UZB-7s? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Big head slap from me. Why BRD4206A.gbl the UZB-7 should be BRD4201A.gbl.
This kit board product if you want to build the sample. |
Beta Was this translation helpful? Give feedback.
-
|
Limit EU is 13 output but 140 = 14 but not the measured so you will get about 13 due to losses. |
Beta Was this translation helpful? Give feedback.
-
|
If you are concerned and can not measure set 130 |
Beta Was this translation helpful? Give feedback.
-
|
If you have a zniffer check the RSSI vs a european slave at the same distance between zniffer and transmitter. Tune to make them similar and you are probably safe. Fibaro slaves I believe are all set to max so compare to one of those with no obstructions. |
Beta Was this translation helpful? Give feedback.
-
I have changed my Z-Stick 7 to BRD4201A with the unlocked bootloader (took quite a few tries, but it eventually worked), and it works, but at the same disappointing level as previously. Looks like this stick is just not very good at all, at least in the EU version. |
Beta Was this translation helpful? Give feedback.
-
|
Ive had some dead nodes now as well :/ sadly the firmware update/change did not fully help |
Beta Was this translation helpful? Give feedback.
-
|
I just upgraded from 7.18.1 to 7.19.2.0 GA released March 8. |
Beta Was this translation helpful? Give feedback.
-
|
Which version did you use? BRD4206A or BRN4201A? |
Beta Was this translation helpful? Give feedback.
-
|
I've used the BRD4206A, according to this from Silicon Labs.
|
Beta Was this translation helpful? Give feedback.
-
|
Just find out that the SLUSB001A (UZB-7) show as a ZST10-700 (Zooz) under Z-Wave JS but seem to work ok. |
Beta Was this translation helpful? Give feedback.
-
FYI, if you use Home Assistant then it is a known problem that USB discovery for Z-Wave USB is a little too generic now. See this issue: |
Beta Was this translation helpful? Give feedback.
-
|
Hello there! I have a Silicon Labs SLUSB7000A stick with 7.11.0 firmware. The PCB inside is marked "BRD1001A". It is not clear to me which firmware file I should use to update. I see both "BRD4206A" and "BRD4201A" discussed here. Does anyone know which I should use? Thanks!
|
Beta Was this translation helpful? Give feedback.
-
|
I have the same one and yet to find a fw. Any luck? |
Beta Was this translation helpful? Give feedback.
-
|
I have the same exact board I updated to 7.17.2 then 7.19.3 using the files listed there https://aeotec.freshdesk.com/support/solutions/articles/6000252296-update-z-stick-7-with-windows. Z-Wave JS is correctly showing FW v7.19.3. |
Beta Was this translation helpful? Give feedback.
-
|
Version 7.20.0 released. https://www.silabs.com/documents/public/release-notes/SRN14930-7.20.0.0.pdf |
Beta Was this translation helpful? Give feedback.
-
|
Version 7.20.1.0 is out via Gecko SDK Release 4.3.1 https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.3.1 I noticed in the release notes -- "Known issues from current release" Serial API controller unable to update to 7.20. Curious if anyone is successful in upgrading to this latest version. |
Beta Was this translation helpful? Give feedback.
-
Meanwhile at Silabs: sounds good. Ship it! |
Beta Was this translation helpful? Give feedback.
-
|
I tried to upgrade my UZB7 from 7.17.2 to 7.20.1 using PC Controller and got "Serial upload aborted file error 0x18". Does anyone know the difference between the BRD4201A and BRD4206A firmware versions? |
Beta Was this translation helpful? Give feedback.
-
|
My guess is that BRD4201A supports SAW filter which allows different regions to be selected. BRD4206A supports Long Range mode, but does not support SAW (locked to US market in that case). But that is just a guess. |
Beta Was this translation helpful? Give feedback.
-
|
I guess BRD4201A is the one to use in Europe then? I have used this with success, but was confused by an knowledge article from Silicon Labs only mentioning BRD4206A. |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone succeed in upgrading to 7.20.1, i'm also getting error 0x18. |
Beta Was this translation helpful? Give feedback.
-
|
@AlCalzone why even bothering to release a new version then? |
Beta Was this translation helpful? Give feedback.
-
|
🤷♂️ |
Beta Was this translation helpful? Give feedback.
-
|
I will update the latest test results so far, It's just that it's currently experiencing another strange problem, It can only be said that it is indeed possible to upgrade, but the function is still abnormal and not perfect, the following is a picture of my successful upgrade to UZB7: |
Beta Was this translation helpful? Give feedback.
-
@AlCalzone Is that really an error message and not just an information message? And do you know if this UZB-7 USB Stick (Silabs SLUSB001A / SLUSB7000A) hardware with latest Z-Wave chip ZW0700 firmware actually has enabled support Z-Wave Long Range (LR)? And if so does Zwave JS enable Z-Wave LR automatically for all regions (countries)? ...and finally, the follow-up question for that is if it is only supported if choosen "US_LR" as the region (meaning that it can currently only be supported in the USA or?)? https://community.silabs.com/s/article/how-to-set-up-z-wave-long-range?language=en_US https://www.silabs.com/wireless/z-wave/z-wave-long-range-overview I believe this same UZB-7 USB stick dongle is the official Z-Wave 700 reference design from Z-Wave 700 ZGM130S Long Range Wireless Starter Kit, or? https://www.silabs.com/development-tools/wireless/z-wave/z-wave-700-starter-kit https://www.silabs.com/development-tools/wireless/z-wave/z-wave-long-range-700-starter-kit https://www.mouser.se/new/silicon-labs/silabs-z-wave-800-dev-tool/ |
Beta Was this translation helpful? Give feedback.
-
|
The command used by the stick to notify us about restarts includes information whether Long Range is supported. I assume this is where the message above comes from. Not sure though why it appears 4 times in a row. For the other questions: I'm not sure, I haven't looked too much at supporting LR for now. |
Beta Was this translation helpful? Give feedback.
-
|
I rebuilt 7.20 from source with the correct keys. You are welcome to try it. The GBL file is in this zip. This updates ok for our SmartStick and ZNET: |
Beta Was this translation helpful? Give feedback.
-
|
We still can not 'officially' upgrade to the latest Gecko SDK (GSDK) Version 4.3.2.0 contained |
Beta Was this translation helpful? Give feedback.
-
|
I've successfully upgraded from 7.19.4 to latest 7.21.0 Gecko SDK (GSDK) Version 4.4.0 whitout errors using Z-Wave PC Controller and zwave_ncp_serial_api_controller_BRD4206A.gbl. All nodes reporting fine in HA Z-Wave JS. |
Beta Was this translation helpful? Give feedback.
-
|
Naive question - is it possible to do it through HA by going to Settings/Devices/Z-wave/USB-Controller/Update? |
Beta Was this translation helpful? Give feedback.
-
|
Basically not impossible, as that process in theory just calls Z-Wave JS corresponding function, which should work. Sadly (as I wrote lat night), in my case with Z-Wave JS something went wrong. The process was very fast... 2-3 sec. if I remember right, I did not have time to really realise what happened, and in my next breath I simply just got bootloader error with the dongle, so never again could be 'reached' ( As I remembered that the 'low-level' flashing with Minicom is something like low-level serial data pass, I tried and luckily it worked. |
Beta Was this translation helpful? Give feedback.
-
|
I did the upgrade also on a day when Gecko 4.4 released. First time through Z-Wave JS, but with a half bricked dongle as the result. Then I made a 'forced' flash again through Linux - CLI with Minicom, successfully, and since that I have no problems with it. So seems for me the/this latest firmware works fine also... |
Beta Was this translation helpful? Give feedback.
-
|
7.21.0 is still broken for me, using both 4201A and 4206A. After upgrade, region is shown as Unknown and Measured output power is 0.1 dBm. Pings to nodes fail. Setting these values to the correct ones (0/3.3 and USA or USA Long Range) also fails. Downgrading back to 7.18 the region and powerlevels are restored to the correct ones and pings work again. Setting region logs
Seting powerlevels logs
The same actions also fail when using PC Controller. |
Beta Was this translation helpful? Give feedback.
-
|
Pretty disappointed in 7.21.2 not fixing the lockup issue but I do see it has fixed direct upgrades from 7.17.x to newer firmwares |
Beta Was this translation helpful? Give feedback.
-
|
I cannot believe it... |
Beta Was this translation helpful? Give feedback.
-
|
Here is the thread on silabs own community board (where they promissed a fix in this latest release) - if more people signed up and expressed their (polite) opinion, perhaps the matter would get even more attention on their side |
Beta Was this translation helpful? Give feedback.
-
|
It's not possible. I hope it's a joke and they repair the protocol. |
Beta Was this translation helpful? Give feedback.
-
|
Just upgraded to 7.21.5 with the BRD4206A file, on my UZB-7 (SLUSB7000A, chip marked BRD1001A). Region set as EU, TX Power Normal at 140 (14dBm) and Tw Power Level Measured at 0. I have the range issues discussed over here. Devices literally needs to be within 50 - 100 cm of the controller. So I have tried to downgrade the firmware, and I have tried to install the same version 7.21.5 but the BRD4201A flavour instead to no avail. All attempts at doing OTW gives the 0x18 error code. Which I guess is due to this note on silabs website Did anyone previously have range issues and manage to solve them? Any tips to give? This firmware debacle is just redicilous at this point. It's more tempting to just give up and look for other options to be honest. |
Beta Was this translation helpful? Give feedback.
-
|
There is an unlocked bootloader that removes the version check. It should allow you to re-install the same version for a different board. Unless you want to dig in a huge github discussion thread, it's most easy to find on Aeotec's support website: https://aeotec.freshdesk.com/support/solutions/articles/6000270183-z-stick-7-update-or-downgrade-with-zwavejs-firmware-flasher-and-nodejs -> scroll down to "4. Downgrading with ZWaveJS Firmware Flasher", download the linked bootloader, flash this one first, then the firmware you want to install. |
Beta Was this translation helpful? Give feedback.
-
Mate, you are a life saver! This worked like a charm. Thank you so much! So as a reference for others. I first installed 7.21.5 (BRD4206A) through z-wave js ui. Firmware update was successfull. However all my nodes died and nothing responded to pings. I took one of my battery operated sensors and brought it to my server, to which it responded again. As soon as I went more than ~1m away from my server it was unable to reach the controller. The background RSSI that z-wave js ui reported was around -120dBm on the controller, and the signal strength (when looking at the line between the node and the controller in the network graph) was also around -100 or -90dBm when the device was literally 50 cm away. With the help of the unlocked bootloader I was finally able to flash 7.21.5, so the same version, but the BRD4201A flavour. Now I have three nodes that are two floors down and behind atleast two walls, without issues. Two mains powered, one battery-powered. Background RSSI on the controller dropped to about -90dBm. Unsure if that is good enough, but atleast it got lower with the new firmware. I used z-wave js ui to set the region to Europe, normal power level to 13dBm and measured power to 0dBm. No issues there. I did however see the "controller jammed" message once today. So I am hoping that was just due to excessive chatter while interviewing, pairing, grouping and changing config on the nodes. |
Beta Was this translation helpful? Give feedback.
-
Nope, firmware is bugged as hell. |
Beta Was this translation helpful? Give feedback.
and others
Note! You first need to update firmware to a later GA (General Availability) version of firmware before using UZB-7 as a commercial product.
Official firmware for zwave_ncp_serial_api_controller_BRD4206A firmware images that Silicon Labs UZB-7 (SLUSB001A) needs found here:
https://github.com/SiliconLabs/gecko_sdk
Link example for Silicon Labs Gecko SDK (GSDK) Version 4.1.6 (which contains Z-Wave and Z-Wave Long Range 700/800 SDK 7.18.8.0, see):
https://github.com/SiliconLabs/gecko_sdk/tree/v4.1.6/protocol/z-wave/Apps/bin/gbl
Note! It is important to first update to 7.18.8 first before updating to 7.20.X or later!
Update: "Z-Wave Controller firmwares based on Z-Wave SDK 7.19.3 have a bug t…