Z-Wave Controller no longer starting with 0.2.0

[bakgwailo]

Describe the issue you are experiencing

I've found my Z-Wave controller (Aeotec ZW090) no longer comes up with Z-Wave JS 0.2.0, and none of my Z-Wave controls work. Downgrading to 0.1.98, however, solves my problems and everything works OK. With 0.2.0, all of my switches/etc appear on the home page, but, attempted to toggle them results in nothing happening - and a fresh of of the page puts them back in their previous state.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

0.2.0

Steps to reproduce the issue

1. Update to 0.2.0
2. See that Z-Wave switches/integrations no longer function

System Health information

Version | core-2023.10.5
Installation Type | Home Assistant OS
Host Operating System | Home Assistant OS 11.0

Z-Wave JS Addon: 0.2.0 (0.1.98 works)

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

2023-10-24T00:31:52.176Z CNTRLR « [Node 020] ping successful
New client
New client
Client disconnected
Code 1000:
2023-10-24T00:32:26.687Z CNTRLR The controller is unresponsive
2023-10-24T00:32:26.692Z DRIVER Controller missed Send Data callback. Attempting to recover...
2023-10-24T00:32:26.712Z CNTRLR Performing soft reset...
2023-10-24T00:32:27.741Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-10-24T00:32:28.850Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-10-24T00:32:30.964Z CNTRLR Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-10-24T00:32:30.965Z CNTRLR [Node 016] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
Starting logging event forwarder at info level
Stopping logging event forwarder
Starting logging event forwarder at debug level
Stopping logging event forwarder

Additional information

No response

[jozg]

Hello,

The same here, 0.1.98 works and with the 0.2 version it stops reacting, so rollbacked for now,
Glad that i'm not the only one.

Regards

[jozg]

