ZMNHUD Timed out while waiting for a response from the node (ZW0201) #6598
Unanswered
toat
asked this question in
Request Support / Investigate Issue
Replies: 1 comment
-
Recent logs in debug mode. |
Beta Was this translation helpful? Give feedback.
0 replies
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?
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
What did you expect to happen instead?
Steps to reproduce the behavior:
Anything else we should know?
I previously open a issue on :
home-assistant/core#104598
Software versions
Driver (node-zwave-js): ...
zwave-js: 12.4.1
Z-Wave JS UI: ...
zwave-js-ui: 9.6.2
Home Assistant Z-Wave Integration: ...
Home Assistant Z-Wave JS Addon: ...
Z-Wave JS UI
Current version: 3.1.0
ioBroker.zwave2 Adapter: ...
![image](https://private-user-images.githubusercontent.com/26632961/295246673-4a02ec4e-9dec-4c8b-8951-2adba49c7600.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIxMzkyNDEsIm5iZiI6MTcyMjEzODk0MSwicGF0aCI6Ii8yNjYzMjk2MS8yOTUyNDY2NzMtNGEwMmVjNGUtOWRlYy00YzhiLTg5NTEtMmFkYmE0OWM3NjAwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI4VDAzNTU0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNjMWFiMGY2OTZlZWJkN2YzMGJmNzg2YjI2YTNlMmQyNDBlY2E0MDhjZDc4OWIyYThmMjRkOTkyOWExNmUzOTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.c_MdLwC1xuFVBkLkk0qiyFSElu_8JW1KcBlH1T86RoY)
If you are using something non-standard, tell us here: ...
Device information
Manufacturer: ...
Model name: ...
Node ID: ...
ZMNHUD
Qubino / Flush Pilot (DIN Version)
Firmware Range: All Versions
Product Manufacturer: 0x0159
Product Identifiers: 0x0004:0x0052
https://devices.zwave-js.io/?jumpTo=0x0159:0x0004:0x0052:0.0
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_2023-11-28.log
zwavejs_current.log
Beta Was this translation helpful? Give feedback.
All reactions