OK, may have found a fix. While on v16.0.1, go into: ZWAVE JS UI >> Settings >> ZWave.
And disable “Soft Reset” before you upgrade. All seems normal now!
So that basically seems like you have to do that BEFORE you’ve already run into a problem, right? Since this bug crashes ZWAVE JS UI and makes it impossible to change settings.
No, you can still configure it. If you do encounter the add-on restarting for some reason, then just unplug your USB stick and it will fail on startup. In that case at least you can still configure it afterwards.
Of course, if you do it prior to upgrading it’s easier.
What’s frustrating is that in the past I’ve set this up. I knew how to ID which USB device I was using so I could configure ZWave to use that ZWave device - all that stuff. But that’s been half a year and I’m dealing with having to set up a server and two new systems, including one to control a CNC and other devices, so this is really a bad time for failure. It’s been down about a week now and I’m realizing what a serious inconvenience it is and how much we’ve counted on Home Assistant. (And it’s got me thinking maybe I should find a commercial program. I’m in my 60s and hope to be around for a good while, but if Home Assistant can be this unreliable, what would happen if I were incapacitated or dead and my wife were stuck in this house with all these things no longer working?)
It appears ZWAVE JS isn’t working because ZWave isn’t working - which makes me think @smithkt might be right and the USB port might have changed - but I don’t even remember how to check the USB IDs on HA. (On standard Linux, I’d use lsusb to get the info.) So I don’t remember how to check it out, get the proper ID for the device, or how to specify the device. I can’t get to anything in the web UI that lets me do that.
Yeah, well, it was busted and wouldn’t start before the upgrade. I don’t have anything doing auto-upgrades, so I don’t know why it broke, but just one evening, poof no ZWave. I really was hoping the upgrade would fix it.
Settings>system>hardware
Click all hardware.
That will give you a list of everything.
Hmmmm…Okay, found my device as ttyUSB1, but I thought the number given in the error would be the UUID for that device. It’s not. I was thinking maybe my Z-Stick just died, but I think if that were the case, it wouldn’t show up in the hardware. I’m thinking about the “Name has no useable address” part of the error message. It did have one and now it doesn’t. So I’m wondering if something happened with the configuration.
Since I made this thread about the ZWAVE JS UI, and it now looks more like it’s not the UI, but the ZWave setup, I started a 2nd thread with some more direct questions.
The zwave-js ui still loads? If so, go to the settings on the left side. scroll down to zwave. there should be a drop down that lets you select the port.
No.
I’m figuring it’s not the JS end of things, since it looks like it’s ZWave itself. ZWave JS seems like it won’t load without the ZWave integration working properly.
That’s backwards. The integration is dependent on ZUI in this case.
Now I’m remembering that there was something odd - I remember having th change things around somehow in the Z-Wave at one point. Something like that MQTT was included or excluded or something odd like that.
There’s also an option under ZWave->Configure to turn on the ZWave Supervisor. Is that supposed to be on or off?
You’re using Z-Wave JS UI, so that option should be already off.
It is off - but since something’s gone wrong, I’m making sure it should be off - that it didn’t somehow get changed.
From what you’re saying, I take it that it should be off?
It is required to be off if you want to use ZUI.
And isn’t ZUI the standard at this point? or does it matter if I use ZUI or the Supervisor?
Your problem is currently in Z-Wave JS UI. It helps to understand how the pieces interact, here’s the diagram from the integration docs:
The boxes are different components. The Z-Wave integration is connecting to the Z-Wave JS Server over a TCP connection (websocket). Your error indicates that the integration (HA) cannot connect to the server which is provided by Z-Wave JS UI. ZUI is listening for client connections (which is HA), not the other way around. Which means the fault is currently in Z-Wave JS UI. HA won’t work until you correct that component. Usually this means the add-on cannot connect to the USB stick or it’s failing to startup.
No, ZUI is provided as a “community” add-on. They are not official add-ons, but maintained separately. The “community” designation is pretty weak though.
I recommend keeping ZUI, it has many more features and debugging capabilities than the official add-on.
I’m getting multiple updates right now - each time I do one or two updates, I get more. I’m guessing, since I had not had time to look at HA for a while, that it’s catching up. So I’ll get all those installed (since they include ZWave and ZWave JS) and see if that helps.
I was using ZUI. I checked my other HA instance to see what’s running there. (I have one in the house and one in the barn.)
Thank you for the background accompanying your diagram to help me understand just what’s going on. From what I see, there are two ZWave JS add-ons I can use, one with the “UI” added and one without? So you’re using the one with the UI and it looks like that’s the one I’ve been using, too. (Some of this sounds familiar, but once I got my system set up and working, I had to move on to other things and it’s been at least 6 months since then, so I’ve forgotten the details.)
Yes, there are two add-ons, but you can also run outside of add-ons, e.g. external Docker containers, Ubuntu Snap, bare-metal binary, etc… For add-ons, I always recommend Z-Wave JS UI since it has more features and it’s easier to troubleshoot. Either add-on provides the same exact functionality to HA itself.
Just did the ZWave JS UI update. Whenever I get to that update, I get this:
By “This,” I mean the “Entity not found.” I see that before I click to install the update, then afterwards. It’s been like that for months, but it’s kept working. I’m not sure what is not found. Anyway, thought I should point that out. Now that it’s updated, this evening I can do more with troubleshooting.
I have both ZWave JS UI and ZWave JS installed. The latter, the one you’re not recommending and, I think the one I was not using, does have an entry in the sidebar, so, after not using it for a long time, I forgot that’s not what I want to be using. That’s the one I had been trying to start. (It’s really confusing, if you’re not close to the situation, to have two add-ons with such similar names!) So can I delete the ZWave JS addon without a problem? I would think getting it out of the way would help. (Also, any way to get ZWave JS UI up as an entry on the sidebar instead?)
ZWave JS UI is working now. One device shows as dead. It’s charging and may be out of range. However, the ZWave integration is not working. I get this from the integration:
And if I click on Configure, I get this - now different, without a host listed:
And here’s the ZWave JS UI logs:
2023-10-04 17:46:48.199 INFO Z-WAVE: [Node 005] Value added 5-112-0-19 => 2
2023-10-04 17:46:48.200 INFO Z-WAVE: [Node 005] Value added 5-112-0-20 => 0
2023-10-04 17:46:48.201 INFO Z-WAVE: [Node 005] Value added 5-112-0-23 => 8287
2023-10-04 17:46:48.202 INFO Z-WAVE: [Node 005] Value added 5-112-0-24 => 0
2023-10-04 17:46:48.202 INFO Z-WAVE: [Node 005] Value added 5-112-0-26 => 20
2023-10-04 17:46:48.203 INFO Z-WAVE: [Node 005] Value added 5-112-0-33 => 90
2023-10-04 17:46:48.204 INFO Z-WAVE: [Node 005] Value added 5-112-0-34 => 60
2023-10-04 17:46:48.204 INFO Z-WAVE: [Node 005] Value added 5-112-0-38 => 0
2023-10-04 17:46:48.205 INFO Z-WAVE: [Node 005] Value added 5-112-0-39 => 0
2023-10-04 17:46:48.206 INFO Z-WAVE: [Node 005] Value added 5-112-0-40 => 2
2023-10-04 17:46:48.207 INFO Z-WAVE: [Node 005] Value added 5-112-0-41 => 62
2023-10-04 17:46:48.209 INFO Z-WAVE: [Node 005] Value added 5-112-0-42 => 80
2023-10-04 17:46:48.210 INFO Z-WAVE: [Node 005] Value added 5-112-0-43 => 0
2023-10-04 17:46:48.211 INFO Z-WAVE: [Node 005] Value added 5-112-0-46 => 68
2023-10-04 17:46:48.212 INFO Z-WAVE: [Node 005] Value added 5-112-0-48 => 0
2023-10-04 17:46:48.213 INFO Z-WAVE: [Node 005] Value added 5-112-0-49 => 0
2023-10-04 17:46:48.214 INFO Z-WAVE: [Node 005] Value added 5-112-0-52 => 23312
2023-10-04 17:46:48.214 INFO Z-WAVE: [Node 005] Value added 5-112-0-54 => 3454
2023-10-04 17:46:48.215 INFO Z-WAVE: [Node 005] Value added 5-112-0-55 => 11038
2023-10-04 17:46:48.216 INFO Z-WAVE: [Node 005] Value added 5-112-0-61 => 0
2023-10-04 17:46:48.217 INFO Z-WAVE: [Node 005] Value added 5-112-0-62 => 0
2023-10-04 17:46:48.218 INFO Z-WAVE: [Node 005] Value added 5-114-0-manufacturerId => 335
2023-10-04 17:46:48.219 INFO Z-WAVE: [Node 005] Value added 5-114-0-productType => 21570
2023-10-04 17:46:48.220 INFO Z-WAVE: [Node 005] Value added 5-114-0-productId => 21558
2023-10-04 17:46:48.222 INFO Z-WAVE: [Node 005] Value added 5-128-0-level => 100
2023-10-04 17:46:48.224 INFO Z-WAVE: [Node 005] Value added 5-128-0-isLow => false
2023-10-04 17:46:48.225 INFO Z-WAVE: [Node 005] Value added 5-134-0-libraryType => 6
2023-10-04 17:46:48.226 INFO Z-WAVE: [Node 005] Value added 5-134-0-protocolVersion => 4.5
2023-10-04 17:46:48.227 INFO Z-WAVE: [Node 005] Value added 5-134-0-firmwareVersions => 1.0,2.16
2023-10-04 17:46:48.229 INFO Z-WAVE: [Node 005] Value added 5-134-0-hardwareVersion => 1
2023-10-04 17:46:48.246 INFO Z-WAVE: [Node 005] Ready: Nortek Security & Control LLC - GoControl GC-TBZ48 (Z-Wave Plus Thermostat)
2023-10-04T21:46:48.247Z CNTRLR Retrieving priority route to node 5…
2023-10-04T21:46:48.251Z CNTRLR [Node 005] The node is ready to be used
2023-10-04T21:46:48.253Z CNTRLR « [Node 005] ping successful
2023-10-04 17:46:48.493 INFO Z-WAVE: [Node 011] Is alive
2023-10-04T21:46:48.496Z CNTRLR [Node 011] The node is alive.
2023-10-04 17:46:48.513 INFO Z-WAVE: [Node 011] Value added 11-37-0-currentValue => true
2023-10-04 17:46:48.514 INFO Z-WAVE: [Node 011] Value added 11-37-0-targetValue => true
2023-10-04 17:46:48.516 INFO Z-WAVE: [Node 011] Value added 11-113-0-System-Hardware status => 0
2023-10-04 17:46:48.517 INFO Z-WAVE: [Node 011] Value added 11-113-0-alarmType => undefined
2023-10-04 17:46:48.519 INFO Z-WAVE: [Node 011] Value added 11-113-0-alarmLevel => undefined
2023-10-04 17:46:48.520 INFO Z-WAVE: [Node 011] Value added 11-114-0-manufacturerId => 371
2023-10-04 17:46:48.521 INFO Z-WAVE: [Node 011] Value added 11-114-0-productType => 3
2023-10-04 17:46:48.523 INFO Z-WAVE: [Node 011] Value added 11-114-0-productId => 2
2023-10-04 17:46:48.524 INFO Z-WAVE: [Node 011] Value added 11-134-0-libraryType => 3
2023-10-04 17:46:48.525 INFO Z-WAVE: [Node 011] Value added 11-134-0-protocolVersion => 4.24
2023-10-04 17:46:48.526 INFO Z-WAVE: [Node 011] Value added 11-134-0-firmwareVersions => 2.9
2023-10-04 17:46:48.527 INFO Z-WAVE: [Node 011] Value added 11-134-0-hardwareVersion => 255
2023-10-04 17:46:48.529 INFO Z-WAVE: [Node 011] Ready: Leak Intelligence, LLC - LGZW (Water Valve Control)
2023-10-04T21:46:48.530Z CNTRLR Retrieving priority route to node 11…
2023-10-04T21:46:48.534Z CNTRLR [Node 011] The node is ready to be used
2023-10-04T21:46:48.537Z CNTRLR « [Node 011] ping successful
2023-10-04 17:46:48.601 INFO Z-WAVE: [Node 006] Is alive
2023-10-04T21:46:48.602Z CNTRLR [Node 006] The node is alive.
2023-10-04 17:46:48.611 INFO Z-WAVE: [Node 006] Value added 6-114-0-manufacturerId => 59
2023-10-04 17:46:48.613 INFO Z-WAVE: [Node 006] Value added 6-114-0-productType => 1
2023-10-04 17:46:48.614 INFO Z-WAVE: [Node 006] Value added 6-114-0-productId => 1129
2023-10-04 17:46:48.617 INFO Z-WAVE: [Node 006] Ready: Allegion - BE469ZP (Touchscreen Deadbolt Z-Wave Plus)
2023-10-04T21:46:48.619Z CNTRLR Retrieving priority route to node 6…
2023-10-04T21:46:48.622Z CNTRLR [Node 006] The node is ready to be used
2023-10-04T21:46:48.624Z CNTRLR « [Node 006] ping successful
2023-10-04 17:46:48.760 INFO Z-WAVE: Next update scheduled for: Thu Oct 05 2023 00:00:00 GMT-0400 (Eastern Daylight Time)
2023-10-04T21:46:52.029Z CNTRLR [Node 008] The node did not respond after 1 attempts, it is presumed dead
2023-10-04 17:46:52.032 INFO Z-WAVE: [Node 008] Is dead
2023-10-04T21:46:52.034Z CNTRLR [Node 008] The node is dead.
2023-10-04T21:46:52.038Z CNTRLR [Node 008] ping failed: The node did not acknowledge the command (ZW0204)
2023-10-04T21:46:55.466Z CNTRLR [Node 010] The node did not respond after 1 attempts, it is presumed dead
2023-10-04 17:46:55.470 INFO Z-WAVE: [Node 010] Is dead
2023-10-04T21:46:55.472Z CNTRLR [Node 010] The node is dead.
2023-10-04T21:46:55.476Z CNTRLR [Node 010] ping failed: The node did not acknowledge the command (ZW0204)
[17:46:57] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023-10-04 17:47:05.627 INFO APP: GET /health/zwave 301 13.940 ms - 191
2023-10-04T21:47:19.493Z CNTRLR [Node 017] The node did not respond after 1 attempts, it is presumed dead
2023-10-04 17:47:19.495 INFO Z-WAVE: [Node 017] Is dead
2023-10-04T21:47:19.497Z CNTRLR [Node 017] The node is dead.
2023-10-04T21:47:19.497Z CNTRLR All nodes are ready to be used
2023-10-04 17:47:19.498 INFO Z-WAVE: Controller status: Scan completed
2023-10-04 17:47:19.499 INFO Z-WAVE: Network scan complete. Found: 12 nodes
2023-10-04T21:47:19.513Z CNTRLR [Node 017] ping failed: The node did not acknowledge the command (ZW0204)
2023-10-04T21:47:19.514Z CNTRLR » [Node 017] querying node info…
2023-10-04T21:47:19.516Z CNTRLR » [Node 017] pinging the node…
2023-10-04T21:47:20.350Z DRIVER unexpected response, discarding…
2023-10-04T21:47:46.010Z CNTRLR [Node 017] The node did not respond after 1 attempts, it is presumed dead
2023-10-04T21:47:46.014Z CNTRLR [Node 017] ping failed: The node did not acknowledge the command (ZW0204)
2023-10-04T21:47:46.020Z CNTRLR [Node 017] Interview attempt (1/5) failed, node is dead.
2023-10-04 17:47:46.021 ERROR Z-WAVE: [Node 017] Interview FAILED: The node is dead
2023-10-04 17:47:52.764 INFO APP: GET /health/zwave 301 4.213 ms - 191
2023-10-04 17:48:22.949 INFO APP: GET /health/zwave 301 2.449 ms - 191
2023-10-04 17:48:53.134 INFO APP: GET /health/zwave 301 2.220 ms - 191
2023-10-04 17:49:23.299 INFO APP: GET /health/zwave 301 3.457 ms - 191
2023-10-04 17:49:53.468 INFO APP: GET /health/zwave 301 3.443 ms - 191
2023-10-04 17:50:23.651 INFO APP: GET /health/zwave 301 3.211 ms - 191
2023-10-04 17:50:53.825 INFO APP: GET /health/zwave 301 4.748 ms - 191
2023-10-04 17:51:23.998 INFO APP: GET /health/zwave 301 2.819 ms - 191
2023-10-04 17:51:54.183 INFO APP: GET /health/zwave 301 2.043 ms - 191
2023-10-04 17:52:24.364 INFO APP: GET /health/zwave 301 2.275 ms - 191
2023-10-04 17:52:54.525 INFO APP: GET /health/zwave 301 2.072 ms - 191