Ok, also with 0.2.1 the same problem for me, here is the log:
2023-10-25T15:17:06.658Z CNTRLR [Node 043] Embedded device config loaded
2023-10-25T15:17:06.673Z CNTRLR [Node 044] Embedded device config loaded
2023-10-25T15:17:06.685Z CNTRLR [Node 045] Embedded device config loaded
2023-10-25T15:17:06.698Z CNTRLR [Node 046] Embedded device config loaded
2023-10-25T15:17:06.711Z CNTRLR [Node 047] Embedded device config loaded
2023-10-25T15:17:06.723Z CNTRLR [Node 048] Embedded device config loaded
2023-10-25T15:17:06.735Z CNTRLR [Node 049] Embedded device config loaded
2023-10-25T15:17:06.750Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2023-10-25T15:17:06.761Z CNTRLR serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
0 ms
2023-10-25T15:17:06.762Z CNTRLR Interview completed
Starting server on 0.0.0.0:3000
2023-10-25T15:17:06.797Z CNTRLR [Node 001] The node is alive.
2023-10-25T15:17:06.799Z CNTRLR [Node 001] The node is ready to be used
2023-10-25T15:17:06.803Z CNTRLR Interviewing nodes and/or determining their status: 17, 11, 31, 18, 5, 16, 35,
2, 4, 47, 43, 46, 44, 49, 41, 48, 45, 37, 13, 14, 30, 34, 29
2023-10-25T15:17:06.804Z CNTRLR » [Node 017] pinging the node...
2023-10-25T15:17:06.906Z CNTRLR » [Node 011] pinging the node...
2023-10-25T15:17:06.908Z CNTRLR » [Node 031] pinging the node...
2023-10-25T15:17:06.912Z CNTRLR » [Node 018] pinging the node...
2023-10-25T15:17:06.914Z CNTRLR » [Node 005] pinging the node...
2023-10-25T15:17:06.916Z CNTRLR » [Node 016] pinging the node...
2023-10-25T15:17:06.919Z CNTRLR » [Node 035] pinging the node...
2023-10-25T15:17:06.921Z CNTRLR » [Node 002] pinging the node...
2023-10-25T15:17:06.924Z CNTRLR » [Node 004] pinging the node...
2023-10-25T15:17:06.928Z CNTRLR [Node 047] The node is asleep.
2023-10-25T15:17:06.930Z CNTRLR [Node 047] The node is ready to be used
2023-10-25T15:17:06.932Z CNTRLR [Node 043] The node is asleep.
2023-10-25T15:17:06.933Z CNTRLR [Node 043] The node is ready to be used
2023-10-25T15:17:06.934Z CNTRLR [Node 046] The node is asleep.
2023-10-25T15:17:06.935Z CNTRLR [Node 046] The node is ready to be used
2023-10-25T15:17:06.936Z CNTRLR [Node 044] The node is asleep.
2023-10-25T15:17:06.938Z CNTRLR [Node 044] The node is ready to be used
2023-10-25T15:17:06.939Z CNTRLR [Node 049] The node is asleep.
2023-10-25T15:17:06.941Z CNTRLR [Node 049] The node is ready to be used
2023-10-25T15:17:06.942Z CNTRLR [Node 041] The node is asleep.
2023-10-25T15:17:06.943Z CNTRLR [Node 041] The node is ready to be used
2023-10-25T15:17:06.944Z CNTRLR [Node 048] The node is asleep.
2023-10-25T15:17:06.945Z CNTRLR [Node 048] The node is ready to be used
2023-10-25T15:17:06.947Z CNTRLR [Node 045] The node is asleep.
2023-10-25T15:17:06.948Z CNTRLR [Node 045] The node is ready to be used
2023-10-25T15:17:06.950Z CNTRLR [Node 037] The node is asleep.
2023-10-25T15:17:06.951Z CNTRLR [Node 037] The node is ready to be used
2023-10-25T15:17:06.953Z CNTRLR [Node 013] Beginning interview - last completed stage: ProtocolInfo
2023-10-25T15:17:06.953Z CNTRLR » [Node 013] pinging the node...
2023-10-25T15:17:06.957Z CNTRLR [Node 014] Beginning interview - last completed stage: ProtocolInfo
2023-10-25T15:17:06.957Z CNTRLR » [Node 014] pinging the node...
2023-10-25T15:17:06.960Z CNTRLR [Node 030] Beginning interview - last completed stage: ProtocolInfo
2023-10-25T15:17:06.960Z CNTRLR » [Node 030] pinging the node...
2023-10-25T15:17:06.962Z CNTRLR [Node 034] Beginning interview - last completed stage: ProtocolInfo
2023-10-25T15:17:06.963Z CNTRLR » [Node 034] pinging the node...
2023-10-25T15:17:06.965Z CNTRLR [Node 029] The node is asleep.
2023-10-25T15:17:06.967Z CNTRLR [Node 029] Beginning interview - last completed stage: ProtocolInfo
2023-10-25T15:17:06.968Z CNTRLR » [Node 029] querying node info...
ZwaveJS server listening on 0.0.0.0:3000
2023-10-25T15:17:07.200Z CNTRLR [Node 017] The node is alive.
2023-10-25T15:17:07.201Z CNTRLR [Node 017] The node is ready to be used
2023-10-25T15:17:07.203Z CNTRLR « [Node 017] ping successful
2023-10-25T15:17:07.269Z CNTRLR [Node 011] The node is alive.
2023-10-25T15:17:07.270Z CNTRLR [Node 011] The node is ready to be used
2023-10-25T15:17:07.271Z CNTRLR « [Node 011] ping successful
2023-10-25T15:17:07.300Z CNTRLR [Node 031] The node is alive.
2023-10-25T15:17:07.301Z CNTRLR [Node 031] The node is ready to be used
2023-10-25T15:17:07.304Z CNTRLR « [Node 031] ping successful
2023-10-25T15:17:07.336Z CNTRLR [Node 018] The node is alive.
2023-10-25T15:17:07.337Z CNTRLR [Node 018] The node is ready to be used
2023-10-25T15:17:07.339Z CNTRLR « [Node 018] ping successful
2023-10-25T15:17:07.370Z CNTRLR [Node 005] The node is alive.
2023-10-25T15:17:07.370Z CNTRLR [Node 005] The node is ready to be used
2023-10-25T15:17:07.372Z CNTRLR « [Node 005] ping successful
2023-10-25T15:17:07.401Z CNTRLR [Node 016] The node is alive.
2023-10-25T15:17:07.401Z CNTRLR [Node 016] The node is ready to be used
2023-10-25T15:17:07.403Z CNTRLR « [Node 016] ping successful
2023-10-25T15:17:07.432Z CNTRLR [Node 035] The node is alive.
2023-10-25T15:17:07.432Z CNTRLR [Node 035] The node is ready to be used
2023-10-25T15:17:07.433Z CNTRLR « [Node 035] ping successful
2023-10-25T15:17:07.488Z CNTRLR [Node 002] The node is alive.
2023-10-25T15:17:07.489Z CNTRLR [Node 002] The node is ready to be used
2023-10-25T15:17:07.490Z CNTRLR « [Node 002] ping successful
2023-10-25T15:17:07.522Z CNTRLR [Node 004] The node is alive.
2023-10-25T15:17:07.523Z CNTRLR [Node 004] The node is ready to be used
2023-10-25T15:17:07.526Z CNTRLR « [Node 004] ping successful
2023-10-25T15:17:11.644Z CNTRLR [Node 013] The node did not respond after 1 attempts, it is presumed dead
2023-10-25T15:17:11.646Z CNTRLR [Node 013] The node is dead.
2023-10-25T15:17:11.649Z CNTRLR [Node 013] ping failed: The node did not acknowledge the command (ZW0204)
2023-10-25T15:17:11.649Z CNTRLR » [Node 013] querying node info...
2023-10-25T15:17:11.649Z CNTRLR » [Node 013] pinging the node...
New client
2023-10-25T15:17:42.173Z CNTRLR The controller is unresponsive
2023-10-25T15:17:42.175Z DRIVER Controller missed Send Data callback. Attempting to recover...
2023-10-25T15:17:42.208Z CNTRLR Performing soft reset...
2023-10-25T15:17:43.219Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-10-25T15:17:44.325Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-10-25T15:17:46.431Z CNTRLR Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-10-25T15:17:46.432Z CNTRLR [Node 014] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2023-10-25T15:17:46.432Z CNTRLR » [Node 014] querying node info...

