Unable to connect to ws server

Hi, I am running HA on a raspberry Pi 3 using a usb zwave stick (aeon 7 gen, firmware 20.2) that works like a charm. Unfortunately I am not able to connect the ws server and I cannot see the zwave devices as HA entitites. I do not know the architecture of HA on a rpi, is it working in a docker sandbox? do I need to configure docker also for the ws server?

What’s “the ws server” to you?

well I suppose the WebSocket HA integration that provides communications between HA and Zwave.

But what are the actual symptoms?
You can access HA, right?
How can you tell the zwave stick “works like a charm” if you cannot see any zwave devices…

If you are using HAOS you need to install one of the add-ons, Z-Wave JS or Z-Wave JS UI. If you are running HA in container, you need to install Z-Wave JS UI in container. Any of those provide the Z-Wave driver and the websocket server, HA itself does not.

https://www.home-assistant.io/integrations/zwave_js/#running-z-wave-js-server

For an add-on install, follow the instructions in the add-on docs.

For a container install of ZUI, follow its installation instructions:

  1. https://zwave-js.github.io/zwave-js-ui/#/getting-started/docker?id=installation
  2. https://zwave-js.github.io/zwave-js-ui/#/getting-started/quick-start?id=minimum-settings
  3. https://zwave-js.github.io/zwave-js-ui/#/homeassistant/homeassistant-official
3 Likes

I can see and interact with the devices but I cannot see them as HA entities

I am running HAOS on a raspberry pi 3. ZUI is installed, and I can see the devices through its interface. The problem arises in the lack of integration with HA. How can I have proof of the ws running? how can I test the communication between ZUI and ws server?

Seems you skipped the installation instructions?

https://github.com/hassio-addons/addon-zwave-js-ui/blob/0e18f6aed798ba395e7420660a970955ea8c8d85/zwave-js-ui/DOCS.md#setting-up-the-home-assistant-z-wave-js-integration

Now it is time to set up Home Assistant:

I have tried several times to follow these steps, but as the post title says it is “unable to connect”. What am I missing?

It means the add-on is not running (e.g. there is an error), or the z-wave driver has failed (error) or default settings related to Websocket server were changed.

Thanks. How can I debug/fix this?

Check the logs in the add-on logs tab for any startup errors.

Check the driver logs in ZUI for any errors: https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

Undo any changes made to websocket server settings, the default ones are set for use with HA.

ZUI log

