Z-wave JS not working after upgrading from 2022.12.8 to 2023.X (tried several versions)

Configuration Z-Wave
1

My Z-wave integration fails when upgrading core from 2022.12.8 to various 2023 versions, including the latest/current 2023.09.2. I have a “Aeotec z-stick gen5”, and zwave-js-ui: 8.25.1 + zwave-js: 11.14.2

Today I upgraded to the latest Z-wave UI and core 2023.9.2 - but still the same issue. I have tried various versions of core, and disabling “soft reset” etc but not sure how to proceed?
Reverting back solves my issue, but then I loose some other features. Is there any more information I can provide? Anyone that can give me some hints on what to test next? Thanks in advance :slight_smile:

The logs are from a few days bac - before my last update.

zwave-js-ui: 8.26.0
zwave-js: 11.14.3
home id: 4121890287
home hex: 0xf5af0def

Home Assistant 2023.9.2
Supervisor 2023.09.2
Operating System 10.5
Frontend 20230911.0 - latest

I get the message:

Z-Wave JS: Failed setup, will retry
Failed to connect: ws://a0d7b954-zwavejs2mqtt:3000

Aeotec Z-stick Gen5

Driver Version:
11.14.2
Server Version:
1.31.0
Home ID:
4121890287
Server URL:
ws://a0d7b954-zwavejs2mqtt:3000

Working version of Core:

Home Assistant 2022.12.8
Supervisor 2023.09.2
Operating System 10.5
Frontend 20221213.1 - latest

2023-09-16 22:56:53.185 INFO (MainThread) [homeassistant.setup] Setup of domain usb took 0.0 seconds
2023-09-16 22:56:53.195 INFO (SyncWorker_6) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant
2023-09-16 22:56:53.197 INFO (SyncWorker_1) [homeassistant.loader] Loaded alexa from homeassistant.components.alexa
2023-09-16 22:56:53.235 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [547868885696] Received unknown command: zwave_js/subscribe_controller_statistics
2023-09-16 22:56:53.251 INFO (SyncWorker_3) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2023-09-16 22:56:53.443 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2023-09-16 22:56:53.475 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.0 seconds
2023-09-16 22:56:53.515 INFO (SyncWorker_5) [homeassistant.loader] Loaded ukraine_alarm from homeassistant.components.ukraine_alarm

