I’ve installed Z-Wave JS UI and I’m using the client from that (verses the client from Z-Wave JS Integration). I’m able to include and exclude my devices fine, but they don’t show up in HA. I’ve also enabled this:
Create devices in Home Assistant using MQTT discovery. This is an alternative to Home Assistant Z-Wave JS integration
I’m not certain what I’m doing wrong here.
Hardware is HA yellow with CM5 and Zooz 800LR GPIO board installed.
Enable Z-Wave JS websocket server. This can be used with Home Assistant Z-Wave JS integration to discover entities
Did you add zwave integration to connect zwavejsui to ha in HA?
When I try to add this, it comes back saying “failed to connect” but in the terminal window I can see that port 3000 is being listened to (netstat -tpln).
Settings → Device & services → Integrations → Z-Wave
I unchecked the box for “Use the Z-Wave Supervisor add-on” and used the default URL of ws://localhost:3000
By using what’s called the rpiboot method. Since the CM5 doesn’t support USB boot devices, I essentially turn the HA yellow into a USB device and upload the image that way.
How did you install zwavejsui?
From Settings → Add-ons
Localhost may be wrong? depends
I tried ws://127.0.0.1:3000, which is the equivalent, and that didn’t work either.
The documentation indicates that the prefered agent is zwavejs and not zwavejsui. Installing zwavejs means I have to disable the client in the UI. When I do that, the UI no longer functions (the dashboard is empty, and attempts at inclusion reports “client is not running”.
At least zwavejs gets the device into HA, so I’ve removed the UI for now.
Not sure what you mean by “agent” or “client”, neither of those are common terms in the context of Z-Wave. Both add-ons are servers, they provide the zwave-js-server Websocket server which the integration talks to (if want to to mention a client, the client is HA and the Z-Wave integration). The ZUI add-on provides a separate Web GUI in addition to the websocket server.
You can only run one of the add-ons at the same time. Running both will conflict with each other.
If the ZUI add-on URL didn’t work, then you may have changed some of the settings you weren’t supposed to. A common error is to change the Websocker server hostname. You don’t need to make any changes to the ZUI settings except the serial port and security keys. Although I do also recommend permanently turning on driver debug logging for troubleshooting, but you may want to skip this if your HAOS is installed on an SD card (logs would be write heavy depending on the activity).
I tried your suggestion and removed both zwavejs and zwavejsui and restarted HA. I confirmed that they were removed. I installed zwavejsui and configured it for the correct USB port and assigned the security numbers. The previous devices showed up in the zwavejsui dashboard, but when I looked for them in HA, they were not to be found.
Z-Wave JS and Z-Wave JS UI are add-ons. In this case you can only run one of the add-ons as they require exclusive use of the USB stick. They provide the same functionality (z-wave js server) to HA though.
Next is the Z-Wave integration that connects to either of the add-ons.