ZMNHUD Timed out while waiting for a response from the node (ZW0201)

[toat]

The problem

Hi,

I got error each time I sent command to ZMNHUD modules. I got 4 and all have the issue. The value seems to be sent correctly, ZMNHUD is for controlling heater by “pilot wire”, I use it to stop and start the heater.
Sometime the command is executed but the module seems to return to previous value 1s later (I use current clamp to monitor the heater activities) and the entity stay On

We can see on the print screen at 15:28 the issue where the module return to previous state but the entity stay in On

Thank you for your help.

Regards,

What version of Home Assistant Core has the issue?

core-2023.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Z-Wave JS UI

Link to integration documentation on our website

No response

Diagnostics information

zwavejs_current.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[toat]

Hello,

Once again but for Off command :

At 00:48:54, command sent Off but after 1s the module is On and the status of the entity is Off :

Debug log in attachment.
zwavejs_2023-11-28.log

[home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

[toat]

Hi,

Issue occurred twice yesterday, node 99 (always him) at 2023-11-30T18:39:45.556Z and 2023-11-30T21:41:37.590Z.
I add a Range Extender DSD37 but not better
May i try new inclusion of node 99 ?
zwavejs_2023-11-30.log.gz

I also always have "Timed out while waiting for a response from the node" only on ZMNHUD

regards,

[raman325]

have you checked the node statistics? It sounds like there is a routes issue at play here which we can't do anything about

[toat]

Hi,

I see timeout response on my 4 modules, this screen is node 99 :

I tried to resolv timeout by changing priority route and return route, no improvement :

This is the right method ?
Node 5 have no timeout in statistics.

When I test using "diagnose", i have no timeout :

What is strange, I got timeout only on ZMNHUD, other module next to ZMNHUD have no timeout.
Who can i deal with timeout ?

Thank you for your help,

[duylong]

Hi,

I have a similar problem with my Qubino ZMNHJD and a lot of returns "Timed out while waiting for a response from the node (ZW0201)".

As it's in WARNING, it's not too blocking but I'm probably thinking of a bug on these Qubino modules overall. I think we should check directly with the library https://github.com/zwave-js/node-zwave-js to find a solution.

[BUBUsnet]

Same issue with two ZMNHDD in firmware 3.4. Multiple other qubinos with firmware 3.5 are working flawlessly:
"Timed out while waiting for a response from the node (ZW0201)"

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.