ZWave JS Install Issue

the.loquitur · May 27, 2023, 5:54am

Hi.

I failed trying to get a Zooz 700 ZST10 USB hub, with 7.18.3 firmware, installed in my bare bones Home Assistant running 2023.5.4. What happened was:

Inserted the ZST10
nothing happened
So I manually installed, adding a device in Devices, selecting Z-Wave and then the Use the Z-Wave Supervisor add-on option, Selected USB Device Path of “ttyS0 - /dev/ttyS0”
This failed to install the Z-Wave JS
The Home Assistant Core Log reads, “Failed to start Z-Wave JS add-on: timeout”
In Add-Ons Z-Wave JS does not exist
In Integrations, a Z-Wave integration does not exist
In Devices, a Z-Wave device does exist
HOWEVER, if I select the Z-Wave JS device, Service Info’s Visit link, it takes me to a Z-Wave JS add-on that previously did not exist.
Afterwards, I check the logs and it reads:

CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-26T06:08:36.998Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2023-05-26T06:08:39.112Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK 
                                  from the controller (ZW0200)
                                      at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Drive
                                  r.ts:4301:23)
                                      at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/contro
                                  ller/Controller.ts:908:33)
                                      at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src
                                  /lib/driver/Driver.ts:1342:26)
                                      at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr
                                  iver.ts:1148:16)
Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4301:23)
    at ZWaveController.identify (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:908:33)
    at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1342:26)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1148:16) (ZW0100)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1165:6)
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 100,
  context: undefined,
  transactionSource: undefined
}
Shutting down
[06:08:39] WARNING: Halt add-on

Finally though, I went back to Integrations, tried to Add Integration and it worked.

When I went back into the logs, they read:

2023-05-26T06:13:42.069Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-05-26T06:13:43.223Z CNTRLR   [Node 004] Timed out while waiting for a response from the node (ZW0201)
2023-05-26T06:13:43.224Z CNTRLR « [Node 004] received no value for parameter #1
2023-05-26T06:13:43.224Z CNTRLR » [Node 004] querying parameter #80 value...
2023-05-26T06:13:43.258Z CNTRLR « [Node 004] parameter #80 has value: 0
2023-05-26T06:13:43.258Z CNTRLR » [Node 004] querying parameter #90 value...
2023-05-26T06:13:43.290Z CNTRLR « [Node 004] parameter #90 has value: 1
2023-05-26T06:13:43.290Z CNTRLR » [Node 004] querying parameter #91 value...
2023-05-26T06:13:43.326Z CNTRLR « [Node 004] parameter #91 has value: 25
2023-05-26T06:13:43.326Z CNTRLR » [Node 004] querying parameter #92 value...
2023-05-26T06:13:43.365Z CNTRLR « [Node 004] parameter #92 has value: 5
2023-05-26T06:13:43.365Z CNTRLR » [Node 004] querying parameter #101 value...
2023-05-26T06:13:43.404Z CNTRLR « [Node 004] parameter #101 has value: 4
2023-05-26T06:13:43.405Z CNTRLR » [Node 004] querying parameter #102 value...
2023-05-26T06:13:43.443Z CNTRLR « [Node 004] parameter #102 has value: 8
2023-05-26T06:13:43.443Z CNTRLR » [Node 004] querying parameter #103 value...
2023-05-26T06:13:43.482Z CNTRLR « [Node 004] parameter #103 has value: 0
2023-05-26T06:13:43.483Z CNTRLR » [Node 004] querying parameter #111 value...
2023-05-26T06:13:43.521Z CNTRLR « [Node 004] parameter #111 has value: 3
2023-05-26T06:13:43.522Z CNTRLR » [Node 004] querying parameter #112 value...
2023-05-26T06:13:43.562Z CNTRLR « [Node 004] parameter #112 has value: 600
2023-05-26T06:13:43.562Z CNTRLR » [Node 004] querying parameter #113 value...
2023-05-26T06:13:43.598Z CNTRLR « [Node 004] parameter #113 has value: 600
2023-05-26T06:13:43.598Z CNTRLR » [Node 004] querying parameter #254 value...
2023-05-26T06:13:43.630Z CNTRLR « [Node 004] parameter #254 has value: 0
2023-05-26T06:13:43.630Z CNTRLR   [Node 004] Interview stage completed: CommandClasses
2023-05-26T06:13:43.630Z CNTRLR   [Node 004] Interview stage completed: OverwriteConfig
2023-05-26T06:13:43.630Z CNTRLR   [Node 004] Interview completed
2023-05-26T06:13:43.631Z CNTRLR   [Node 004] The node is ready to be used
2023-05-26T06:13:43.631Z CNTRLR » [Node 004] Assigning SUC return route...
2023-05-26T06:14:00.511Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:14:12.909Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:14:28.490Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:14:40.892Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:15:39.065Z CNTRLR   [Node 003] treating BasicCC::Set as a report
New client
Client disconnected
Code 1000: 
New client
2023-05-26T06:15:51.465Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:16:17.454Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:16:29.851Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:16:41.468Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:17:06.378Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:17:17.993Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:17:41.750Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:18:32.463Z CNTRLR   [Node 003] treating BasicCC::Set as a report
2023-05-26T06:18:44.864Z CNTRLR   [Node 003] treating BasicCC::Set as a report

