node-zwave-js icon indicating copy to clipboard operation
node-zwave-js copied to clipboard

Nodes Dropping on firmware 7.17.2

Open daphatty opened this issue 2 years ago โ€ข 2 comments

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within ZWaveJS2MQTT?

NO, my problem is NOT within ZWaveJS2MQTT

Checklist

Describe the bug

What causes the bug?

  • Unknown at this point. Nodes just keep dropping. This issue was present before I upgraded my SiLabs ZST10-700 to the latest firmware (7.17.2) and has persisted through the upgrade.

What do you observe?

  • Dead nodes appearing randomly throughout the day.

What did you expect to happen?

  • No dead nodes

Steps to reproduce the behavior:

  1. Wait for a dead node.
  2. Receive an alert from my Home Assistant Automation that a node has died.
  3. Collect driver debug logs

Device information

Manufacturer: SiLabs Model name: ZST10-700 Node ID in your network: 1

How are you using node-zwave-js?

  • [ ] zwavejs2mqtt Docker image (latest)
  • [ ] zwavejs2mqtt Docker image (dev)
  • [ ] zwavejs2mqtt Docker manually built (please specify branches)
  • [ ] ioBroker.zwave2 adapter (please specify version)
  • [ ] HomeAssistant zwave_js integration (please specify version)
  • [ ] pkg
  • [ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
  • [ ] Manually built from GitHub (please specify branch)
  • [ ] Other (please describe)

Which branches or versions?

version: node-zwave-js branch: zwavejs2mqtt branch:

zwavejs2mqtt: 6.14.1 zwave-js: 9.6.2

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

No, it never worked anywhere

If yes, where did it work?

Ongoing issue.

Attach Driver Logfile

Sorry in advance for the links. Log files are too big to copy/paste.

https://drive.google.com/file/d/1j7p8gK8B62RpsYEFE3llxvuchUViXmVw/view?usp=sharing

and

https://drive.google.com/file/d/1XYG3Gbr7g8qtZS03FhKEZr5TvS6batbj/view?usp=sharing

daphatty avatar Jul 28 '22 00:07 daphatty

๐Ÿ‘‹ Hey @daphatty!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log is required to diagnose most issues.

Please consider uploading a logfile that captures your problem.

zwave-js-bot avatar Jul 28 '22 00:07 zwave-js-bot

Please read my comment here: https://github.com/home-assistant/core/issues/75723#issuecomment-1196765674, especially the hints below the line.

Your issue seems to be exactly the same (except the node numbers). You have a couple of power reporting devices which go crazy and repeat their commands every few ms, flooding the network and jamming the controller. Because in that state they don't get an acknowledgement from the controller, they continue spamming and make the issue worse.

At first glance, those are 65, 66, 33, 34, 35, 36, 51, and likely a few more. These should have insanely high incoming command statistics in zwavejs2mqtt. I'd probably start by shutting off their power for a few seconds to let the network settle.

AlCalzone avatar Aug 02 '22 11:08 AlCalzone

This issue has not seen any recent activity and was marked as "stale ๐Ÿ’ค". Closing for housekeeping purposes... ๐Ÿงน

Feel free to reopen if the issue persists.

zwave-js-assistant[bot] avatar Aug 19 '22 12:08 zwave-js-assistant[bot]