core icon indicating copy to clipboard operation
core copied to clipboard

Z-wave not responsing after update of today !

Open Morgandax opened this issue 1 year ago • 69 comments

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 avatar Sep 12 '24 16:09 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': ''}

Morgandax avatar Sep 12 '24 17:09 Morgandax

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)

home-assistant[bot] avatar Sep 12 '24 20:09 home-assistant[bot]

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

jTd7bPLFb avatar Sep 12 '24 21:09 jTd7bPLFb

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?

mrochette01 avatar Sep 12 '24 22:09 mrochette01

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

paul-aviles avatar Sep 12 '24 22:09 paul-aviles

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.

jTd7bPLFb avatar Sep 12 '24 22:09 jTd7bPLFb

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

Nothing works

mrochette01 avatar Sep 12 '24 22:09 mrochette01

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 :-)

paul-aviles avatar Sep 12 '24 22:09 paul-aviles

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

mrochette01 avatar Sep 12 '24 22:09 mrochette01

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

Try the restore again, worked for me.

paul-aviles avatar Sep 12 '24 22:09 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?

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

mrochette01 avatar Sep 12 '24 22:09 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?

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

paul-aviles avatar Sep 12 '24 23:09 paul-aviles

Thanks, I really appreciate the community support.

mrochette01 avatar Sep 12 '24 23:09 mrochette01

Wonder what really happened though....

paul-aviles avatar Sep 12 '24 23:09 paul-aviles

All Z-wave devices non- responsive after update today

bondelswag avatar Sep 13 '24 00:09 bondelswag

All Z-wave devices non- responsive after update today

Do a restore before the update...

paul-aviles avatar Sep 13 '24 00:09 paul-aviles

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

MartinHjelmare avatar Sep 13 '24 03:09 MartinHjelmare

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

jTd7bPLFb avatar Sep 13 '24 04:09 jTd7bPLFb

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

MartinHjelmare avatar Sep 13 '24 04:09 MartinHjelmare

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.

jTd7bPLFb avatar Sep 13 '24 04:09 jTd7bPLFb

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 avatar Sep 13 '24 04:09 MartinHjelmare

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

MartinHjelmare avatar Sep 13 '24 04:09 MartinHjelmare

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

jTd7bPLFb avatar Sep 13 '24 04:09 jTd7bPLFb

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

Regards Richard

darootler avatar Sep 13 '24 06:09 darootler

Please don't comment unless you bring new information.

MartinHjelmare avatar Sep 13 '24 07:09 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

MartinHjelmare avatar Sep 13 '24 08:09 MartinHjelmare

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 :)

LoicbEc avatar Sep 13 '24 10:09 LoicbEc

@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

FoxxMD avatar Sep 13 '24 13:09 FoxxMD

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

MartinHjelmare avatar Sep 13 '24 13:09 MartinHjelmare

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

FoxxMD avatar Sep 13 '24 14:09 FoxxMD