So, what happened? I now have both a Z-Wave JS Add On and a Z-Wave JS integration but no driver. Also, the Z-Wave JS Add On turns itself off quickly after I start it.

I’m fairly new at all of this, at quite a loss here and I’m looking for some direction if possible.

freshcoast · May 27, 2023, 6:03am

This path is incorrect. It’s not your Zooz stick. The correct path would include /dev/serial/by-id, which would map to /dev/ttyUSB0 or similar.

Where you presented with any of those options? If you are using a VM, you’ll need to setup USB pass-through.

Based on your logs though, it appears something happened and it discovered some nodes. Did you select a different USB path for that? If you are not using a USB extension cord, that would be the first thing to try.

the.loquitur · May 27, 2023, 7:16pm

Initially, I was not using a USB extension cord. I used the path that I did because when I go to Settings/System/Hardware/All_Hardware it shows

    ttyUSB0
    /dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10 700_Z-Wave_Stick_0001-if00-port0

However, when I inserted my Zooz stick and tried to Add Integration it gave me the 2 below options:

ttyS0 - /dev/ttyS0, s/n: n/a

and

Zooz ZST10 700 Z-Wave Stic - /dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10 700_Z-Wave_Stick_0001-if00-port0, s/n: 0001 - Silicon Labs - 10C4:EA60

That’s all. There is no option for for me to select /dev/ttyUSB0, so I went with the later option identifying the Zooz stick.

freshcoast · May 27, 2023, 7:25pm

The second option is the correct one, it even says “Zooz” in the pathname. The /dev/serial/by-id path is preferred over /dev/ttyUSB0, as the latter can change (e.g. to /dev/ttyUSB1). /dev/ttyS0 is just plain invalid for a USB z-wave controller.

I’m not really clear on your situation now.

Which USB device path are you currently using? First step would be to use the Zooz path.

Did you install the extension cord? That would be the second step.

After you have done the above, are you still having the same problems?

the.loquitur · May 29, 2023, 2:53am

I didn’t have the right type of USB extension cord, so I went out and got one.

I wiped my NUC (not a VM) with a bare-bone config and plugged the stick’s extension cord in. It didn’t recognize it, so I did the manual install. HA offered me

ttyS0 - /dev/ttryS0, s/n:n/a

and

Zooz ZST10 700 Z-Wave Stic - /dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10 700_Z-Wave_Stick_0001-if00-port0, s/n: 0001 - Silicon Labs - 10C4:EA60

exactly the same as before, so I took the later option as you indicated. Atfer a few minutes, it said, “Success! Created configuration for Z-Wave JS.” It immediately created the device but with the status message reading, “Retrying setup: None”.

The HA Core Log reads:

Logger: homeassistant.config_entries
Source: config_entries.py:429
First occurred: 7:39:21 PM (1 occurrences)
Last logged: 7:39:21 PM

Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background

and the Z-Wave JS logs read:

2023-05-29T02:39:19.655Z CNTRLR   [Node 004]   supports CC Binary Switch (0x25) in version 1
2023-05-29T02:39:19.655Z CNTRLR   [Node 004]   skipping query for All Switch (0x27) because max implemented vers
                                  ion is 0
