Error: failed loading config file /etc/zwave_config.json

Hi All,

After updating zwave js addon this evening to version 0.1.85 it stopped working with this error in the log

[19:25:34] INFO: Service restart after closing
[21:25:35] INFO: Successfully send discovery information to Home Assistant.
Error: failed loading config file /etc/zwave_config.json
Error: Invalid key format for securityKeys.S2_AccessControl option
    at normalizeKey (/usr/src/node_modules/@zwave-js/server/dist/bin/server.js:18:11)
    at /usr/src/node_modules/@zwave-js/server/dist/bin/server.js:66:53
    at Object.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/bin/server.js:140:3)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Function.Module._load (node:internal/modules/cjs/loader:960:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47
[19:25:36] INFO: Service restart after closing

Is it just me or ? Any idea how to fix ? restore of addon backup did not solve the issue.

Any help welcome,

Edwin

I think it’s the Z-Wave JS UI update 1.15.4.
the previous errors in the logs are fixed, removed legacy network key and remove a space in the S2 security key.

If I stop Z-Wave JS UI and restart Z-Wave JS it works. Otherwise the log shows that the zwave device is in use.

2023-08-07T20:52:51.449Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
Unable to start driver ZWaveError: Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port (ZW0100)
    at Driver.openSerialport (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1136:9)
    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:963:5) {
  code: 100,
  context: undefined,
  transactionSource: undefined
}

Rollback to previous version does not solve the problem.
I will stop Z-wave JS UI for now

Same here, after updating zwave js ui it does not show any more devices, also connecting from devices to add-on does not work anymore.

The latest Z-Wave JS UI does have problems, but this error doesn’t look like one of them. It appears you are running both the Z-Wave JS add-on and Z-Wave JS UI add-ons at the same time, which is not allowed. Is that the case? https://www.home-assistant.io/integrations/zwave_js/#can-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on

What are the problems? I haven’t read about any until this.

1 Like

Thanks for the info. I literally just read the thread in the first link.

I guess it’s a good thing I never live on the bleeding edge with updates.

I’m still running zwavejs-ui 8.15.0 & and zwavejs 10.17.1 and I guess I’ll be waiting a bit longer to update.

:slightly_smiling_face:

@freshcoast thx, always had both addons running without issues. rtfm! :sleeping:
Uninstalled and restored backup of z-wave js ui 1.15.3, restart HA and z-wave device are back online.
1.15.4 does not work, no devices.