Yeah, but it wasn’t a new change for this version of the add-on compared to the previous version.
and after upgrade to 0.7.0 still same error:
· AddPrimaryController (0x4d)
· AssignPriorityReturnRoute (0x4f)
· SetLearnMode (0x50)
· AssignSUCReturnRoute (0x51)
· RequestNetworkUpdate (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· SendSUCNodeId (0x57)
· AssignPrioritySUCReturnRoute (0x58)
· ExploreRequestInclusion (0x5e)
· ExploreRequestExclusion (0x5f)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· FirmwareUpdateNVM (0x78)
· GetRoutingInfo (0x80)
· LockUnlockLastRoute (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· FUNC_ID_APPLICATION_SLAVE_COMMAND_HANDLER (0xa1)
· undefined (0xb4)
· EnableWatchdog500 (0xb6)
· DisableWatchdog500 (0xb7)
· KickWatchdog500 (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· GetLibrary (0xbd)
· SendTestFrame (0xbe)
· GetProtocolStatus (0xbf)
· FUNC_ID_ZW_SET_PROMISCUOUS_MODE (0xd0)
· FUNC_ID_PROMISCUOUS_APPLICATION_COMMAND_HANDLER (0xd1)
· StartWatchdog (0xd2)
· StopWatchdog (0xd3)
· SetMaximumRoutingAttempts (0xd4)
· undefined (0xee)
· undefined (0xef)
2024-09-12T15:28:51.882Z CNTRLR querying additional controller information...
2024-09-12T15:28:51.990Z CNTRLR received additional controller information:
Z-Wave API version: 8 (legacy)
Z-Wave chip type: ZW050x
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
Z-Wave Classic nodes: 1, 2, 3, 4, 5, 7, 8, 9, 10, 11, 12, 15, 16, 17,
18, 19, 20, 21, 22, 24, 26, 28, 35, 39, 45, 47, 48, 49, 51, 53, 54, 55, 59, 60
, 61, 62, 63, 64, 65, 66, 67, 70, 71, 73, 74, 75, 76, 78, 82, 83, 84, 89, 91,
94, 95, 99, 100, 101, 104, 105, 114, 115, 116, 120, 122, 123, 129, 130, 133, 1
35, 136
2024-09-12T15:28:51.990Z CNTRLR querying version info...
2024-09-12T15:28:51.997Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 6.07
2024-09-12T15:28:51.998Z CNTRLR querying protocol version info...
2024-09-12T15:28:52.002Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 6.7.0
appl. framework build no.: 97
2024-09-12T15:28:52.003Z CNTRLR querying controller capabilities...
2024-09-12T15:28:52.008Z CNTRLR received controller capabilities:
controller role: Primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2024-09-12T15:28:52.008Z CNTRLR querying serial API setup capabilities...
2024-09-12T15:28:52.013Z CNTRLR supported serial API setup commands:
· GetSupportedCommands
· SetTxStatusReport
· SetPowerlevel
· GetPowerlevel
· GetMaximumPayloadSize
2024-09-12T15:28:52.013Z CNTRLR querying max. payload size...
2024-09-12T15:28:52.016Z CNTRLR maximum payload size: 46 bytes
2024-09-12T15:28:52.017Z CNTRLR supported Z-Wave features:
· SmartStart
2024-09-12T15:28:52.017Z CNTRLR Performing soft reset...
2024-09-12T15:28:52.021Z CNTRLR Waiting for the controller to reconnect...
2024-09-12T15:28:53.523Z CNTRLR Waiting for the Serial API to start...
2024-09-12T15:28:58.525Z CNTRLR Did not receive notification that Serial API has started, checking if it respo
nds...
2024-09-12T15:28:58.527Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-09-12T15:28:58.628Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-09-12T15:28:59.731Z CNTRLR Serial API did not respond, trying again in 2 seconds...
2024-09-12T15:29:01.734Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-09-12T15:29:01.835Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-09-12T15:29:02.937Z CNTRLR Serial API did not respond, trying again in 5 seconds...
2024-09-12T15:29:07.941Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-09-12T15:29:08.042Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-09-12T15:29:09.144Z CNTRLR Serial API did not respond, trying again in 10 seconds...
Either the setting did not apply, or it’s being ignored.
How to proceed then?
the same one as you
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
FYI, the add-on is already being updated to fix this. https://github.com/home-assistant/addons/pull/3760
1 Like
Thank you!
Read the posts above your comment.
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?
Yes, the update is out.
0.7.1 solves it! (refresh updates in HA)
1 Like
Yup, seems so…! My dana lock btze seems broken though, still better than everything broken!
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
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
Then either 1) you aren’t using a VM, and/or 2) you aren’t using a 500-series controller.
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…
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
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.