800 Series Z-Wave Controller Support Tracker #5257
Comments
blhoward2
changed the title
|
I'm able to successfully include and exclude with None security with both the 800-series and 500-series devices I've tried. The 800-series device didn't want to SmartStart, but it's a beta device and I've had problems with it SmartStarting before, so not sure if it's the stick or the device. Heal and reinterview seem fine with the same test devices as above. As do health checks back to the controller. Sends and gets of Multilevel Switch v4 and v2 values work. Same with Color Switch v1, Config v1, and Config v2. Getting Meter v2 values seems to work as well. In the UI, the RF Region defaulted to USA LR, but things seemed to be working in normal mesh mode. A change of that setting to USA didn't change anything functionally that I can see. |
|
I just excluded my 800-series device and it reincluded with SmartStart S2 successfully. |
|
This is for 800 series controllers, not devices. Devices are backwards compatible. |
blhoward2
changed the title
Yes, correct. I'm testing with the 800-series stick I just got. It just happens one of the devices on my test/dev network is also 800-series. |
|
Got it, thanks! |
|
Also, to back up what you already have up there, I tried restoring an NVM backup from my previous 700-series stick to my 800-series stick and got the following error:
|
|
Does backup from the 800 work? If so can you send a copy of a backup with a device included to info@zwave-js.io? |
|
There was no error, but the file produced was 0 bytes. |
|
Ok, thanks. Can you confirm your fw version? Can you post a log of the restore attempt? |
|
|
I have a SiLabs 800 dev kit. I had to upgrade to firmware 7.19.0 for NVM backup to work, otherwise I was seeing the same 0-byte file. 7.19.0 is a "Pre-Certified GA", which is more like a beta. I don't see anything obvious in the release notes to indicate this was fixed, but it made a difference. Here's a backup of the 800 after a factory reset. I don't know if it actually produced a valid fail, but the process was successful and the file size non-zero (it's roughly the same size as a 700 backup). Here's my version info: The SiLabs dev kit and the Zooz stick are different kinds of modules (ZGM230S SiP Module vs. ZG23 SoC), akin to Aeotec Z-Stick 7 vs. Zooz 700. Not sure if that makes any difference. It appears Zooz is using a custom controller firmware now?
In that case, I would have to assume you should not use the generic SiLabs firmware files like with the 700. The restore from a 700 still did not work, however the error is different. Looks like Z-Wave JS doesn't recognize the format (assuming the backup was actually valid): I also noticed changing the region in Z-Wave JS is failing. I tried to switch from US LR to US: I had to restart Z-Wave JS as Get Region continued to show Unknown (perhaps a soft reset would have sufficed). |
|
From the Zooz stick: Notably different from the SiLabs 800 dev kit. |
Well that would be because I update it every Gecko release. The latest Pre-Certified came out yesterday. I don't remember what it arrived with, probably < 7.18. The Zooz sticks may have been manufactured prior to 7.18.2 (the last relevant GA release) and shipped that way. 🤷🏻♂️ Also, I would advise not attempting to use PC Controller to backup and restore from a 700. It bricked my 800 and I had to recover it using some of the debug tools. 😅 |
|
I also have a Zooz 800 usb tick, so posting here to follow along as the thread is updated. |
|
I have a working ZooZ 800 but not all functions of course, watching. |
|
Similar as above two -- ZooZ ZST39 (800 stick), generally working, a few nodes in my 54-device network (not always the same ones each time) seem to go dead every day and need to be pinged. Also sometimes gets stuck in "Exclude failed" mode when I'm trying to add or remove devices, requiring a VM reboot. Not sure if it's the stick or the network, as this is first time experience with both HA/Zwave-JS and the 800-stick. Watching the thread for knowledge updates. "FW 1.1 SDK 7.18.1". |
This occurs on 700 series controllers as well, I have 115 node 700 series z-wave network, all devices connect directly to the controller and this occurs at least 1 time a day if not more. I have had to setup automation to ping the dead nodes so they don't stay dead longer than 30 minutes at a time. |
It hasn't been clear whether this was a firmware issue or a Z-Wave JS issue. I had read some posts indicating that the firmware updates solved the problem, but then again I just read another (recent) set that firmware updates did nothing. I also have set up HA to automatically ping the dead nodes. |
|
I have 103 devices on my mesh (74 repeater, 29 battery), and I have only seen nodes go dead a couple times in the past year. Certainly not daily, weekly, or enough that I setup a scheduled ping. So I don't know - could be controller, device, or mesh dependent? Certainly not a universal thing on zwave js though. |
|
I have 55 devices on my network. I have tested on 500, 700 and 800 controller. On UZB1(500) I did not see dead nodes running several years. On 700 (Z-Stick 7 SDK 7.18.1) and 800 (ZVidar SDK 7.18.3) I have dead nodes daily. Screenshot from yesterday: |
|
Odd. I currently use a uzb7 on US frequency, in case it matters. No dead nodes. Anyway, that is probably a better discussion for a different thread anyway, so we don't derail this one. |
|
How do you chart dead nodes and how do you instruct HASS to automatically ping them? |
|
Let's please move this discussion to its own issue or a discussion. This issue is not for individual troubleshooting or potential issues larger than the 800 series controllers. |
|
What is the best way to move from a 700 to a new 800 stick? NVM backup/restore or Controller Shift? |
From my past experience with 700 series I wouldn't touch 800 with a stick. I would probably suggest 500 series still for a couple more months just to be on the safe side. |
|
Silabs said they have a fix for the lockup in 7.21.2 which is scheduled for mid April. |
|
@AlCalzone the lockup issue is 800 series only or does it affect 700 series as well? |
|
Both AFAIK |
|
Hi. I am trying to get Long Range to work and have been unsuccessful. Has anyone been able to? Thanks! |
|
Are you using the Z-Wave JS UI beta release with LR support? And have you set your controller to the USA Long Range region? |
|
Hi @AlCalzone. Ah. I believe the issue is that I am not using the beta. Can you please tell me how to switch to the beta or direct me to the instructions? Thanks! |
|
@robertsLando can you answer that? |
|
@notrackingme If you are using docker just use the PR ref: zwave-js/zwave-js-ui#3545 |
@asayler I've completely given up on my 800 series controller at this point and migrated back to my gen5 stick. Mine was in that state multiple times per day, got tired of manually resetting it. Since I've ditched it for the 500 series controller, it's been smooth sailing! |
|
I just tried to backup RaZberry 7 Pro and restore on Zooz 800 GPIO and got this error. Running latest firmware/SDK on both controllers and latest zwave-js-ui. |
|
What's "latest" SDK specifically? 7.19.x or higher should work. |
|
@AlCalzone I updated Zooz 800 to SDK 7.19.3 before attempting to restore. Backup file was generated on SDK 7.20.0 (RaZberry 7 Pro). So I assumed that will work but I hit that error above 🤔 I can see in the code that it tries to parse as 700 series NVM, it returns NVM_InvalidFormat so it fallbacks to 500 series parsing: node-zwave-js/packages/nvmedit/src/convert.ts Line 1367 in 4229045 Is there a way how to debug exported NVM backup? |
|
You can send the backup files to my email. I'll take a look when I'm back at work next week. |
|
I've been using the
Really pleased with this. I was already using an 800 series controller so I didn't have to do any of the migration that other folks have dealt with in this thread. |
|
@evanfoster I assume that the controller wasn't actually "bricked", but stuck in bootloader mode and Z-Wave JS didn't fully recognize this - some newer bootloaders have a slightly different "menu" structure. You should be able to recover by starting Z-Wave JS in "bootloader only" mode (see settings). |
|
800 series support is considered complete, I'll close this issue. |
|
This is awesome, thanks so much for all your work. Just to confirm after upgrading to this zwave-js release, setting the right LR frequency, and generating LR keys, any pre-existing 800 LR devices need to be excluded/re-included via smart start to take advantage? |
|
Zui 9.10 is out with LR support 🎉 |
Correct. Also, including ZWLR devices only works via SmartStart. Scan the QR code, switch the protocol to Long Range, then enable the provisioning entry. |
|
Thanks Al, I migrated two Zooz switches over lunch. One ZEN77 800LR and one ZEN76 800LR and both went fine! They setup as “beaming unsupported”, I assume this was expected since it would be redundant or otherwise not needed for such devices to do so now? |
|
Honestly, I'm not sure here but I assume since ZWLR doesn't have direct associations (yet?), mains-powered end devices don't beam - they don't need to communicate with FLiRS devices. |
Hi I have a HUSBZB-1 Gen 5 (SDK: v6.51.7), the backup nvm works. Thanks |
|
Unlikely, The SDK is too old. While you can back it up you won't be able to restore it, zwave will refuse to because it won't be able to convert the NVM format. |
|
Okay thanks for your reply |
I noticed that 7.21.3 GA SDK was released by Silcon Labs a couple of weeks ago, but Zooz hasn't released a ZST39 firmware based on it (nor the 7.21.2 before it) yet. Looking at the release notes for 7.21.3 from SiLabs, there were two interesting points:
Anyway, seems like the wait for a fix to the controller lockup issue continues... |
|
The controller lockup topic is being discussed at #6512. |
and others
Update (2024-04-02)
800 series controllers are fully supported as of https://github.com/zwave-js/node-zwave-js/releases/tag/v12.4.4.
NVM Backup/Restore requires a firmware based on Z-Wave SDK 7.19.0 or higher.
Experimental Long Range support is available in https://github.com/zwave-js/node-zwave-js/releases/tag/v12.5.0, which is being released now
The text was updated successfully, but these errors were encountered: