"Value update failed" for Zooz ZEN34 Parameter 5

[The00Dustin]

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?
When I try to set parameter 5 on any ZEN34, I get "Value update failed" as soon as I wake the device.

What did you expect to happen instead?
I expect the value to update.

Steps to reproduce the behavior:

1. Go to any ZEN34 Node
2. Click on 'Configuration v4'
3. Scroll down to Dimmer Control Group: Dimming Duration
4. Set a new value
5. Wake the device
6. See error 'Value update failed'

Anything else we should know?
The driver log I will attach should reflect this issue several times on node 29 with the latest being at 11:33 UTC and once on node 42 at 11:36 UTC. Node 29 is S2 Authenticated, but Node 42 is No Security. I accidentally put Node 42 in include/exclude mode when trying to wake it, so I had to wait for that to end before I could actually wake it after having previously already tried to set the value.

Software versions

Driver (node-zwave-js): 12.3.0

Z-Wave JS UI: 9.3.2

Home Assistant Z-Wave Integration: 1.33.0

Home Assistant Z-Wave JS Addon: 3.0.2

Device information

Manufacturer: Zooz
Model name: ZEN34
Node ID: 029 & 042 were tested

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

zwave-js-ui-store.zip

[The00Dustin]

With some help on Discord, I was able to verify that the byte size was wrong for this parameter. I botched the pull request process, so the commit to fix this is included in #6474 instead of as a separate PR. I could revert that and make the change again, but I have verified that the parameter updates as expected with the file committed to that PR.

[The00Dustin]

I closed the aforementioned PR and this is now fixed in #6546