ZMNHVD Qubino / Flush Dimmer 0-10V is missing General Purpose value #6582
Replies: 4 comments 2 replies
-
👋 Hey @vilellic! It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS. Please double-check that you uploaded the correct logfile. If you did, disregard this comment. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
-
What the bot said. Can't help without the correct log. |
Beta Was this translation helpful? Give feedback.
-
Hey @AlCalzone , and sorry for the wrong log. Here is the correct one with interview (node 020) and fiddling with the dimmer value up / down. |
Beta Was this translation helpful? Give feedback.
-
@AlCalzone Could you check this one again? |
Beta Was this translation helpful? Give feedback.
-
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?
ZMNHVD Qubino / Flush Dimmer 0-10V is configured as General Purpose sensor (parameter #1: 5). In previous versions I got the General Purpose reading from the input pins. But it disappeared in some version in the past (maybe within couple of months). I noticed it after updating the new Z-Wave JS UI version.
I use this dimmer to control my house ventilation unit. I can control the ventilation speed with output 0-10V and previously got the reading what was the speed in use (also 0-10V).
I have tried to re-interview it many times with no luck.
I have only this left as evidence that I got the value in the past (in Home Assistant) but now it says it's no longer available and I can't see the parameter in Z-Wave JS UI neither.
Software versions
zwave-js-ui: 9.6.2.6e369a1
zwave-js: 12.4.1
zwave adapter: Razberry in raspberry 4
Device information
Manufacturer: Qubino
Model name: ZMNHVD Flush Dimmer 0-10V
Node ID: 020
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-01-15.log
Beta Was this translation helpful? Give feedback.
All reactions