Zwave.js fails to load

fribse · September 29, 2021, 10:16pm

I see this when it tries to load:

[00:14:10] INFO: Successfully send discovery information to Home Assistant.
Error: failed loading config file /etc/zwave_config.json
Error: Invalid key format for securityKeys.S0_Legacy option
    at normalizeKey (/usr/src/node_modules/@zwave-js/server/dist/bin/server.js:16:11)
    at /usr/src/node_modules/@zwave-js/server/dist/bin/server.js:59:53
    at Object.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/bin/server.js:118:3)
    at Module._compile (internal/modules/cjs/loader.js:1072:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
    at Module.load (internal/modules/cjs/loader.js:937:32)
    at Function.Module._load (internal/modules/cjs/loader.js:778:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47
[00:14:11] INFO: Successfully send discovery information to Home Assistant.

I have no idea why this suddenly happened. It was crashed, so I started it, and now it shows this?

tmjpugh · September 29, 2021, 11:01pm

Can’t load config because wrong key format
May need open config and fix if not able by UI

BebeMischa · September 29, 2021, 11:03pm

Have you just updated Z-wave JS to 0.1.41?

mwav3 · September 29, 2021, 11:22pm

There seems to be some changes around the security keys recently

It looks like it’s causing problems.

I’d file a github issue

AnAx · September 29, 2021, 11:24pm

Same error for me after updating Z-wave JS to 0.1.41.
Had a quick look and I do not have the file : /etc/zwave_config.json

BebeMischa · September 29, 2021, 11:25pm

Look here: Z-wave JS stopped working. Most of my home out of order... Here we go again

tmjpugh · September 29, 2021, 11:25pm

Someone already did

github.com/home-assistant/core

Z-wave JS 0.1.41 udate gone bad

opened 11:18PM - 29 Sep 21 UTC

closed 12:08PM - 30 Sep 21 UTC

BebeMischa

integration: zwave_js

### The problem Just had an update on Z-wave JS, from Z-Wave JS 0.1.40 to Z-Wav…e JS 0.1.41. After that update Z-wave is dead. All my buttons and sensors out of order. No light in the bathroom, WC and so on. Restoring backup made by the update and reboot the host solved the issue. Now afraid to update again... ### What is version of Home Assistant Core has the issue? core-2021.9.7 ### What was the last working version of Home Assistant Core? core-2021.9.7 ### What type of installation are you running? Home Assistant Supervised ### Integration causing the issue Z-wave JS ### Link to integration documentation on our website https://www.home-assistant.io/integrations/zwave_js/ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt Logger: homeassistant.config_entries Source: components/zwave_js/__init__.py:590 First occurred: 00:03:52 (1 occurrences) Last logged: 00:03:52 Error setting up entry Z-Wave JS for zwave_js Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 304, in async_setup result = await component.async_setup_entry(hass, self) # type: ignore File "/usr/src/homeassistant/homeassistant/components/zwave_js/__init__.py", line 121, in async_setup_entry await async_ensure_addon_running(hass, entry) File "/usr/src/homeassistant/homeassistant/components/zwave_js/__init__.py", line 590, in async_ensure_addon_running addon_network_key = addon_options[CONF_ADDON_NETWORK_KEY] KeyError: 'network_key' ``` ### Additional information So my setup is now running again on Z-wave JS 0.1.40 but I wan't you guys to be aware of this problem.

BebeMischa · September 29, 2021, 11:26pm

It was me…

mwav3 · September 29, 2021, 11:27pm

Just saw it, and looks like the fix will be released in the beta core update tomorrow.

So either wait until tomorrow for the update, or restore your backup/snapshot prior to updating the addon and restart.

freshcoast · September 29, 2021, 11:32pm

Go into the addon configuration and fix the s0_legacy_key setting so it’s in the Z-Wave JS format, not the OZW format. That means instead of 0x11, 0x22, 0x33, ... it’s 112233. No hex prefixes, commas, or spaces. After that, you’ll still need to wait for the update that was already mentioned.

fribse · September 30, 2021, 6:52am

Hi All
Wow, that was a lot of great information. I’m going to roll back, it had done the update automagically.
It’s not a VERY big issue here, as I only have my lock on z-wave, but the lock is rather essential though

EDIT: And the rollback is done, and it’s working again…

BetaUser · September 30, 2021, 10:01am

I had the same error.
But changing the key format fixed it! thank you

beurdy · September 30, 2021, 10:09am

Can you post an example?

I just tried the same but failed. Using v0.1.42

fribse · September 30, 2021, 11:12am

After upgrading I changed the keyformat and removed ,0x so it’s just one long hexadecimal string, and then it worked.

BetaUser · September 30, 2021, 11:12am

@freshcoast has explained it above:
in the supervisor you go to the configuration of the Z-Wave JS module.
There I changed my s0_legacy_key and network_key.
Mine had these 0x?? hex prefix in it. just remove them like mentioned above.
Than save and reboot ha.

fribse · September 30, 2021, 11:16am

You can see the beginning of my key.
That was written as:
0xF0, 0xC7, …
and now it’s just
F0C7…

beurdy · September 30, 2021, 11:22am

Thanks all!

You should also empty the network_key field. That was my mistake…