e[90m2024-03-12 16:36:50.050e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:36:50.054e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:36:50.058e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 0 => 8
2024-03-12T15:36:50.150Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:36:50.153e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 255
2024-03-12T15:36:50.160Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:36:50.164e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 255
e[90m2024-03-12 16:36:50.327e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.398 ms - 191e[0m
e[90m2024-03-12 16:36:51.647e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 004] Metadata updated: 49-0-Illuminance
e[90m2024-03-12 16:36:51.651e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 004] Value updated: 49-0-Illuminance 3 => 2
e[90m2024-03-12 16:37:20.472e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.215 ms - 191e[0m
e[90m2024-03-12 16:37:28.604e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:37:28.608e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:37:28.612e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 8 => 0
2024-03-12T15:37:28.704Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:37:28.707e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 0
2024-03-12T15:37:28.715Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:37:28.717e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 0
e[90m2024-03-12 16:37:50.617e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.356 ms - 191e[0m
e[90m2024-03-12 16:37:53.301e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:37:53.305e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:37:53.309e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 0 => 8
2024-03-12T15:37:53.402Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:37:53.406e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 255
2024-03-12T15:37:53.413Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:37:53.415e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 255
e[90m2024-03-12 16:38:20.762e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.490 ms - 191e[0m
e[90m2024-03-12 16:38:50.912e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.417 ms - 191e[0m
e[90m2024-03-12 16:39:21.070e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.402 ms - 191e[0m
e[90m2024-03-12 16:39:40.282e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:39:40.286e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:39:40.290e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 8 => 0
2024-03-12T15:39:40.383Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:39:40.386e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 0
2024-03-12T15:39:40.395Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:39:40.397e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 0
e[90m2024-03-12 16:39:51.218e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.362 ms - 191e[0m
e[90m2024-03-12 16:40:21.411e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.291 ms - 191e[0m
e[90m2024-03-12 16:40:51.572e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.407 ms - 191e[0m
e[90m2024-03-12 16:41:08.133e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:41:08.137e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:41:08.141e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 0 => 8
2024-03-12T15:41:08.232Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:41:08.235e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 255
2024-03-12T15:41:08.242Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:41:08.244e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 255
e[90m2024-03-12 16:41:21.740e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.384 ms - 191e[0m
e[90m2024-03-12 16:41:49.221e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:41:49.226e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:41:49.232e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 113-0-Home Security-Motion sensor status 0 => 8
2024-03-12T15:41:49.334Z CNTRLR [Node 005] treating BasicCC::Set as a report
e[90m2024-03-12 16:41:49.338e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 32-0-currentValue 0 => 255
2024-03-12T15:41:49.365Z CNTRLR [Node 005] treating BasicCC::Set as a report
e[90m2024-03-12 16:41:49.368e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 32-0-currentValue 255 => 255
e[90m2024-03-12 16:41:51.886e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.421 ms - 191e[0m
e[90m2024-03-12 16:42:17.912e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:42:17.920e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:42:17.924e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 8 => 0
2024-03-12T15:42:18.013Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:42:18.016e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 0
2024-03-12T15:42:18.023Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:42:18.025e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 0
e[90m2024-03-12 16:42:22.028e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.273 ms - 191e[0m
e[90m2024-03-12 16:42:50.125e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:42:50.131e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:42:50.134e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 113-0-Home Security-Motion sensor status 8 => 0
2024-03-12T15:42:50.240Z CNTRLR [Node 005] treating BasicCC::Set as a report
e[90m2024-03-12 16:42:50.243e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 32-0-currentValue 255 => 0
2024-03-12T15:42:50.271Z CNTRLR [Node 005] treating BasicCC::Set as a report
e[90m2024-03-12 16:42:50.274e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 005] Value updated: 32-0-currentValue 0 => 0
e[90m2024-03-12 16:42:52.173e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.212 ms - 191e[0m
e[90m2024-03-12 16:43:22.316e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.341 ms - 191e[0m
e[90m2024-03-12 16:43:52.487e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.282 ms - 191e[0m
e[90m2024-03-12 16:44:13.348e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:44:13.353e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:44:13.357e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 0 => 8
2024-03-12T15:44:13.449Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:44:13.452e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 255
2024-03-12T15:44:13.459Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:44:13.461e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 255
e[90m2024-03-12 16:44:22.632e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.333 ms - 191e[0m
e[90m2024-03-12 16:44:52.812e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.219 ms - 191e[0m
e[90m2024-03-12 16:45:22.958e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.994 ms - 191e[0m
e[90m2024-03-12 16:45:53.103e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.461 ms - 191e[0m
e[90m2024-03-12 16:46:23.249e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.162 ms - 191e[0m
e[90m2024-03-12 16:46:32.249e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:46:32.253e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:46:32.258e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 8 => 0
2024-03-12T15:46:32.349Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:46:32.351e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 0
2024-03-12T15:46:32.358Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:46:32.360e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 0
e[90m2024-03-12 16:46:53.403e[39m e[32mINFOe[39m e[1mAPPe[22m: e[0mGET /health/zwave e[36m301e[0m 2.887 ms - 191e[0m
e[90m2024-03-12 16:46:56.535e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmType 0 => 0
e[90m2024-03-12 16:46:56.540e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-alarmLevel 0 => 0
e[90m2024-03-12 16:46:56.543e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 113-0-Home Security-Motion sensor status 0 => 8
2024-03-12T15:46:56.636Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:46:56.639e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 0 => 255
2024-03-12T15:46:56.646Z CNTRLR [Node 006] treating BasicCC::Set as a report
e[90m2024-03-12 16:46:56.648e[39m e[32mINFOe[39m e[1mZ-WAVEe[22m: [Node 006] Value updated: 32-0-currentValue 255 => 255

Those aren’t driver logs, but it does appear ZUI is working OK. That would leave a problem with the WS server configuration in ZUI. Did you change something?


I didn’t.

Yeah, you did. Server Host. Should be blank.

I am removing it promptly.


well, it seems you are a wizard…

is there any further step to do?

Nope, that’s it.

1 Like