2023-05-29T02:39:19.656Z CNTRLR » [Node 004]   querying the CC version for Meter...
2023-05-29T02:39:19.685Z CNTRLR   [Node 004]   supports CC Meter (0x32) in version 3
2023-05-29T02:39:19.685Z CNTRLR » [Node 004]   querying the CC version for Scene Actuator Configuration...
2023-05-29T02:39:19.718Z CNTRLR   [Node 004]   supports CC Scene Actuator Configuration (0x2c) in version 1
2023-05-29T02:39:19.718Z CNTRLR » [Node 004]   querying the CC version for Scene Activation...
2023-05-29T02:39:19.754Z CNTRLR   [Node 004]   supports CC Scene Activation (0x2b) in version 1
2023-05-29T02:39:19.755Z CNTRLR » [Node 004]   querying the CC version for Configuration...
2023-05-29T02:39:19.786Z CNTRLR   [Node 004]   supports CC Configuration (0x70) in version 1
2023-05-29T02:39:19.786Z CNTRLR » [Node 004]   querying the CC version for Association...
2023-05-29T02:39:19.815Z CNTRLR   [Node 004]   supports CC Association (0x85) in version 1
2023-05-29T02:39:19.815Z CNTRLR » [Node 004]   querying the CC version for CRC-16 Encapsulation...
2023-05-29T02:39:19.845Z CNTRLR   [Node 004]   supports CC CRC-16 Encapsulation (0x56) in version 1
2023-05-29T02:39:19.845Z CNTRLR » [Node 004]   querying the CC version for Manufacturer Specific...
2023-05-29T02:39:19.877Z CNTRLR   [Node 004]   supports CC Manufacturer Specific (0x72) in version 2
2023-05-29T02:39:19.882Z CNTRLR   [Node 004] Embedded device config loaded
2023-05-29T02:39:19.885Z CNTRLR   [Node 004] Interviewing Association...
2023-05-29T02:39:19.885Z CNTRLR » [Node 004] querying number of association groups...
2023-05-29T02:39:19.918Z CNTRLR « [Node 004] supports 2 association groups
2023-05-29T02:39:19.918Z CNTRLR » [Node 004] querying association group #1...
2023-05-29T02:39:19.951Z CNTRLR « [Node 004] received information for association group #1:
                                  maximum # of nodes: 5
                                  currently assigned nodes: 1
2023-05-29T02:39:19.952Z CNTRLR » [Node 004] querying association group #2...
2023-05-29T02:39:19.990Z CNTRLR « [Node 004] received information for association group #2:
                                  maximum # of nodes: 5
                                  currently assigned nodes: 1
2023-05-29T02:39:19.993Z CNTRLR   [Node 004] Checking/assigning lifeline groups: 1, 2
                                  supports classic associations:       true
                                  supports multi channel associations: false
2023-05-29T02:39:19.994Z CNTRLR   [Node 004] Configuring lifeline group #1:
                                  group supports multi channel:  false
                                  configured strategy:           auto
                                  must use node association:     true
                                  must use endpoint association: false
2023-05-29T02:39:19.995Z CNTRLR   [Node 004] Lifeline group #1 is already assigned with a node association
2023-05-29T02:39:19.995Z CNTRLR   [Node 004] Configuring lifeline group #2:
                                  group supports multi channel:  false
                                  configured strategy:           auto
                                  must use node association:     true
                                  must use endpoint association: false
2023-05-29T02:39:19.996Z CNTRLR   [Node 004] Lifeline group #2 is already assigned with a node association
2023-05-29T02:39:19.998Z CNTRLR   [Node 004] Interviewing Binary Switch...
2023-05-29T02:39:19.999Z CNTRLR » [Node 004] querying Binary Switch state...
2023-05-29T02:39:20.041Z CNTRLR « [Node 004] received Binary Switch state:
                                  current value:      false
