Having a really difficult time lately with Z-wave.
I initially went the path of least resistance, setting things up using what seemed to be the default option, using Z-Wave JS. However, I’ve had all sorts of odd things happen. Devices go “dead” after a while. Often they don’t pair up and leave behind mysterious “nodes”. Sometimes the device shows, but there’s no controls, even though a previous pairing with my Z-wave USB stick and Home Assistant was fine.
To try to remedy this, I looked into Z-Wave JS UI. From there, it only got less user-friendly and more confusing. I can’t see how the multitude of settings in Z-Wave JS translates to a simple tottle for a light on or off.
So, what should I use? Is the built in Z-Wave JS just horribly unstable and Z-Wave JS UI is the way to go? If so, why is Z-Wave JS UI so incredibly confusing to use?
Zwavejsui is literally zwavejs + a UI
There is functionally no real difference beyond the ui
Your ”dead device” issues are likely related to poor network. Identify any device with poor connectivity and do you have mostly battery devices or AC?
I have four wired devices. Three are Inovelli Red Series dimmers, and one is a dimmer outlet. The rest sadly after that are all battery (two UltraLoq Locks, a security keypad, and a Schlang contact sensor). I’ve been migrating from Hubitat, where I had some issues with the switches, but not nearly so many problems until today.
I see you must use Z-Wave JS UI or Z-Wave JS. I’ve tried going the Z-Wave JS UI route, then using the default integration for Z-wave to contact the Z-Wave JS UI server (running on the same device) and go from there. However, my Z-Wave JS UI server seems to be unreachable, even if I can get to it through the add-on just fine.
Double check you have the right components set up and running. For Z-Wave to work correctly:
- The Integration “Z-Wave” must be running (Settings → Devices & Services → Integrations)
- One and only one of the Add-on’s must be running, either “Z-Wave JS” or “Z-Wave JS UI” (Settings → Add-ons)
I finally have that figured out. The issue with Z-Wave JS UI was that the hostname it picks isn’t the IP I was assuming it was. I now have it integrated just as I had the old Z-Wave JS integration that seemed to be the default.
Sadly…nothing is any better! I’ve spent the entire day trying over and over. Going so far as to reset my Z-wave adapter TWICE, wiping the network clean, resetting devices. It still comes down to the same thing. I can maybe get all but 3 devices at a time to pair properly, but then one of the ones that was working will mysteriously go dead. I’m not dealing with a huge number of devices, 10 at most. My Zwave adapter is listed as “Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller”. I’m not certain, but isn’t that one of the newer ones out there? Why am I having so much trouble?
Check tx/rx for each device and the controller for obvious issues. You can see this in zwavejsui
If controller is plugged in directly to host, maybe add usb extension. Also make sure it is properly powered. If USB it probably is but if host has power issue it’ll be effected so check host powerless as well
The solution was both more complex and simpler than I expected it seems.
I checked the firmware on my USB Z Wave device. Though I purchased it in March and I swear I had put firmware updates on it, it had not one but two available…both from March. It was tricky finding where in Simplicity Studio to apply the updates, but I did, also wiping the stick. Did yet another factory reset of all my Z-wave devices and tried once more. That seems to have done the trick. Root cause: bad outdated Z-wave USB Controller firmware. groan