[hhamer78]

I have a comparable issue; with the upgrade to 0.2.0. Once or twice a day buttons (on user interface, app, webpage) don't react for ZWave devices. The devices are still alive; no complaints from HA. It also seems data is coming in fine (for example power metering).

I investigated and can't find anything in the log files when this happends. I can't find any "button pushed" or whatever trigger. If I would find that and it would give some time-out I would understand it in a way .... but I even don't see anything triggering. Restarting the Zwave-JS add-on solves the issue.

[SergeyAnokhin]

Hello,

Same for me with EVERSPRING Z-Wave (Z-Wave+). Rollbacked to 1.98
sensor.00_zwave_usb_stick_status -> 'unresponsive'

2023-10-27T20:34:47.008Z DRIVER   unexpected response, discarding...
New client
2023-10-27T20:35:14.220Z CNTRLR   The controller is unresponsive
2023-10-27T20:35:14.221Z DRIVER   Controller missed Send Data callback. Attempting to recover...
2023-10-27T20:35:14.242Z CNTRLR   The controller does not support soft reset or the soft reset feature has been 
                                  disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment va
                                  riable.
2023-10-27T20:35:14.243Z CNTRLR   [Node 052] ping failed: Timeout while waiting for a callback from the controll
                                  er (ZW0200)
