core: Z-wave JS 0.1.41 udate gone bad

The problem

Just had an update on Z-wave JS, from Z-Wave JS 0.1.40 to Z-Wave 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?

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.

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 1
Comments: 16 (5 by maintainers)

Most upvoted comments

We’ll release a new add-on version with a fix asap.

MartinHjelmare on Sep 30, 2021

Thanks for the report! It will be fixed in the beta release of core tomorrow.

MartinHjelmare on Sep 29, 2021

@MartinHjelmare

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] config.sh: executing... 
[09:55:32] FATAL: Both 'network_key' and 's0_legacy_key' are set to different values 
[09:55:32] FATAL: so we are unsure which one to use. One needs to be removed from the 
[09:55:32] FATAL: configuration in order to start the addon.
[cont-init.d] config.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

The keys are the same EXCEPT for the fact my network key is lowercase and the S0 key is uppercase.

EDIT: I copied the uppercase key over to the lowercase network key and it is now working. In the meantime, before overwriting the network key, I also enabled SSL on my HASS in case it matters.

alexruffell on Sep 30, 2021

Ok, I now upgraded from 0.1.40 directly to 0.1.42 and everything is ok. Did not need to edit anything.

BebeMischa on Sep 30, 2021

The Network Key is the legacy encryption key. The format needs to be changed if you have it.

fribse on Sep 30, 2021

Convert it to this format: A1B2C3A1B2C3A1B2C3A1B2C3A1B2C3A1

With that it works as it should. Thanks.

fribse on Sep 30, 2021