Z-wave not responsing after update of today !

[Morgandax]

The problem

Hello, Following an update of zwave js, nothing works anymore because it notifies me that it cannot load the configuration. This is the first time this has happened to me...! And I'm worried because quite a few zwave devices, am I the only one that this update has broken? Thank you in advance for your feedback and help. Morgan

What version of Home Assistant Core has the issue?

core-2024.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zwave JS

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[Morgandax]

2024-09-12 18:38:31.054 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-0658_0200-if00', 's0_legacy_key': '', 's2_access_control_key': '', 's2_authenticated_key': '', 's2_unauthenticated_key': '', 'lr_s2_access_control_key': '', 'lr_s2_authenticated_key': ''}

[home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[jTd7bPLFb]

same here. after update, no z-wave devices work. pinging them works, but all other stuff is no go.

update: after poweroff homeassistant, replug usb stick, boot homeassistant up and re-interviewing each z-wave device, some of them (the ones without S2 connection security) seem to come back again

[mrochette01]

Same thing on my side, after the update only 2 devices work out of 40. I rebooted via the HA interface and also performed a cold reboot. It still doesn't work.

What's the solution?

[paul-aviles]

Same here, but disabling zwave, reconnecting the usb plug and restarting it did nothing.

[jTd7bPLFb]

Insecure connection seems to work. S2 required devices (like Shlage Z-Wave Lock) does not work. Securely connected devices do now work either, even after re-inverviewing. I could re-connecte (exclude, include) the T6 Thermostat in insecure mode, but not in S2.

[mrochette01]

I have: 1- Stopped HA 2 - Removed the USB key 3 - Put the USB key back 4 - Restarted HA

Nothing works

[paul-aviles]

Even the restore of backup created before the update does not work for me.

Update: I did the restore to 0.6.2 again and it worked. I also got the notification for an update available....will definitely skip it :-)

[mrochette01]

I'm thinking of going back? But it doesn't seem to work.

[paul-aviles]

I'm thinking of going back? But it doesn't seem to work.

Try the restore again, worked for me.

[mrochette01]

I'd like a little help with the backspace. Can you share with me how to do it? Thank you

Update: Is this the right procedure?

System -> Backups -> Select backup (addon_core_zwave_js_0.6.2) and the left button and select the file and the "restore" action. Is this the right procedure?

I backtracked and restarted HA. To be continued..... ET CA FONCTIONNE. I'll wait before installing the next version.

[paul-aviles]

I'd like a little help with the backspace. Can you share with me how to do it? Thank you

Update: Is this the right procedure?

System -> Backups -> Select backup (addon_core_zwave_js_0.6.2) and the left button and select the file and the "restore" action. Is this the right procedure?

Yes, make sure you select the options and select Restore like the image.

[mrochette01]

Thanks, I really appreciate the community support.

[paul-aviles]

Wonder what really happened though....

[bondelswag]

All Z-wave devices non- responsive after update today

[paul-aviles]

All Z-wave devices non- responsive after update today

Do a restore before the update...

[MartinHjelmare]

Please report what add-on version caused the problem. Ie what did you update to?

[jTd7bPLFb]

latest version that was pushed today (12.09.2024) Diagnostics Driver version: 13.3.0 Server version: 1.38.0 Server URL: ws://core-zwave-js:3000

[MartinHjelmare]

I'd like to know exactly which version since there were two updates published during the same day.

[jTd7bPLFb]

How do we find out the version. and yes, there were 2 updates. I am on the 2nd one, think was .1 at the end, did not relally take note, as before I never had issues.

as I say, seems that anything that was bound with S2 does not work anymore ( smoke alarms, schlage zwave lock). other devices I was able to reinvterview or exclude include without security.

[MartinHjelmare]

That would be add-on version 0.7.1. The version is shown on the update notification and when the add-on is installed, on the info tab of the add-on.

[MartinHjelmare]

I have enough information for now. I'll possibly ask for more information later.

[jTd7bPLFb]

Yes. 0.7.1. I see it in the add on info tab.

[darootler]

I do have the same problem, all devices are not available. Downgraded to version 0.6.2, everything fine again.

Regards Richard

[MartinHjelmare]

Please don't comment unless you bring new information.

[MartinHjelmare]

I've tested S2 inclusion on driver version 13.3.0 with the add-on version 0.7.1 and that is working for me. At this point we need driver debug level logs of an S2 inclusion attempt, from users with affected devices.

https://www.home-assistant.io/integrations/zwave_js/#how-do-i-access-the-z-wave-logs

[LoicbEc]

Bonjour , si cela peut aider , j'ai eu le même soucis . Après plusieurs redémarrages , reconstruction sans succès . j'ai re interroger les modules et tout et rentrée dans l'ordre bonne journée a tous :)

[FoxxMD]

@MartinHjelmare I am experiencing this same issue and am attaching DEBUG log level logs of Z-Wave JS addon startup that includes devices with S2 inclusion.

I did both upgrades yesterday (for the add-on) at which point failures started occurring.

• Z-wave JS Addon
  • Driver Version 13.3.0
  • Server Version 1.38.0