2023-05-29T02:39:20.042Z CNTRLR   [Node 004] Interviewing Meter...
2023-05-29T02:39:20.042Z CNTRLR » [Node 004] querying meter support...
2023-05-29T02:39:20.079Z CNTRLR « [Node 004] received meter support:
                                  type:                 Electric
                                  supported scales:     
                                  · kWh
                                  · W
                                  · V
                                  · A
                                  supported rate types: 
                                  supports reset:       true
2023-05-29T02:39:20.080Z CNTRLR » [Node 004] querying meter value (type = Electric, scale = kWh)...
2023-05-29T02:39:20.115Z CNTRLR » [Node 004] querying meter value (type = Electric, scale = W)...
2023-05-29T02:39:20.147Z CNTRLR » [Node 004] querying meter value (type = Electric, scale = V)...
2023-05-29T02:39:20.179Z CNTRLR » [Node 004] querying meter value (type = Electric, scale = A)...
2023-05-29T02:39:20.219Z CNTRLR   [Node 004] SceneActuatorConfigurationCC: setting metadata
2023-05-29T02:39:20.279Z CNTRLR   [Node 004] Interviewing Configuration...
2023-05-29T02:39:20.280Z CNTRLR   [Node 004] ConfigurationCC: Loading configuration parameters from device confi
                                  g
2023-05-29T02:39:20.286Z CNTRLR » [Node 004] querying parameter #1 value...
New client
Client disconnected
Code 1000: 
2023-05-29T02:39:21.345Z CNTRLR   [Node 004] Timed out while waiting for a response from the node (ZW0201)
2023-05-29T02:39:21.345Z CNTRLR « [Node 004] received no value for parameter #1
2023-05-29T02:39:21.346Z CNTRLR » [Node 004] querying parameter #80 value...
2023-05-29T02:39:21.385Z CNTRLR « [Node 004] parameter #80 has value: 0
2023-05-29T02:39:21.386Z CNTRLR » [Node 004] querying parameter #90 value...
2023-05-29T02:39:21.416Z CNTRLR « [Node 004] parameter #90 has value: 1
2023-05-29T02:39:21.416Z CNTRLR » [Node 004] querying parameter #91 value...
2023-05-29T02:39:21.448Z CNTRLR « [Node 004] parameter #91 has value: 25
2023-05-29T02:39:21.448Z CNTRLR » [Node 004] querying parameter #92 value...
2023-05-29T02:39:21.481Z CNTRLR « [Node 004] parameter #92 has value: 5
2023-05-29T02:39:21.482Z CNTRLR » [Node 004] querying parameter #101 value...
2023-05-29T02:39:21.521Z CNTRLR « [Node 004] parameter #101 has value: 4
2023-05-29T02:39:21.522Z CNTRLR » [Node 004] querying parameter #102 value...
2023-05-29T02:39:21.563Z CNTRLR « [Node 004] parameter #102 has value: 8
2023-05-29T02:39:21.563Z CNTRLR » [Node 004] querying parameter #103 value...
2023-05-29T02:39:21.604Z CNTRLR « [Node 004] parameter #103 has value: 0
2023-05-29T02:39:21.604Z CNTRLR » [Node 004] querying parameter #111 value...
2023-05-29T02:39:21.641Z CNTRLR « [Node 004] parameter #111 has value: 3
2023-05-29T02:39:21.642Z CNTRLR » [Node 004] querying parameter #112 value...
2023-05-29T02:39:21.674Z CNTRLR « [Node 004] parameter #112 has value: 600
2023-05-29T02:39:21.674Z CNTRLR » [Node 004] querying parameter #113 value...
2023-05-29T02:39:21.705Z CNTRLR « [Node 004] parameter #113 has value: 600
2023-05-29T02:39:21.705Z CNTRLR » [Node 004] querying parameter #254 value...
2023-05-29T02:39:21.735Z CNTRLR « [Node 004] parameter #254 has value: 0
2023-05-29T02:39:21.736Z CNTRLR   [Node 004] Interview stage completed: CommandClasses
2023-05-29T02:39:21.736Z CNTRLR   [Node 004] Interview stage completed: OverwriteConfig
2023-05-29T02:39:21.736Z CNTRLR   [Node 004] Interview completed
2023-05-29T02:39:21.736Z CNTRLR   [Node 004] The node is ready to be used
2023-05-29T02:39:21.737Z CNTRLR » [Node 004] Assigning SUC return route...

