Every single time I upgrade the HA OS the Z-Wave JS Add-On gets messed up and rather than rebuild it again I would really like to fix it as well as understand why this happens.
I am using a Zwave.me stick on a USB 3 port of a Raspberry Pi 4
My settings are still intact, but it fails to talk to the stick with the following info:
Failed to save add-on configuration, Device ‘/dev/serial/by-id/usb-0658_0200-if00’ does not exist in Z-Wave JS (core_zwave_js)
I have to assume that when I upgrade the OS something happens to the Device /dev/xxx. I assume if I can find the dang Device and replace it in YAML it would work but I can’t find it in Host Hardware. I did try /dev/ttyAMA0 for kicks, but I believe that is mapped to something else, maybe Bluetooth but in any event it fails.
Can someone point me in the right direction to correct this?
I am on version 0.1.51 of Z-Wave JS and a version or two ago they removed the ability to manually input the device path from the GUI but I can go to YAML and put it in there. It was actually in there fine but wasn’t working so I changed it to /dev/ttyAMA0 just to see since that worked 4 OS updates ago but has not since. Now if I try to use the path: /dev/serial/by-id/usb-0658_0200-if00 I get the error above. The by-id came directly from a backup of the addon.json but was also in the YAML config.
I have rebooted the Pi several times and moved the stick around to different USB ports as well, no go.
I upgraded to 1.51 prior to upgrading to the new OS and it was working fine. I have a feeling it has to do with the zwave.me stick because I run into this 5 out of 7 times I upgrade the OS. I’ve literally spent 30+ hours rebuilding my zwave network over 2020 because I have to uninstall ZwaveJS, reinstall then it finds the stick then go through exclude/include on all my devices then fix cards and automations. It royally sucks!
That was a big “no go”. I wasn’t thinking but the restore doesn’t roll back the OS which is when the problem stared. I am confident it is just a crappy Z-Wave controller or perhaps it was defective from the git go.
I appreciate all the help but am giving up at this point and will buy a different controller.
I’ve been waiting quite a while for Aeotec 7 stock to return also. I purchased a Zooz ZST10, but when I found out you can’t backup or update that controller it got relegated to the ‘shelf’.
Curious @ServiceXp did you ever try the utilities that Aeotec uses for backup and restore? From what I am seeing, the Zooz is a clone of Aeotec and just might work.
Also, do you use Zwave2Mqtt? I was using it and love it but having to rebuild after most OS updates I dumped it to eliminate the extra work.
The Zooz isn’t a clone. It uses a different Z-Wave module, ZM130S, while the Aeotec controllers use the EFR32ZG14. The Aeotec controllers also have a custom designed antenna that is tuned for the specific region. Zooz does not.
Aeotec doesn’t have a backup utility for the 700-series. They instruct you to use the PC-Controller software from Silicon Labs. That supports all controllers. Node-zwave-js also supports backup and restore, and conversion between any NVM version, including 500 to 700 sticks, so might as well use it if you’re already using Z2M.
I will assume you are talking about z-wave2mqtt? Which I haven’t tried yet. Well, that’s a lie. I tried for about an hour but could not get it to connect to the stick, so I gave up.