• Home Assistant 2024.9.1
• Supervisor 2024.09.1
• OS 13.1 running as a VM in Proxmox 8.2.2
• Controller is a GoControl HUSBZB-1 Firmware 4.32
  • Passthrough full USB port, this has never been a problem before

Secure z-wave devices:

• Schlage BE469ZP Lock - S0 Legacy
• 3x NewOne N4003 Plug - S2 (Z-Wave Plus v2)
• Zooz ZSE40 700 Sensor - S2 (Z-Wave Plus v2)

No changes to configuration or keys were made prior to the add-on upgrades. I have done a full shutdown of the VM, replugged USB and verified port passthrough as well as USB availability in the VM.

zwave.log

[MartinHjelmare]

@FoxxMD please check if all network keys are set in the add-on configuration options.

[FoxxMD]

All network keys are set but I can't verify they are the same as the ones before the upgrade. I don't have any recent backups.

EDIT: Found the backups in HA! Can verify the keys are the same as when I was on addon 0.6.2

[paul-aviles]

Yesterday I reverted back to 0.6.2 and got it working. Today I saw someone posted they had no issues with the update so hesitated to try again but went on doing it. 1 deleted all the backups 2 did a full backup and downloaded it to my pc 3 did the upgrade to 0.7.1 from Settings/Add-ons/Z-Wave JD

All went fine and it took about 1 min. (Pi 4 8gb)

So I don't know what happened yesterday, perhaps both updates went one after the other too quickly?

Anyway, seems to be ok now. Thanks MartinHjelmare.

[jTd7bPLFb]

I see this in log 2024-09-13T14:44:49.433Z CNTRLR [Node 064] Interview stage completed: NodeInfo 2024-09-13T14:44:49.440Z CNTRLR [Node 064] supports Security S2, but no S2 network keys were configured. The i nterview might not include all functionality. Error in driver ZWaveError: Node 064 supports Security S2, but no S2 network keys were configured. The interview might not include all functionality. (ZW0214) at ZWaveNode.interviewCCs (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:2251:8) at ZWaveNode.interviewInternal (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1861:20) at Driver.interviewNodeInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1922:10) { code: 214, context: undefined, transactionSource: undefined

BUT the keys are all set in configuration of the plugin. I did re copy/paste them in, and hit save, just to make sure.

but still same error

[MartinHjelmare]

Not sure what's happening with the missing keys, maybe some kind of storage corruption. I'd advise users that are seeing similar issues to try the update again after restoring a working backup. Make sure you have a good backup before trying the update.

ie do these steps:

1. Restore a working backup.
2. Check that everything is working again.
3. Try the add-on update version 0.7.1 again.

[FoxxMD]

Reverting to 0.6.1 has resolved the issue. Will attempt to update again after making some backups and getting some more free time to troubleshoot.

[tateu]

Using an Ecolink Smart Switch via HUSBZB-1: when I upgraded from 0.6.2 -> 0.7.0 -> 0.7.1 with reboots, the switch stopped working. I restored to a backup of 0.6.2 with a reboot and it started working again. I then went directly from 0.6.2 -> 0.7.1 just now and the switch worked after a reboot.

[CrunchSA]

restore to 0.6.2 followed by re-update to 0.7.1 is working

[jTd7bPLFb]

restore (downgrade) to 0.6.2 followed by re-update to 0.7.1 is working. Seems the 0.7.0 in between broke things for the ones who were fast to update to it :)

[Bubbalax]

I upgraded Zwave to version 0.7.0, then to 0.7.1, and noticed that some devices went offline. I downgraded to 0.6.2, and everything started working again. After upgrading back to 0.7.1, things seemed fine at first, but I soon noticed that my automations weren't working. Specifically, all my Z-Wave devices that were added securely were reporting as connected, but they were not responding to commands (e.g., turning on/off). However, legacy Z-Wave devices were functioning normally. I then restored my setup back to 0.6.2, and everything is working correctly again.

[Morgandax]

La restauration (déclassement) vers 0.6.2 suivie d'une nouvelle mise à jour vers 0.7.1 fonctionne.Il semble que le 0.7.0 entre les deux a cassé des choses pour ceux qui ont été rapides à le mettre à jour :)

How do you perform a downgrade, please?

[Bubbalax]

La restauration (déclassement) vers 0.6.2 suivie d'une nouvelle mise à jour vers 0.7.1 fonctionne.Il semble que le 0.7.0 entre les deux a cassé des choses pour ceux qui ont été rapides à le mettre à jour :)

How do you perform a downgrade, please?

You do a restore from the time before you did the 0.7.0 upgrade.

[Morgandax]

La restauration (déclassement) vers 0.6.2 suivie d'une nouvelle mise à jour vers 0.7.1 fonctionne.Il semble que le 0.7.0 entre les deux a cassé des choses pour ceux qui ont été rapides à le mettre à jour :)

How do you perform a downgrade, please?

You do a restore from the time before you did the 0.7.0 upgrade.

A complete restore of HA ? Thanks

[FoxxMD]

@Morgandax and any others who need to restore back to 0.6.X but don't know how to do this:

Find Backups Page

• Open HA -> Settings -> System -> Backups
• Or go to http://MY_HOME_ASSISTANT_HOST:PORT/hassio/backups
• Or from anywhere in HA type c and search for Backups (second entry)

Find Correct Backup

Somewhere near the top of the list you should see addons_core_zwave_js_0.6.2 (or whatever version of 0.6.X you have backed up)

Restore Backup

Click the backup name, then select Z-Wave JS from the popup menu, then Restore

HA will restore the backup and you should be operating normally again.

[Morgandax]

@Morgandax and any others who need to restore back to 0.6.X but don't know how to do this:

Find Backups Page

• Open HA -> Settings -> System -> Backups
• Or go to http://MY_HOME_ASSISTANT_HOST:PORT/hassio/backups
• Or from anywhere in HA type c and search for Backups (second entry)

Find Correct Backup

Somewhere near the top of the list you should see addons_core_zwave_js_0.6.2 (or whatever version of 0.6.X you have backed up)

Restore Backup

Click the backup name, then select Z-Wave JS from the popup menu, then Restore

HA will restore the backup and you should be operating normally again.

This community is awesome :)! Thank you so much guys ! I was able to reinstall only the Z-WAVE JS addon, and now I'm on version 0.6.2! However, I'm stuck just like with version 0.7 (even though version 0.6 worked well at the time) :( Any idea?

[jTd7bPLFb]

This community is awesome :)! Thank you so much guys ! I was able to reinstall only the Z-WAVE JS addon, and now I'm on version 0.6.2! However, I'm stuck just like with version 0.7 (even though version 0.6 worked well at the time) :( Any idea?

Restore from backup the 0.6.2 version. I think, that on reinstall (as uninstall, install), the keys might be re-generated and do not correspond to your old keys.

Better to restore 0.6.2 from the latest backup.

[Morgandax]

This community is awesome :)! Thank you so much guys ! I was able to reinstall only the Z-WAVE JS addon, and now I'm on version 0.6.2! However, I'm stuck just like with version 0.7 (even though version 0.6 worked well at the time) :( Any idea?

Restore from backup the 0.6.2 version. I think, that on reinstall (as uninstall, install), the keys might be re-generated and do not correspond to your old keys.

Better to restore 0.6.2 from the latest backup.

That's what I did, I restored the plugin to version 0.6.2, but without success... Or maybe I didn't understand you and missed something?

[Morgandax]

Here is the error I get when I attempt to restore Z-wave JS: An error occurred during restore of 0e4c7f8a, check job 'a44a214ebc314fcaaaaebd297992b789' or supervisor logs for details

This community is awesome :)! Thank you so much guys ! I was able to reinstall only the Z-WAVE JS addon, and now I'm on version 0.6.2! However, I'm stuck just like with version 0.7 (even though version 0.6 worked well at the time) :( Any idea?

Restore from backup the 0.6.2 version. I think, that on reinstall (as uninstall, install), the keys might be re-generated and do not correspond to your old keys.

Better to restore 0.6.2 from the latest backup.

Here is the error I get when I attempt to restore Z-wave JS: An error occurred during restore of 0e4c7f8a, check job 'a44a214ebc314fcaaaaebd297992b789' or supervisor logs for details

[Morgandax]

This community is awesome :)! Thank you so much guys ! I was able to reinstall only the Z-WAVE JS addon, and now I'm on version 0.6.2! However, I'm stuck just like with version 0.7 (even though version 0.6 worked well at the time) :( Any idea?

Restore from backup the 0.6.2 version. I think, that on reinstall (as uninstall, install), the keys might be re-generated and do not correspond to your old keys.

Better to restore 0.6.2 from the latest backup.

It's working again now. The issue was with my Z-Wave key, which I had unplugged and replugged, but my virtual machine (on my Synology NAS) had 'lost' it. After reassigning the key to the VM, everything went back to normal.

Thanks to everyone, it's really nice to know that there's such a great community 🙏🏼.

Issue solved on my end thanks to the downgrade + reassigning the key to the VM.

Is it safe to update to 0.7.1, or is it recommended to wait ?

Have a good day. Morgan

[jTd7bPLFb]

Had to downgrade to 0.6.2 again, because 0.7.1 seems to be glitching. aftet reboot, the symptoms of S2 key not set message, although the key is set and 0.7.1 was running for 5 hours, returned. Maybe it's just me, but ¯_(ツ)_/¯ .

Edited: spelling

[paul-aviles]

Had to downgrade to 0.6.2 again, because 0.7.1seema to be glitching. aftet reboot, the symptoms of S2 key not set message, although the key is set and 0.7.1 was running for 5 hours, returned. Maybe it's just me, but ¯(ツ)/¯ .

I think I am getting the same, just noticed it this morning after your message. I see the message in the logs of a missing key or driver not ready.

Any developer wanting to do any debug before I downgrade to.0.6.2?

[joshuathejack]

Same. All Z-wave devices show as available but are not actionable. Cannot interact with them. Also, I'm not allowed to skip the 0.7.1 update. Reverted back to 0.6.2 until we get clear direction.