The Z-Waze JS is installed but it won’t start. BTW, its config points to:

Zooz ZST10 700 Z-Wave Stic - /dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10 700_Z-Wave_Stick_0001-if00-port0, s/n: 0001 - Silicon Labs - 10C4:EA60

freshcoast · May 29, 2023, 6:09am

Looks like the integration disconnects while the driver is busy. It will retry. Does it end up in a permanent disconnected state? If so, if you reload the integration (Settings → Device & Services → Z-Wave → … → Reload) does it progress? Does the driver come up successfully?

the.loquitur · May 29, 2023, 6:50am

I tired reloading and it returned the state: “Retrying setup: None”. When I tried the reload, it returned with a dialog box saying “The integration was reloaded.” However, the Z-Wave integration continued to have the same: “Retrying setup: None” state.

In the Z-Wave JS logs, I’m still stuck at:

New client
Client disconnected
Code 1000:

and the HA Core logs read:

Home Assistant Core
2023-05-28 23:24:07.111 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-28 23:43:29.374 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-28 23:48:46.540 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:50:06.699 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:51:27.072 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:52:47.231 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:54:07.644 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:55:27.718 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:56:48.037 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:58:08.323 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-28 23:59:28.514 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:00:27.522 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:00:27.540 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:00:31.030 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:00:31.051 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:00:34.933 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:00:34.949 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:00:40.280 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:00:50.452 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:00:53.630 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:00:53.636 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:00:59.127 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:01:09.272 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:01:29.712 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:02:10.113 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:02:22.277 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:02:30.339 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:03:31.092 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:07:04.891 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:07:19.831 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:15:16.952 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:16:37.350 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:17:57.613 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:19:17.991 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:20:38.146 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:21:58.557 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:23:19.007 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:24:39.480 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10\xa0700_Z-Wave_Stick_0001-if00-port0', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': ''}
2023-05-29 00:27:00.380 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:27:10.334 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:29:37.591 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:31:14.931 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 00:31:51.749 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 01:18:23.724 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background
2023-05-29 01:20:09.215 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: None; Retrying in background

freshcoast · May 29, 2023, 4:21pm

I wonder if this is a bug in the add-on management and it’s confused by the serial path. Your Zooz stick is from a bad batch that have mis-configured product ids and include a unicode space character in the path. I don’t have any further input on that error, but there are a few options I’d try.

Submit a new issue to Issues · home-assistant/core · GitHub. It may some time to address though.
Re-try the installation after re-programming the product name using the Silicon Labs programming utility to remove the unicode \xa0 character. This is explained in post Remove Space in the ID path for Zooz ZST10 700 Z-Wave Stick name - #9 by ServiceXp. You do need to download Simplicity Studio which is a pain. I think Zooz will fix this for you, but you’ll need to ship the stick back to them. Check with their Support.
Install the Z-Wave JS UI community add-on, instead of the official add-on. This will allow you to use path /dev/ttyUSB0 instead of the /dev/serial/by-id path. The only problem with this is there is a chance USB0 can change to USB1, depending on your system configuration. If you don’t re-plug the stick, or don’t have other devices using USBX, then you might be OK. I, and many others, prefer ZUI. You can still go this route and also fix the device naming above to use the /dev/serial/by-id path.
Install the Z-Wave JS official add-on first manually, then install the Z-Wave integration and disable the checkbox “Use Supervisor” when installing it. You’ll need to manually input the Server URL as ws://core-zwave-js:3000. Doing it this way will remove the management connection between HA and the add-on, which is where it seems to be failing. It seems the add-on itself is working OK, just not the integration add-on management. Might as well use ZUI though.

the.loquitur · May 30, 2023, 2:41am

2 & 4. I already have Silicon Lab’s Simplicity Studio installed and I’m a little familiar with it. Following the instructions in the post Remove Space in the ID path for Zooz ZST10 700 Z-Wave Stick name - #9 by ServiceXp was pretty easy. Here are the stick’s new attributes:

