Zwave JS Parameters Not Being set for switch

Configuration Z-Wave
1

I’m trying to set a parameter on my GE 14294 Zwave Dimmer, but the parameters are not being applied. I’m using Zwave JS 1.28, driver 10.22.3.

When I try to set, for example, Parameter 8 to value 1, I get a “The Parameter has been updated” confirmation in the UI, but the parameter has not been updated. If I refresh the page, Parameter 8 is still showing as the original value. I get the following logs:

2023-06-06T01:04:09.265Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      167
                                  └─[ConfigurationCCSet]
                                      parameter #:      8
                                      reset to default: false
                                      value size:       1
                                      value format:     UnsignedInteger
                                      value:            1
2023-06-06T01:04:09.276Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-06-06T01:04:09.294Z DRIVER « [REQ] [SendData]
                                    callback id:     167
                                    transmit status: OK
2023-06-06T01:04:10.314Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      168
                                  └─[ConfigurationCCGet]
                                      parameter #: 8
2023-06-06T01:04:10.330Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-06-06T01:04:10.343Z DRIVER « [REQ] [SendData]
                                    callback id:     168
                                    transmit status: OK
2023-06-06T01:04:10.358Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[ConfigurationCCReport]
                                      parameter #: 8
                                      value size:  2
                                      value:       3

It appears that Zwave JS is successfully sending the parameter change, but it’s just not taking on the switch, since the switch returns the previous parameter.

I’m not sure if it’s just this particular switch, since I have a couple other 14294 switches, and they have no issues changing parameters. I’m also able to change the parameters on my Zooz switches without issue.

I tried rebooting the HASS server, excluding/including the switch, excluding/factory reset/including the switch, and it continues to behave this way.

EDIT: I’m now thinking it has something to do with the 14294 switches. Of the 5 currently in use, only 1 responds correctly to Parameter updates. The only difference that I can see is that when I send updates to the one working switch, under ConfigurationCCSet, value size is “2”, whereas all the other (non-working) switches show a value size “1”.

2

The firmware is probably different. No amount of factory resetting will fix it if it’s a bug in the hardware. Only a firmware update. Verify the firmware is up to date on all the devices.

3

I’m running firmware version 5.26 on my 14294’s and it updates fine.

4

All five of my switches are on the same firmware version, 5.29, which is the latest per Jasco firmware site. I’m not sure if I can roll back to 5.26; I’ll try that when I get a second.

Can you check to see if you are updating with a “value size” of 1 or 2 from the Zwave log? I’m almost convinced this is the problem, though I have no idea how to test with a different value, or how to figure out where it’s coming from.

Using the “Download Diagnostics” and comparing the files between the switches, the only difference (other than trivial node number differences) between the working 14942 switch and one of the non-working 14942 switches is valueSize parameter in the three sections for the “Dim Rate Timing”. This is the example from the working switch. Notice the valueSize parameter here is 2. On the non-working switches, the valueSize parameter is 1:

        {
          "endpoint": 0,
          "commandClass": 112,
          "commandClassName": "Configuration",
          "property": 8,
          "propertyName": "Dim Rate Timing (Z-Wave)",
          "ccVersion": 1,
          "metadata": {
            "type": "number",
            "readable": true,
            "writeable": true,
            "description": "Timing of steps or levels",
            "label": "Dim Rate Timing (Z-Wave)",
            "default": 3,
            "min": 1,
            "max": 255,
            "unit": "10ms",
            "valueSize": 2,
            "format": 1,
            "allowManualEntry": true,
            "isFromConfig": true
          },
          "value": 1
        },
5

I see the same problem. Looks like a Z-Wave JS bug. The device file has the value size set as 1 byte, but the device itself reports a 2-byte value when it reports. If you use Z-Wave JS UI and use the manual setting with 2-bytes it works, but the value API that HA uses uses 1-byte.

My 14294 defines a 1-byte param, not 2.

        {
          "endpoint": 0,
          "commandClass": 112,
          "commandClassName": "Configuration",
          "property": 8,
          "propertyName": "Dimmer Rate (Z-Wave)",
          "ccVersion": 1,
          "metadata": {
            "type": "number",
            "readable": true,
            "writeable": true,
            "label": "Dimmer Rate (Z-Wave)",
            "default": 3,
            "min": 1,
            "max": 255,
            "unit": "10ms",
            "valueSize": 1,
            "format": 1,
            "allowManualEntry": true,
            "isFromConfig": true
          },
          "value": 3
        },
6

I created an issue on Github: GE/Jasco 14942 Device File Error - Incorrect Value Size · Issue #5900 · zwave-js/node-zwave-js · GitHub

1 Like
7

By the way, thank you for this. I’ve been meaning to make the switch to Z-Wave JS UI for a while now, and this pushed me to do it.

And finally!! All my switches dim correctly now!! Had to do it the manual way, but it’s not like I’m setting those parameters very often.

8

Well, I should have mentioned, but you can do it in HA too. But ZUI has its benefits.