2023-10-27T20:35:22.431Z DRIVER     no handlers registered!
2023-10-27T20:35:35.063Z CNTRLR « [Node 020] received wakeup notification
2023-10-27T20:35:35.063Z CNTRLR   [Node 020] The node is now awake.
2023-10-27T20:35:35.317Z CNTRLR » [Node 020] Sending node back to sleep...
2023-10-27T20:35:59.105Z CNTRLR « [Node 035] received wakeup notification
2023-10-27T20:35:59.106Z CNTRLR   [Node 035] The node is now awake.
2023-10-27T20:35:59.107Z CNTRLR   [Node 035] expects some queries after wake up, so it shall receive
2023-10-27T20:35:59.107Z CNTRLR   [Node 035] compat query "Battery"::get()
2023-10-27T20:36:09.116Z CNTRLR   [Node 035] error during API call: The message has expired (ZW0215)
2023-10-27T20:36:57.076Z CNTRLR « [Node 033] received wakeup notification
2023-10-27T20:36:57.076Z CNTRLR   [Node 033] The node is now awake.
2023-10-27T20:36:57.077Z CNTRLR   [Node 033] expects some queries after wake up, so it shall receive
2023-10-27T20:36:57.077Z CNTRLR   [Node 033] compat query "Battery"::get()
2023-10-27T20:37:07.079Z CNTRLR   [Node 033] error during API call: The message has expired (ZW0215)
2023-10-27T20:37:12.041Z CNTRLR « [Node 009] received wakeup notification
2023-10-27T20:37:12.041Z CNTRLR   [Node 009] The node is now awake.
2023-10-27T20:37:12.292Z CNTRLR » [Node 009] Sending node back to sleep...

2023-10-27T20:42:59.335Z CNTRLR   [Node 063] The node is alive.
2023-10-27T20:42:59.335Z CNTRLR   [Node 063] The node is ready to be used
2023-10-27T20:42:59.336Z CNTRLR « [Node 063] ping successful
2023-10-27T20:43:12.635Z DRIVER   unexpected response, discarding...
New client
New client
Client disconnected
Code 1000: 
2023-10-27T20:43:39.845Z CNTRLR   The controller is unresponsive
2023-10-27T20:43:39.846Z DRIVER   Controller missed Send Data callback. Attempting to recover...
2023-10-27T20:43:39.850Z CNTRLR   The controller does not support soft reset or the soft reset feature has been 
                                  disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment va
                                  riable.
2023-10-27T20:43:39.851Z CNTRLR   [Node 052] ping failed: Timeout while waiting for a callback from the controll
                                  er (ZW0200)
2023-10-27T20:43:48.056Z DRIVER     no handlers registered!
2023-10-27T20:43:50.056Z CNTRLR « [Node 036] received wakeup notification
2023-10-27T20:43:50.060Z CNTRLR   [Node 036] The node is now awake.
2023-10-27T20:43:50.062Z CNTRLR   [Node 036] expects some queries after wake up, so it shall receive

Thanks

[edddeduck]

Similar issue seen on my setup - "UZB by Z-Wave.Me" I have Firmware: 5.2

2023-11-03T00:26:16.135Z CNTRLR   The controller is unresponsive
2023-11-03T00:26:16.136Z DRIVER   Controller missed Send Data callback. Attempting to recover...
2023-11-03T00:26:16.197Z CNTRLR   The controller does not support soft reset or the soft reset feature has been disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment variable.

After that the plugin will shutdown more logs available if needed.

[jozg]

Ok, i updated my gen5 stick to the 1.02 firmware, and the problem is solved. I first make a backup with the backup tool, so i haven't had to pair again the devices. more info zwave-js/node-zwave-js#6341
Update can be download at https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update
And the backup tool https://aeotec.freshdesk.com/support/solutions/articles/6000108806-z-stick-gen5-backup-software

Regards,

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.