I setup ZwaveJSUI and added my devices. Now Im trying to setup ZwaveJS to import devices to HA. I add ZwaveJS integration and unselect install supervisor and then get the websocket screen. No matter what I type no connection. I am running Home Assistant on a Yellow device. As far as i understand its HAOS not in docker or anything. I SSH to the yellow, tried docker ps just to make sure it says docker command not found. So as i understand it should be running locally. Please help I’m going nuts.
Did you install it as the standard Add-on under HAOS on your HA Yellow?
If the answer is yes, the Z-wave Integration should have this WebSocket connection:
Note that I mean exactly the same
Using what SSH server? What port? If you are ssh-ing to port 22 (SSH Default) then you are likely connecting to the Advanced SSH add-on, and not the Yellow HAOS. You have to enable SSH on port 22222 to get to the underlying OS, it is not enabled by default.
If you truly get to the OS then the docker ps command will work as Home Assistant itself runs as a docker container.
Example:
PS C:\Users\marti> ssh -p 22222 root@hass-prod
Welcome to Home Assistant OS.
Use `ha` to access the Home Assistant CLI.
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c0c6f7e717cc 3f6f8ac8/amd64-addon-smartbed-mqtt:1.1.22 "/smartbed-mqtt/run.…" 8 hours ago Up 8 hours addon_3f6f8ac8_smartbed-mqtt
8443345c4a3f ghcr.io/esphome/esphome-hassio:2025.4.0 "/init" 8 hours ago Up 8 hours addon_5c53de3b_esphome
d70e89779e1b ghcr.io/hassio-addons/vscode/amd64:5.19.1 "/init" 8 hours ago Up 8 hours (healthy) addon_a0d7b954_vscode
8a00cb34e774 ghcr.io/home-assistant/amd64-hassio-cli:2025.04.0 "/init" 4 days ago Up 4 days hassio_cli
f501290b9c95 ghcr.io/hassio-addons/zwave-js-ui/amd64:3.22.0 "/init" 4 days ago Up 4 days (healthy) 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp addon_a0d7b954_zwavejs2mqtt
4cfefad1955f ghcr.io/home-assistant/qemux86-64-homeassistant:2025.4.2 "/init" 4 days ago Up 8 hours homeassistant
c463a146604c ghcr.io/home-assistant/amd64-hassio-supervisor:latest "/init" 7 days ago Up 7 days hassio_supervisor
aa9c317a0149 brainicism/bgutil-ytdlp-pot-provider:0.8.2 "node build/main.js" 8 days ago Up 8 days 0.0.0.0:4416->4416/tcp, :::4416->4416/tcp addon_d5369777_ytm_po_token_generator
9e93b97d4cef ghcr.io/home-assistant/amd64-hassio-observer:2025.02.0 "/usr/bin/observer" 3 weeks ago Up 3 weeks 0.0.0.0:4357->80/tcp, [::]:4357->80/tcp hassio_observer
062ce072b5bc ghcr.io/home-assistant/amd64-hassio-multicast:2025.02.0 "/init" 3 weeks ago Up 3 weeks hassio_multicast
949cd457841a ghcr.io/home-assistant/amd64-hassio-audio:2025.02.0 "/init" 3 weeks ago Up 3 weeks hassio_audio
2b046420ecae homeassistant/amd64-addon-nginx_proxy:3.11.1 "/init" 6 weeks ago Up 6 weeks 0.0.0.0:443->443/tcp, :::443->443/tcp addon_core_nginx_proxy
30ea030ec3c9 ghcr.io/home-assistant/amd64-hassio-dns:2025.02.0 "/init" 6 weeks ago Up 6 weeks hassio_dns
5d8699d580c4 homeassistant/amd64-addon-whisper:2.4.0 "/init" 2 months ago Up 2 months (healthy) addon_core_whisper
c0c4cfabcb8f homeassistant/amd64-addon-piper:1.5.2 "/init" 2 months ago Up 2 months (healthy) addon_core_piper
19f2798e3138 homeassistant/amd64-addon-openwakeword:1.10.0 "/init" 2 months ago Up 2 months (healthy) addon_core_openwakeword
#
Holy Jesus. I had found that answer and even tried that and still got no connection. So I went back to the zwavejsui settings for home assistant and put it in the server host line just hoping and this time it worked! I had tried my own server name and ip address I didnt think to try a0d7b954-zwavejs2mqtt. Since it originally, I think, said optional. Thank you for the help.
You’re not supposed to change the ZUI Websocket server settings, it’s supposed to be blank.