Attributes:
DEVLINKS: >-
  /dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_0001-if00-port0
  /dev/serial/by-path/pci-0000:00:14.0-usb-0:10:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: Zooz_ZST10_700_Z-Wave_Stick
ID_MODEL_ENC: Zooz_ZST10_700_Z-Wave_Stick
ID_MODEL_ID: ea60
ID_PATH: pci-0000:00:14.0-usb-0:10:1.0
ID_PATH_TAG: pci-0000_00_14_0-usb-0_10_1_0
ID_REVISION: '0100'
ID_SERIAL: Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_0001
ID_SERIAL_SHORT: '0001'
ID_TYPE: generic
ID_USB_DRIVER: cp210x
ID_USB_INTERFACES: ':ff0000:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: Zooz_ZST10_700_Z-Wave_Stick
ID_USB_MODEL_ENC: Zooz_ZST10_700_Z-Wave_Stick
ID_USB_MODEL_ID: ea60
ID_USB_REVISION: '0100'
ID_USB_SERIAL: Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_0001
ID_USB_SERIAL_SHORT: '0001'
ID_USB_TYPE: generic
ID_USB_VENDOR: Silicon_Labs
ID_USB_VENDOR_ENC: Silicon\x20Labs
ID_USB_VENDOR_ID: 10c4
ID_VENDOR: Silicon_Labs
ID_VENDOR_ENC: Silicon\x20Labs
ID_VENDOR_ID: 10c4
MAJOR: '188'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '74605051372'

However, now that I did this, installing with the JS Supervisor gives me “Failed to install the Z-Wave JS add-on” and without JS Supervisor it gives me “Failed to connect” with the URL set to both “ws://localhost:3000” and “ws://core-zwave-js:3000”.

I tried initially installing the both JS and JS UI and they returned the error messages:

Can't install homeassistant/amd64-addon-zwave_js:0.1.83: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=0.1.83&fromImage=homeassistant%2Famd64-addon-zwave_js&platform=linux%2Famd64: Internal Server Error ("Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: no such host")

and

Can't install ghcr.io/hassio-addons/zwave-js-ui/amd64:1.13.2: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=1.13.2&fromImage=ghcr.io%2Fhassio-addons%2Fzwave-js-ui%2Famd64&platform=linux%2Famd64: Internal Server Error ("Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io: no such host")

I’ve just ordered a Silicon Labs UZB-7, Z-Wave 700 Stick Bridge Module, to see how that goes, after I apply what ever firmware updates are available.

I really appreciate your help here and with your sticking with this. There is only so much that you can do not being a developer.

Thanks !

freshcoast · May 30, 2023, 3:21am

Those errors don’t really have anything to do with Z-Wave or the controller. Seems you’re having some kind of DNS issue.

Jgree321 · August 14, 2023, 1:47am

Having similar issues with Zooz S2 stick.
Fought with it a ton when first trying to integrate to HA via Vmware but was working fine for many months until today…
Today I added a bluetooth usb device which required me making some edits to Vmware to autoconnect that USB.
For some reason after messing around with things today Zwave JS would never start up correctly.
Logs showed:
DRIVER Controller identification returned invalid node ID 0
The controller was being specified in the config file with the serial-by-id like this:
Device
/dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_6c31808ea321ec11929fbb942c86906c-if00-port0

I gave up fighting with it and launched zwave JS UI which was already installed/configured.
It loaded up fine and all Zwave devices came online in a short time.
I know Zwave JS UI specifies the device simply by USB0 so I tried editing the config file for Zwave JS to be the same way. Even with that though it fails to start.

Summary, I have no idea what’s going on with Zwave JS but for now I’ve abandoned it and I’m running on the JS UI version.
I feel like the Zooz stick has given me nothing but fits.

harryfine · August 14, 2023, 2:17am

I tried everything also, there are issues and the developers don’t seem to want to admit it, they send you running in circles trying different things. I finally gave up.

freshcoast · August 14, 2023, 2:37am

That’s a bug in Z-Wave JS. Stick with ZUI which has a workaround.

You should stick with using /dev/serial/by-id/usb-Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_6c31808ea321ec11929fbb942c86906c-if00-port0 in ZUI. Using /dev/ttyUSB0 might cause you problems in the future, as those device names can change.