ZwaveJS 0.7.0 breaking my Zwave

Configuration Z-Wave
12

How to proceed then?

13

the same one as you

14

First, obvious answer is to rollback to the previous version assuming you have a backup.

Second, feel free to submit an issue because the add-on did not migrate the soft-reset configuration to the v13 configuration. https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating/v13?id=removed-deprecated-things

15

FYI, the add-on is already being updated to fix this. https://github.com/home-assistant/addons/pull/3760

1 Like
16

Thank you!

17

I’m stuck in the same boat! :frowning:

18

Read the posts above your comment.

19

so according to this thread: Fix zwave_js soft reset option by MartinHjelmare · Pull Request #3760 · home-assistant/addons · GitHub the fix should be out there already or no?

20

Yes, the update is out.

21

0.7.1 solves it! (refresh updates in HA)

1 Like
22

Yup, seems so…! My dana lock btze seems broken though, still better than everything broken!

23

I directly installed 0.7.1 and now nothing works. Don’t thinkt the fix fixed it… Or is there something else going on here?

2024-09-12T20:45:54.354Z DRIVER   version 13.3.0

2024-09-12T20:45:54.354Z DRIVER   

2024-09-12T20:45:55.375Z CONFIG   version 13.3.0

2024-09-12T20:45:55.764Z CNTRLR   querying Serial API capabilities...

2024-09-12T20:45:55.911Z DRIVER   unexpected response, discarding...

2024-09-12T20:45:55.912Z DRIVER   unexpected response, discarding...

2024-09-12T20:45:55.913Z DRIVER   unexpected response, discarding...

2024-09-12T20:45:55.914Z DRIVER   unexpected response, discarding...

2024-09-12T20:45:55.938Z DRIVER     no handlers registered!

2024-09-12T20:45:59.910Z DRIVER     no handlers registered!

2024-09-12T20:46:05.909Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for a respo

                                  nse from the controller (ZW0200)

                                      at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Drive

                                  r.ts:5814:23)

                                      at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/l

                                  ib/controller/Controller.ts:1125:37)

                                      at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src

                                  /lib/driver/Driver.ts:1521:46)

                                      at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Dr

                                  iver.ts:1322:16)

Error in driver ZWaveError: Failed to initialize the driver: ZWaveError: Timeout while waiting for a response from the controller (ZW0200)

    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5814:23)

    at ZWaveController.queryCapabilities (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:1125:37)

    at Driver.initializeControllerAndNodes (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1521:46)

    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1322:16) (ZW0100)

    at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1342:6) {

  code: 100,

  context: undefined,

  transactionSource: undefined

}

Shutting down

[20:46:05] WARNING: Halt add-on

s6-rc: info: service legacy-services: stopping

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped
24

Interesting, I did not have an issue with any of my 59 Zwave devices after upgrade to 0.7.0. No problems either with 0.7.1

25

Then either 1) you aren’t using a VM, and/or 2) you aren’t using a 500-series controller.

26

I am not on a virtual machine but Home Assistant Blue, also an Aeon stick. Z-Wave collapsed after update 0.7.

Update 0.71 fixed it. Thanks! There was a moment of panick since I have almost 100 Z-Wave devices…

27

I just tried upgrading to 0.71, and it is still broken. Restored from backup to 0.6.2, and everything is working again.

4 Likes
28

For those who have upgraded to 0.7.1 successfully, have you set the “500 series controller soft reset” to disabled?

I’m still running 0.6.2 until I know the correct upgrade path and settings.

29

+1. Something is still not OK. Have 500 controller, upgraded to 0.71, tried every scenario (enabled, disabled, automatic) - no z-wave. Restoring 0.62 fixes.

3 Likes
30

I having a .0.7.1 problem as well

2 Likes
31

I I have to report problems still too. 0.71 fixed the network for most of my devices but not my Devolo Thermostatic Valces. They stop working and report E5 (no connection to controller).

Downgrade to 0.62 and everything is fine.

What to do?

2 Likes