node-zwave-js: Wrong parameter Implementation for "ZW ESJ 300"

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

• 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.

Describe the bug

What causes the bug? Wrong config file, parameter 0 is wrongly implemented. What do you observe? The permissible values are too small, the configuration of the running time for the device is done differently than described. What did you expect to happen? Allow to enter the required value for configuration but with current config file not possible.

To solve, either allow bigger values to be entered and let the user “calculate” the required number or implement four bitmask options which will set all four values. I used the device extensively on an old Vera Lite where setting the parameter in dec or hex works fine. When migrating one device to HA in zwaveJS, I could even see that parameter 0 is configured with value 30125 (decimal) which is “illegal” as per current device file.

I am not an expert, I try to explain how it should be. The parameter 0 is configuring the runtime up and down as a bitmask with 16bits (?) like 1000111001110011. In the device manual it is explained using hex (0x) values but I figured it is just a fancier way of saying bitmask. I tried to write a corrected version for the parameters but not sure if this is correct as I never coded anything. It is attached. 0x0064.txt

Otherwise I am happy to explain how it should work and provide the original manual. Thanks

Device information

Manufacturer: Reitz-Group.de Model name: ZW ESJ 300 “manufacturer”: “Reitz-Group.de”, “manufacturerId”: “0x0064”, “label”: “ZW ESJ 300”, “description”: “Duwi ZW ESJ 300 Blind Control”, here

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

version: node-zwave-js branch: zwave-js-ui branch:

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

No, it never worked anywhere

If yes, where did it work?

No response

Attach Driver Logfile

I don’t think this would serve any purpose as it is a configuration file problem.