GE/Jasco 14942 Device File Error - Incorrect Value Size

[Nick2253]

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

• [X] I have checked the troubleshooting section and my problem is not described there.

• [X] I have read the changelog and my problem was not mentioned there.

Describe the bug

The device file for GE 14294 dimmer switches appears to have the incorrect "valueSize" parameter for the three dimming time parameters.

The 14294 device file refers to the Jasco template file, which refers to the master template file "dimming_timing".

"dimming_timing" has a valueSize parameter of 1, but the 14294 switch requires a valueSize of 2 in order to successfully set the parameter.

This was discussed and confirmed in a thread on the Home Assistant Forum. When manually setting the parameter through the Z-Wave JS UI with the 2-byte size, the 14294 switch accepted the parameter updates. With the specified 1-byte size, it did not.

The attached log shows an attempt at changing parameter 12 "Dimmer Rate (All-on/All-off)" to value "1". The logs show transmit is "OK", but when it queries the devices afterwards, the device reports back the previous value of "3".

Device information

Manufacturer: GE/Jasco Model name: 14294 / ZW3005

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)
• [X] 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?

Zwave JS: 1.28 Driver: 10.22.3

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Yes (please describe)

If yes, where did it work?

No response

Attach Driver Logfile

log.txt

[zwave-js-bot]

👋 Hey @Nick2253!

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 make sure you upload the correct one.

[apella12]

Did some investigation into this. There are two GE/Jasco devices 14294 with identical numbers (Type:Id) (0x4944:0x3038). One version has 1 byte parameters 8, 10, 12 and the other 2 byte. 1 Byte) https://products.z-wavealliance.org/products/1442 2 Byte) https://products.z-wavealliance.org/products/2105

Sometimes the version can be used to separate devices. What version do you have? It would under the version tab in Zwave-js-ui. The concern would be changing it globally might cause problems with the 1 byte owners. Also since there is a workaround with the custom configuration, maybe this isn't worth the effort?

FYI-I also found a couple of other GE/Jasco dimmers with two byte parameters 8, 10, 12. Because of the nature of the parameter (not really changed much) there are others device owners that would have a problem changing the parameter if they tried. AFAICT all the GE/Jasco devices in Zwave-JS are setup with 1 byte.

[AlCalzone]

@JascoProducts can you shed some light onto this?

[Nick2253]

As far as I can tell, the only difference between those two devices is that 2105 is the updated firmware (v5.26). Maybe I'm missing something (especially since I don't understand why they'd have to get recertified for a firmware update), but I think it's just the firmware change. If you check for ZW3010 device, you'd also see two different certifications for two different firmware versions.

If I'm correct, then the only thing we'd need to check on is the firmware version.

[AlCalzone]

That sounds likely