reinterview node fails immediatly after response #7526
Unanswered
TomMalfrere
asked this question in
Request Support / Investigate Issue
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checklist
I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.
Describe the issue
What is happening?
reinterview node 072 fails every time
Device is declared dead while it was just communicating...
I see the interview doing a node ping which fails and when I do a manual ping it passes... (timeout to low?)
node 072 is the most remote node in my network...
What did you expect to happen instead?
retry maybe...
Steps to reproduce the behavior:
click "reinterview node" on device 072
Anything else we should know?
I was using the latest zwave-js-ui docker but went back to zwavejs/zwave-js-ui:9.26.0
I had the issues in both,
Software versions
docker with zwavejs/zwave-js-ui:9.26.0
Driver (node-zwave-js): 13.10.3
Z-Wave JS UI: 9.26.0.47f4c89
sends to mosquitto (latest docker om docker hub) and then to domoticz
Z-Wave Controller (Stick/Dongle/...)
Aeotec z-stick gen 5
FW: v1.0 SDK: v6.51.2
Device information
Manufacturer: Neo
Model name: wallplug NAS-WR01ZE
Node ID: 072
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
zwavejs_2024-12-31.log
Beta Was this translation helpful? Give feedback.
All reactions