Z-Wave JS add-on options: not a valid value for dictionary value

Configuration Z-Wave
1

Logger: homeassistant.components.zwave_js
Source: components/hassio/addon_manager.py:410
integration: Z-Wave (documentation, issues)
First occurred: January 19, 2025 at 1:15:47 PM (1046 occurrences)
Last logged: 12:26:14 PM

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-0658_0200-if00’, ‘s0_legacy_key’: ‘REDACTED’, ‘s2_access_control_key’: ‘5AA0CF8D8AF498C5DACB6F90ED147F80’, ‘s2_authenticated_key’: ‘REDACTED’, ‘s2_unauthenticated_key’: 'REDACTED, ‘lr_s2_access_control_key’: ‘REDACTED’, ‘lr_s2_authenticated_key’: ‘REDACTED’}

I updated and the logs show this error
WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

I failing to start.

Any ideas on how to roll it back?

2

This is standard message if you use custom addons. It is for info only and does not indicate an error or good system operation

I would double check the entered data. You may be entering something wrong or extra

3

I’m going to take a guess and say that even though the config is correct, somehow the ZStick is not actually connected or seen by ZWaveJS

1 Like
4

I started to have the same, not sure when:

2025-06-22 11:38:26.133 DEBUG (MainThread) [homeassistant.components.zwave_js] Add-on store info: {'detached': False, 'apparmor': 'default', 'auth_api': False, 'docker_api': False, 'full_access': False, 'homeassistant_api': False, 'host_network': False, 'host_pid': False, 'ingress': False, 'long_description': '# Home Assistant Add-on: Z-Wave JS\n\nAllow Home Assistant to talk to a Z-Wave Network via a USB Controller.\n\n![Supports aarch64 Architecture][aarch64-shield] ![Supports amd64 Architecture][amd64-shield] ![Supports armhf Architecture][armhf-shield] ![Supports armv7 Architecture][armv7-shield] ![Supports i386 Architecture][i386-shield]\n\n\n[aarch64-shield]: https://img.shields.io/badge/aarch64-yes-green.svg\n[amd64-shield]: https://img.shields.io/badge/amd64-yes-green.svg\n[armhf-shield]: https://img.shields.io/badge/armhf-yes-green.svg\n[armv7-shield]: https://img.shields.io/badge/armv7-yes-green.svg\n[i386-shield]: https://img.shields.io/badge/i386-yes-green.svg\n', 'rating': 6, 'signed': True, 'supervisor_api': True, 'supervisor_role': 'default', 'arch': ['amd64', 'i386', 'armhf', 'armv7', 'aarch64'], 'documentation': True, 'advanced': False, 'available': True, 'build': False, 'description': 'Control a Z-Wave network with Home Assistant Z-Wave JS', 'homeassistant': '2025.5.0', 'icon': True, 'logo': True, 'name': 'Z-Wave JS', 'repository': 'core', 'slug': 'core_zwave_js', 'stage': 'stable', 'update_available': False, 'url': 'https://github.com/home-assistant/addons/tree/master/zwave_js', 'version_latest': '0.16.0', 'version': '0.16.0', 'installed': True}
2025-06-22 11:38:26.137 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_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0', 
's0_legacy_key': 'REDACTED', 
's2_access_control_key': 'REDACTED', 
's2_authenticated_key': 'REDACTED',
 's2_unauthenticated_key': 'REDACTED', 
'lr_s2_access_control_key': 'REDACTED', 
'lr_s2_authenticated_key': 'REDACTED'
}

I did check that all the REDACTED valued are valid HEX and no invalid char had crept in. In this worked find. All I did was apply a recent upgrade

5

I found that my Z-WAVE JS add-on also is not starting:

2025-06-22 12:17:41.207 CONFIG   version 15.6.0
2025-06-22 12:17:41.596 CNTRLR   querying Serial API capabilities...
2025-06-22 12:17:46.555 DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK 
                                 from the controller (ZW0200)
                                     at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/drive
                                 r/Driver.ts:7057:23)
                                     at ZWaveController.queryCapabilities (file:///usr/src/node_modules/zwave-j
                                 s/src/lib/controller/Controller.ts:1063:37)
                                     at Driver.initializeControllerAndNodes (file:///usr/src/node_modules/zwave
                                 -js/src/lib/driver/Driver.ts:1970:46)
                                     at Immediate.<anonymous> (file:///usr/src/node_modules/zwave-js/src/lib/dr
                                 iver/Driver.ts:1696:16)
Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
    at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7057:23)
    at ZWaveController.queryCapabilities (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:1063:37)
    at Driver.initializeControllerAndNodes (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1970:46)
    at Immediate.<anonymous> (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1696:16) (ZW0100)
    at Immediate.<anonymous> (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1716:6) {
  code: 100,
  context: undefined,
  transactionSource: undefined
}
Shutting down
[04:17:46] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

disconnecting the controller, and even fully shutting down my HA Rpi and restarting didn’t help

6

Your not mistakenly using both zwavejs and zwavejsui

Need to look into why it’s not connecting with controller