Unable to detect that stick doesn't support soft-reset #7218
Answered
by
kpine
crawford
asked this question in
Request Support / Investigate Issue
-
Checklist
Describe the issueAfter updating zwave-js-server from 1.28.0 to 1.35.0, I noticed that the server continually crashes after attempting to soft-reset the stick. Here are the logs from one of those cycles: The older version didn't bother with the soft-reset, however, logging this message instead: "Soft reset is enabled through config, but this stick does not support it." I disabled soft-reset in the config but I figured you'd want to know about the regression. Software versionsNo response Z-Wave Controller (Stick/Dongle/...)No response Device informationNo response Checklist
Upload LogfileNo response |
Beta Was this translation helpful? Give feedback.
Answered by
kpine
Oct 6, 2024
Replies: 2 comments 6 replies
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
Take a look at the migration guide for v12, there's a section that covers this: https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating/v12?id=removed-the-controller39s-supportssoftreset-property
Your controller currently identifies as: which is not in the list of known problematic controllers. I can't find this list on the documentation, so here's the source: node-zwave-js/packages/zwave-js/src/lib/driver/Driver.ts Lines 2553 to 2579 in 7198eb3 So disabling soft-reset by config is expected in this case. If whatever controller you're using (it would help to mention which one) universally doesn't support soft-reset, perhaps it could be added to the list of problem controllers. In that case you'll probably need to provide more information, I would add the full driver debug logs (yours are not debug) like the bot asked for. The message in the old log is based on the previous behavior where the driver auto-detected controllers that failed soft-reset and it disabled them and cached that result (unless your controller decided to changes IDs). Per the migration guide, the auto-behavior was removed in v12. |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Thanks for the quick reply. I suspected this might be related to that change to the soft-reset logic. Unfortunately, I can't easily get the debug logs since I've rolled back (and will remain pinned) to 1.28.0, but I think the question has been answered anyway. For what it's worth, this is how the device reports itself over USB: |
Beta Was this translation helpful? Give feedback.
-
|
Is it really an Aeotec Z-Stick Gen5 though? I think several controllers match that USB ID because of the USB serial chip. The firmware version doesn't match a Gen5. There are some additional notes on soft-reset solutions at #6341. |
Beta Was this translation helpful? Give feedback.
-
|
Good point! Actually, it is not. It's a Nortek HUSBZB-1. The soft reset is an issue for my setup because it takes a long time for this device to recover. I've got udev rules in place to ensure that it has a consistent name, so that's not an issue; it reconnects just fine. But the frequent soft resets result in lots of perceived latency when using the system (there's a decent chance the hub is in the process of resetting, or whatever it's doing). The ideal solution would be to replace the hub with one that an actual human has used before and can vouch for, but sifting through the mountains of bot spam across the Internet these days has made that tricky. |
Beta Was this translation helpful? Give feedback.
-
|
Huh, interesting. I thought the Nortek had a different USB ID since it's a whole different stack than the other 500-series. Not that it matters. I haven't heard any issues with soft-reset for that device until now. Any 700 or 800 series supports soft-reset unconditionally. The soft-reset does not result in a USB reset, unlike the 500-series. |
Beta Was this translation helpful? Give feedback.
-
|
Never heard of that issue before. Still, your best bet is to just disable soft-reset in the addon options, or if you're using zwave-js-server standalone, in the server config. |
Beta Was this translation helpful? Give feedback.
Answer selected by
crawford
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Take a look at the migration guide for v12, there's a section that covers this: https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating/v12?id=removed-the-controller39s-supportssoftreset-property
Your controller currently identifies as: