search

zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript
https://zwave-js.github.io/node-zwave-js/
MIT License
750 stars 601 forks source link

Trouble healing with 500 series #3958

Closed justindthomas closed 2 years ago

justindthomas commented 2 years ago

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

I recently switched back to using an Aeotec Z-Stick 5+ (instead of the 7 I've been using for a few months). I used the migration tool that @AlCalzone has been working on to shift back.

I'm having some trouble completing a full network heal, though. About 50% of my nodes do okay, but the others fail both when triggered individually and when done as part of a network heal. Although one that was problematic just made a liar out of my and healed okay while I was trying to capture a log. I moved to another, and it failed. So the behavior seems to be inconsistent. The driver logs are attached.

I do have one node near the center of my network that is currently offline (I inadvertently unplugged its power and am not nearby to plug it back in). The interface seems to have recognized that it's offline and it is now marked to "skip." I thought I could just heal around it (honestly, I'd rather that node not be heavily relied on) - but could its existence be causing this issue?

Device information

Manufacturer: Aeotec Model name: Z-Stick 5+ Node ID in your network: 13

How are you using node-zwave-js?

Which branches or versions?

version: node-zwave-js branch: 8.9.0-beta.1 zwavejs2mqtt branch: 0.32.1

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Don't know, this is a new device

If yes, where did it work?

No response

Attach Driver Logfile

zwave_js.log

justindthomas commented 2 years ago

Further information: doing a Soft Reset on the controller seems to help. I was able to heal 6 stubborn nodes before it started failing again with the "no response from controller" errors.

I'm not confident about the firmware version on my Z-Stick 5+. ZwaveJS2MQTT reports 1.2, but it looks like the latest from Aeotec is 1.02 and it was only released this month (and I definitely haven't updated it since then).

jmgiaever commented 2 years ago

Upgrade to Z2M 6.2.0 that doesn't include beta.1. That was released by a mistake.

justindthomas commented 2 years ago

Okay, thanks. I'll work on that. I try to update as soon as new releases are made available through the official integrations, but I'll figure out how to accelerate that locally

jmgiaever commented 2 years ago

Try to use the master branch. I'm not using docker so not sure how it works. But I know the master tag has it. :)

AlCalzone commented 2 years ago

Closing for now - feel free to reopen if the issue persists in v8.9.2.