2023-09-16 22:57:11.496 INFO (MainThread) [homeassistant.setup] Setting up zwave_js
2023-09-16 22:57:11.497 INFO (MainThread) [homeassistant.setup] Setup of domain zwave_js took 0.0 seconds
2023-09-16 22:57:11.530 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: ws://a0d7b954-zwavejs2mqtt:3000 ; Retrying in background
2023-09-16 22:57:11.547 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 6.1 seconds
2023-09-16 22:57:11.554 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 6.0 seconds
2023-09-16 22:57:12.135 INFO (MainThread) [homeassistant.setup] Setting up hacs
2023-09-16 22:57:12.135 INFO (MainThread) [homeassistant.setup] Setup of domain hacs took 0.0 seconds
2023-09-16 22:57:12.136 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2023-09-16 22:57:12.160 INFO (MainThread) [homeassistant.setup] Setting up met
2023-09-16 22:57:12.160 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.0 seconds
2023-09-16 22:57:12.182 INFO (Thread-2 (_thread_main)) [homeassistant.components.mqtt.client] Connected to MQTT server [xxxxxxxx.duckdns.org:1883](http://xxxxxxxx.duckdns.org:1883/) (0)
2023-09-16 22:57:12.207 INFO (MainThread) [custom_components.hacs]
2

You’ll need to look at the Z-Wave JS UI logs to see what is going on. If the integration cannot connect, more than likely it means there was some error and ZUI has not started the z-wave driver and websocket server.

1 Like
3

thanks - i will have a look later tommorrow

4

again thanks for all feedbacks :slight_smile:

I have looked further into debug logs from from the Z-wave integration (Enabled debug logging), and in ‘Z-Wave JS’ where I enabled ‘silly’ logging to file for both ‘general’ and ‘Z_wave’ - but I cannot find any obvious warnings of interest.

I do not use the Z-wave JS supervisor add-on ?

In other discussion threads I see discussions on which ws: adress to use. Z-Wave integration failed to connect - need some high level direction
I guess I have ws://a0d7b954-zwavejs2mqtt:3000 - as the error message is about this one - but I cannot see where I could change this value?

I should also mention that for debugging this I brought my rasberry plus only a couple of the Z-wave components home from my remote location (a heatit wall controller (NODE 11)+ keyfob (NODE 10)
It looks like the other nodes still are alive - is there some caching that can be reset? (without loosing the node config?)

In the z-ui_2023-09-24.log I see (I have disabled MQTT for now)

2023-09-24 20:22:21.354 WARN BACKUP: Store backup is disabled
2023-09-24 20:22:21.355 WARN BACKUP: Nvm backup is disabled
2023-09-24 20:22:21.352 INFO MQTT: MQTT is disabled
2023-09-24 20:22:21.397 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2023-09-24 20:22:21.400 INFO Z-WAVE: Setting user callbacks
2023-09-24 20:22:21.426 WARN BACKUP: Store backup is disabled
2023-09-24 20:22:21.436 INFO APP: e[0mPOST /api/settings e[32m200e[0m 365.764 ms - 1480e[0m
2023-09-24 20:22:21.428 WARN BACKUP: Nvm backup is disabled
2023-09-24 20:22:21.492 INFO APP: e[0mGET /api/auth-enabled e[36m304e[0m 4.443 ms - -e[0m
2023-09-24 20:22:21.647 INFO APP: e[0mGET /health/zwave e[36m301e[0m 1.561 ms - 191e[0m
2023-09-24 20:22:24.858 INFO Z-WAVE: Z-Wave driver is ready
2023-09-24 20:22:24.860 INFO Z-WAVE: Controller status: Driver ready
2023-09-24 20:22:24.878 DEBUG Z-WAVE: [Node 001] Binding to node events
...

2023-09-24 20:22:24.914 DEBUG Z-WAVE: [Node 011] Has been added to nodes array
2023-09-24 20:22:24.921 INFO Z-WAVE: Scanning network with homeid: 0xf5af0def
2023-09-24 20:22:24.956 INFO Z-WAVE: [Node 001] Is alive
2023-09-24 20:22:24.962 INFO Z-WAVE: Powerlevel is not supported by controller
2023-09-24 20:22:24.963 INFO Z-WAVE: RF region is not supported by controller
2023-09-24 20:22:24.967 INFO Z-WAVE: [Node 001] Ready: AEON Labs - ZW090 (Z‐Stick Gen5 USB Controller)
2023-09-24 20:22:24.986 INFO Z-WAVE: [Node 010] Is asleep
2023-09-24 20:22:25.003 INFO Z-WAVE: [Node 010] Value added 10-91-0-scene-001 => undefined
2023-09-24 20:22:25.005 INFO Z-WAVE: [Node 010] Value added 10-91-0-scene-002 => undefined

2023-09-24 20:22:25.122 INFO Z-WAVE: [Node 011] Value added 11-135-0-80-5 => 0
2023-09-24 20:22:25.123 INFO Z-WAVE: [Node 011] Value added 11-135-0-value => undefined
2023-09-24 20:22:25.125 INFO Z-WAVE: [Node 011] Value added 11-135-0-identify => undefined
2023-09-24 20:22:25.126 INFO Z-WAVE: [Node 011] Value added 11-135-0-timeout => undefined
2023-09-24 20:22:25.134 INFO Z-WAVE: [Node 011] Ready: Heatit - Z-PH WALL CONTROLLER (Z-Push Wall Controller)

...

2023-09-24 20:22:26.146 INFO Z-WAVE: Z-Wave server started
2023-09-24 20:22:27.404 INFO Z-WAVE: Next update scheduled for: Mon Sep 25 2023 00:00:00 GMT+0200 (Central European Summer Time)
2023-09-24 20:22:29.800 INFO Z-WAVE: [Node 009] Is dead
2023-09-24 20:22:29.804 INFO Z-WAVE: Controller status: Scan completed
2023-09-24 20:22:29.805 INFO Z-WAVE: Network scan complete. Found: 8 nodes
2023-09-24 20:22:34.736 DEBUG SOCKET: User disconnected from fOxBjOGxTUYcEDpGAAAH: transport close
2023-09-24 20:22:51.826 INFO APP: e[0mGET /health/zwave e[36m301e[0m 2.670 ms - 191e[0m

In the core log there are some problems with mill integration - which I think are unrelated to this. The mill issues I see others are struggling with as well. I dont include those messages here to avoid false hit by other googling the mill issue Mill · Issue #100045 · home-assistant/core · GitHub

2023-09-24 20:17:20.819 INFO (MainThread) [homeassistant.setup] Setting up zwave_js
2023-09-24 20:17:20.820 INFO (MainThread) [homeassistant.setup] Setup of domain zwave_js took 0.0 seconds
2023-09-24 20:17:21.404 INFO (MainThread) [homeassistant.setup] Setting up renault
2023-09-24 20:17:21.404 INFO (MainThread) [homeassistant.setup] Setup of domain renault took 0.0 seconds
2023-09-24 20:17:21.440 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: ws://a0d7b954-zwavejs2mqtt:3000 ; Retrying in background
2023-09-24 20:17:21.446 INFO (MainThread) [homeassistant.setup] Setting up automation
2023-09-24 20:17:21.448 INFO (MainThread) [homeassistant.setup] Setting up script
2023-09-24 20:17:21.515 INFO (MainThread) [homeassistant.setup] Setting up met
2023-09-24 20:17:21.515 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.0 seconds
2023-09-24 20:17:21.529 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 4.5 seconds
2023-09-24 20:17:21.547 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2023-09-24 20:17:21.547 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 4.3 seconds
2023-09-24 20:17:21.587 INFO (SyncWorker_6) [homeassistant.loader] Loaded switch from homeassistant.components.switch

JS log :

2023-09-24T18:22:21.404Z DRIVER   version 11.14.3
2023-09-24T18:22:21.405Z DRIVER   
2023-09-24T18:22:21.405Z DRIVER   starting driver...
2023-09-24T18:22:21.405Z DRIVER   opening serial port /dev/serial/by-id/usb-0658_0200-if00
2023-09-24T18:22:21.418Z DRIVER   serial port opened
2023-09-24T18:22:21.419Z SERIAL » 0x15                                                                 (1 bytes)
2023-09-24T18:22:22.441Z DRIVER   loading configuration...
2023-09-24T18:22:22.451Z CONFIG   Using external configuration dir /data/db
2023-09-24T18:22:22.452Z CONFIG   version 11.14.3
2023-09-24T18:22:24.006Z DRIVER   beginning interview...
2023-09-24T18:22:24.008Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2023-09-24T18:22:24.009Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2023-09-24T18:22:24.009Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2023-09-24T18:22:24.010Z DRIVER   added request handler for SerialAPIStarted (0x0a)...
                                  1 registered
2023-09-24T18:22:24.010Z CNTRLR   querying Serial API capabilities...

...

2023-09-24T18:22:24.320Z DRIVER « [RES] [GetSerialApiInitData]
                                    payload: 0x05081df1070000000000000000000000000000000000000000000000000000000
                                  500
2023-09-24T18:22:24.325Z CNTRLR   received additional controller information:
                                    Z-Wave API version:         5 (legacy)
                                    Z-Wave chip type:           ZW050x
                                    node type                   Controller
                                    controller role:            primary
                                    controller is the SIS:      true
                                    controller supports timers: false
                                    nodes in the network:       1, 5, 6, 7, 8, 9, 10, 11
2023-09-24T18:22:24.373Z DRIVER   Cache file for homeId 0xf5af0def found, attempting to restore the network from
                                   cache...
2023-09-24T18:22:24.381Z DRIVER   all queues idle
2023-09-24T18:22:24.806Z CNTRLR   [Node 011] Embedded device config loaded
2023-09-24T18:22:24.810Z DRIVER   Restoring the network from cache was successful!
2023-09-24T18:22:24.821Z CNTRLR   setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2023-09-24T18:22:24.824Z DRIVER   all queues busy
2023-09-24T18:22:24.828Z SERIAL » 0x01050006640f97                                                     (7 bytes)
2023-09-24T18:22:24.829Z DRIVER » [REQ] [SetSerialApiTimeouts]
                                    payload: 0x640f
2023-09-24T18:22:24.832Z SERIAL « [ACK]                                                                   (0x06)
2023-09-24T18:22:24.834Z SERIAL « 0x01050106640f96                                                     (7 bytes)
2023-09-24T18:22:24.835Z SERIAL » [ACK]                                                                   (0x06)
2023-09-24T18:22:24.836Z DRIVER « [RES] [SetSerialApiTimeouts]
                                    payload: 0x640f

2023-09-24T18:22:24.839Z CNTRLR   serial API timeouts overwritten. The old values were: ack = 1000 ms, byte = 15
                                  0 ms
2023-09-24T18:22:24.839Z CNTRLR   Interview completed
2023-09-24T18:22:24.840Z DRIVER   Network key for S0 configured, enabling S0 security manager...
2023-09-24T18:22:24.841Z DRIVER   At least one network key for S2 configured, enabling S2 security manager...
2023-09-24T18:22:24.850Z DRIVER   driver ready
2023-09-24T18:22:24.860Z DRIVER   Checking for configuration updates...
2023-09-24T18:22:24.973Z CNTRLR   Interviewing nodes and/or determining their status: 9, 10, 11, 5, 6, 7, 8
2023-09-24T18:22:25.036Z CNTRLR   Retrieving priority route to node 10...
2023-09-24T18:22:25.044Z CNTRLR   [Node 011] The node is asleep.
2023-09-24T18:22:25.135Z CNTRLR   Retrieving priority route to node 11...
2023-09-24T18:22:25.138Z CNTRLR   [Node 011] The node is ready to be used
2023-09-24T18:22:25.215Z CNTRLR   Retrieving priority route to node 5...
2023-09-24T18:22:25.297Z CNTRLR   Retrieving priority route to node 6...
2023-09-24T18:22:25.517Z CNTRLR   Retrieving priority route to node 7...
2023-09-24T18:22:25.614Z CNTRLR   Retrieving priority route to node 8...
2023-09-24T18:22:25.669Z SERIAL » 0x010800130901002501c8                                              (10 bytes)
2023-09-24T18:22:26.233Z SERIAL « [ACK]                                                                   (0x06)
2023-09-24T18:22:26.236Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-09-24T18:22:26.239Z SERIAL » [ACK]                                                                   (0x06)
2023-09-24T18:22:26.243Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-09-24T18:22:27.399Z DRIVER   No configuration update available...
2023-09-24T18:22:29.780Z SERIAL « 0x010700130101019b71                                                 (9 bytes)
2023-09-24T18:22:29.783Z SERIAL » [ACK]                                                                   (0x06)
2023-09-24T18:22:29.792Z DRIVER « [REQ] [SendData]
                                    callback id:     1
                                    transmit status: NoAck
2023-09-24T18:22:29.802Z CNTRLR   All nodes are ready to be used
2023-09-24T18:22:29.812Z SERIAL » 0x010400920a63                                                       (6 bytes)
2023-09-24T18:22:29.813Z DRIVER » [REQ] [GetPriorityRoute]
                                    node ID: 10
2023-09-24T18:22:29.820Z SERIAL « [ACK]                                                                   (0x06)
2023-09-24T18:22:29.822Z SERIAL « 0x010a01920a0100000000036e                                          (12 bytes)
2023-09-24T18:22:29.823Z SERIAL » [ACK]                                                                   (0x06)
2023-09-24T18:22:29.826Z DRIVER « [RES] [GetPriorityRoute]
                                    node ID:     10
                                    route kind:  LWR
                                    repeaters:   none
                                    route speed: 100k
2023-09-24T18:22:29.834Z SERIAL » 0x010400920b62                                                       (6 bytes)
2023-09-24T18:22:29.834Z DRIVER » [REQ] [GetPriorityRoute]
                                    node ID: 11
2023-09-24T18:22:29.839Z SERIAL « [ACK]                                                                   (0x06)
2023-09-24T18:22:29.841Z SERIAL « 0x010a01920b0100000000036f                                          (12 bytes)
2023-09-24T18:22:29.842Z SERIAL » [ACK]                                                                   (0x06)
2023-09-24T18:22:29.843Z DRIVER « [RES] [GetPriorityRoute]
                                    node ID:     11
                                    route kind:  LWR
                                    repeaters:   none
                                    route speed: 100k
2023-09-24T18:22:29.849Z SERIAL » 0x01040092056c                                                       (6 bytes)
2023-09-24T18:22:29.850Z DRIVER » [REQ] [GetPriorityRoute]
                                    node ID: 5
2023-09-24T18:22:29.854Z SERIAL « [ACK]                                                                   (0x06)
5

Did you disable the websocket server in the ZUI configuration? My logs show:

2023-09-22 13:09:43.237 INFO Z-WAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000
2023-09-22 13:09:43.237 INFO Z-WAVE: Z-Wave server started

The first line means the websocket server is listening. You either disabled the server, or did you omit that log line? A disabled server would result in this problem.

6

sorry! - it’s there!

2023-09-25 21:23:08.302 INFO Z-WAVE: [Node 008] Value added 8-134-0-hardwareVersion => 2
2023-09-25 21:23:08.307 INFO Z-WAVE: [Node 008] Ready: Fibargroup - FGSD002 (Smoke Detector)
2023-09-25 21:23:08.623 INFO Z-WAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000
2023-09-25 21:23:08.683 INFO Z-WAVE: Z-Wave server started
2023-09-25 21:23:08.792 INFO APP: GET /health/zwave 301 31.862 ms - 191
2023-09-25 21:23:09.190 INFO Z-WAVE: Next update scheduled for: Tue Sep 26 2023 00:00:00 GMT+0200 (Central European Summer Time)
2023-09-25 21:23:09.747 INFO Z-WAVE-SERVER: DNS Service Discovery enabled
2023-09-25 21:23:12.463 INFO Z-WAVE: [Node 009] Is dead
2023-09-25 21:23:12.468 INFO Z-WAVE: Controller status: Scan completed
2023-09-25 21:23:12.469 INFO Z-WAVE: Network scan complete. Found: 8 nodes
2023-09-25 21:23:38.955 INFO APP: GET /health/zwave 301 1.989 ms - 191
2023-09-25 21:24:09.121 INFO APP: GET /health/zwave 301 1.894 ms - 191
2023-09-25 21:24:39.292 INFO APP: GET /health/zwave 301 1.830 ms - 191
2023-09-25 21:25:09.472 INFO APP: GET /health/zwave 301 1.884 ms - 191
2023-09-25 21:25:39.628 INFO APP: GET /health/zwave 301 2.092 ms - 191
2023-09-25 21:26:09.784 INFO APP: GET /health/zwave 301 1.865 ms - 191
2023-09-25 21:26:39.939 INFO APP: GET /health/zwave 301 2.002 ms - 191
2023-09-25 21:27:32.738 INFO APP: GET /health/zwave 301 1.805 ms - 191
2023-09-25 21:27:52.242 INFO APP: GET / 200 557.733 ms - 1680
2023-09-25 21:27:52.278 INFO APP: GET /assets/index-07fef15a.js 304 5.147 ms - -
2023-09-25 21:27:52.293 INFO APP: GET /registerSW.js 304 2.496 ms - -
2023-09-25 21:27:52.302 INFO APP: GET /assets/index-17c83595.css 304 2.825 ms - -
2023-09-25 21:27:52.493 INFO APP: GET /assets/Login-b849578e.js 304 2.534 ms - -
2023-09-25 21:27:52.503 INFO APP: GET /assets/Login-f3260011.css 304 2.093 ms - -
2023-09-25 21:27:52.521 INFO APP: GET /api/auth-enabled 304 5.404 ms - -
2023-09-25 21:27:52.551 INFO APP: GET /assets/Debug-3f1af365.js 304 1.852 ms - -
2023-09-25 21:27:52.659 INFO APP: GET /logo.svg 304 2.440 ms - -
2023-09-25 21:27:52.774 DEBUG SOCKET: New connection KL8DMjmvINavrtnFAAAb
2023-09-25 21:27:52.801 DEBUG SOCKET: Event INITED emitted to KL8DMjmvINavrtnFAAAb
2023-09-25 21:27:52.837 INFO APP: GET /assets/MaterialIcons-Regular-5743ed3d.woff2 304 51.596 ms - -
2023-09-25 21:27:53.860 INFO APP: GET /favicon.ico 200 1241.905 ms - 923
2023-09-25 21:27:53.884 INFO APP: GET /favicon.ico 304 1.542 ms - -

upgraded to core 2023.9.3 now - no change

7

Are you actually still running the add-on? You didn’t switch to something like the container version?

Well, I’m running out of ideas. I myself cannot produce your error. I tried two situations.

  1. Stop the Z-Wave JS UI add-on, then restart HA. In that case I get the error:
2023-09-25 13:57:36.395 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: Cannot connect to host a0d7b954-zwavejs2mqtt:3000 ssl:default [Name has no usable address]; Retrying in background
  1. Disable the websocket server in ZUI, restart the server. In that cas I get the error:
2023-09-25 13:59:12.685 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: ; Retrying in background

I cannot reproduce the exact error message you are seeing:

2023-09-16 22:57:11.530 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: ws://a0d7b954-zwavejs2mqtt:3000 ; Retrying in background

In this case, the log is reporting an exception, and the message contains the websocket URL. I’m not sure where that error would come from.

You might check the /config/.storage/core.config_entries file and make sure there’s nothing really strange about the config entry. Here’s what mine looks like:

      {
        "entry_id": "0df929823f89cfa8a432a2567bff4018",
        "version": 1,
        "domain": "zwave_js",
        "title": "Z-Wave JS",
        "data": {
          "url": "ws://a0d7b954-zwavejs2mqtt:3000",
          "usb_path": null,
          "s0_legacy_key": null,
          "s2_access_control_key": null,
          "s2_authenticated_key": null,
          "s2_unauthenticated_key": null,
          "use_addon": false,
          "integration_created_addon": false
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "user",
        "unique_id": "4015456725",
        "disabled_by": null
      }

You could also try looking up the hostname from another container, such as either of the Terminal add-ons, and double check that it’s being resolved.

image

8

Thanks for all your efforts @freshcoast :slight_smile:
As far as I can see my nslookup looks OK and so does the config_entry. Maybe I should go back to 2022.12.8 and slowly add on new core versions one by one until it fails. It failed already in april version if I remember correct. (Just need to re-find the instructions on how to do it)

Server:		172.30.32.3
Address:	172.30.32.3#53

Name:	a0d7b954-zwavejs2mqtt.local.hass.io
Address: 172.30.33.0

      {
        "entry_id": "4327bd7269e89dbfac7ce6a9a5b5be6b",
        "version": 1,
        "domain": "zwave_js",
        "title": "Z-Wave JS",
        "data": {
          "url": "ws://a0d7b954-zwavejs2mqtt:3000 ",
          "usb_path": "/dev/serial/by-id/usb-0658_0200-if00",
          "s0_legacy_key": "0x00, 0x06, 0x00, 0x04, 0x01, 0x09, 0x06, 0x05, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01",
          "s2_access_control_key": "E0F19BExxxxxxxxxxxxxxxxxxF6192B",
          "s2_authenticated_key": "E6xxxxxxxxxxxxxxxxxxxxxxxxx3C66EE7F",
          "s2_unauthenticated_key": "3108xxxxxxxxxxxxx3",
          "use_addon": false,
          "integration_created_addon": false
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "usb",
        "unique_id": "4121890287",
        "disabled_by": null
      },
9

I am really suspicious of this extra white-space you have in your settings, which I caught glimpse of in the error message:

   "url": "ws://a0d7b954-zwavejs2mqtt:3000 ",

I would go through the configuration again (do not delete the integration), and re-configure it without the trailing whitespace.

1 Like
10

Oops - I see that one now. Hhmm - wonder how that went into the entry. I’ll try what you suggests

Update: Then we made it! Thanks a lot @freshcoast :smiley:

For others googing how to change the URL:
I went to the
services->Z-wave->3 dots to the right of CONFIGURE -> configure -> SUBMIT (not clicking Use the Z-Wave JS Supervisor option)

or with working config

services->Z-wave-> CONFIGURE -> RE-CONFIGURE SERVER->SUBMIT (not clicking Use the Z-Wave JS Supervisor option)

Then I could remove the mystic trailing white space

1 Like