Help w Modify Config Parameter on GE/Jasco Dimmer

I have a new Jasco/Enbrighten/GE Dimmer model ZW3012 (no neutral required). It is not considered officially supported by Indigo, but basic functionality does work.

I have configured the dimmer to be in "Switch Mode", which means it should act like an On/Off switch (only 0 & 100 values). I did this locally using the paddle.

The problem is that the device internally has a delay of about 3 seconds from when you press the down paddle, to when the light actually goes off. Same delay when I send an Off command from Indigo.

I found some documentation snippets (below) on how to reconfigure this with a shorter time, or at least I think.

So first I used the "Modify Configuration Parameter" in Indigo to read current values of all the Parameters, and strangely they are all 0, which doesn't seem right, since 0 isn't even a valid value for some.

Then I decided to write a value of 1 for Parameters 8, 10, and 12 just for the fun of it. And logs show parameter was changed, but when I read them again, they are all back to 0, and of course the device behaves the same as before.

Just wondering if anyone else had any experience with this?

**************************

LED LIGHT
When shipped from the factory, the LED is set to turn ON when the connected light is turned OFF. This is the default setting and can be changed if your primary controller supports the node configuration function. To make the LED turn ON when the light is turned ON, change parameter 3’s value to “1”. To turn the LED OFF at all times, change parameter 3’s value to 2.

Parameter No: 3
Length: 1 Byte
Valid Values = 0, 1 or 2 (default 0)
Invert Switch
If the switch is accidentally installed upside down with “On” at the bottom and “Off” at the top, the default On/Off rocker settings can be reversed by changing parameter 4’s value to “1”.

Parameter No: 4
Length: 1 Byte
Valid Values = 0 or 1 (default 0)
Dim Rate Adjustments
Both the number of steps (or levels) that the dimmer will change and the timing of the steps can be modified to suit personal preferences. The timing of the steps can be adjusted in 10-millisecond intervals. As an example, the default setting for parameter 8 is “3”. This means that the lighting level will change every 30 milliseconds when the Dim Command is received. A value of 255 would mean that the level would change every 2.55 seconds. Combined, the two parameters allow dim rate adjustments from 10 milliseconds to 4.2 minutes to go from maximum-to-minimum or minimum-to-maximum brightness levels.

1. When Receiving a Z-Wave Dim Command
Parameter 7 (number of steps or levels)
Parameter 8 (timing of the steps)
Length: 1 Byte
Valid Values:
Parameter 7 (default = 1) Valid Values: 1-99
Parameter 8 (default = 3) Valid Values: 1-255

2. Manual Control Dimming (pressing the Dimmer’s button)
Parameter 9 (number of steps or levels)
Parameter 10 (timing of the steps)
Length: 1 Byte
Valid Values:
Parameter 9 (default = 1) Valid Values: 1-99
Parameter 10 (default = 3) Valid Values: 1-255

3. When Receiving an All-On or All-Off Command
Parameter 11 (number of steps or levels)
Parameter 12 (timing of the steps)
Length: 1 Byte
Valid Values:
Parameter 11 (default = 1) Valid Values: 1-99
Parameter 12 (default = 3) Valid Values: 1-255

Alternatively, the LED default setting can also be changed at the switch.
To disable the LED indicator:
Press the "ON" switch 3 times successively
Press the "OFF" switch 1 time
Use this same process to restore the original LED setting.

[matt (support)]

Re-sync the module in Indigo and copy/paste the Event Log window results into a reply for me. It is strange it is returning all 0's for any configuration parameter you try to read, so also include a log snippet of you trying to read, set, and read again a parameter that should be valid.

Sorry for taking so long to reply.

I did some more research and some tinkering, and I found all sorts of documentation on supported parameters, some of which should apply to my device, but it seems they have changed things between iterations.

Long story short, I sent requests to the device for every parameter from 1 to I think maybe 200? and found what is/is not supported. And unfortunately on the newest generation of device, the delay I want to change does not appear to be a parameter that can be modified.

I ordered a no-neutral Homeseer device to see if that is better.

I'm having the same issue with a Enbrighten Smart Light Dimmer (46203), firmware 5.54.
It's possible that the ramp parameters can't be modified on this model either, but I thought I would give it a shot. Below is the log when I re-synced the device and also the read, set and read snippet of the log...

Z-Wave Syncing - started for "Bonus Room Lights-Main"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 04 01 01 7D
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5E (no inbound callback)
Z-Wave Debug . . getNodeNeighbors: nodeId 004, neighbors: - none -
Z-Wave Syncing - retrieved module neighbors list: - none -
Z-Wave Syncing - assigning return route to "004 - Bonus Room Lights-Main"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 04 01 B9
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 004, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 04 24 98 21
Z-Wave Debug RCVD nodeInfoFrame: 01 18 00 49 84 04 12 04 11 01 5E 26 85 59 86 72 55 5A 73 5B 9F 6C 70 22 7A 84
Z-Wave Debug . . nodeInfoFrame: node 004, combined class list: 20v1 26v1 27v1 5Ev1 85v1 59v1 86v1 72v1 55v1 5Av1 73v1 5Bv1 9Fv1 6Cv1 70v1 22v1 7Av1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 04 02 72 04 25 99 29
Z-Wave Debug RCVD requestManufactureInfo: 01 18 00 13 99 00 00 02 00 C9 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A7 (node ACK)
Z-Wave Debug RCVD requestManufactureInfo: txTransmitTicks 2, txHopCount 0, txRSSIs 201 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 04 08 72 05 00 63 49 44 32 35 3F
Z-Wave Debug . . requestManufactureInfo: node 004, manufacturerId 0063, productId 49443235
Z-Wave Debug . . requestManufactureInfo: General Electric, Enbrighten Smart Light Dimmer (46203)
Z-Wave Syncing - retrieved manufacture and model names: General Electric - 0063, Enbrighten Smart Light Dimmer (46203) - 49443235
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 04 02 86 11 25 9A CB
Z-Wave Debug RCVD requestVersInfoGen: 01 18 00 13 9A 00 00 02 00 C9 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A4 (node ACK)
Z-Wave Debug RCVD requestVersInfoGen: txTransmitTicks 2, txHopCount 0, txRSSIs 201 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug RCVD requestVersInfoGen: 01 0F 00 04 00 04 09 86 12 03 06 04 05 36 FF 00 7A
Z-Wave Debug . . requestVersInfoGen: node 004, protoVers 6.04, appVers 5.54
Z-Wave Syncing - retrieved protocol version 6.04, app version 5.54
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 04 03 86 13 26 25 9B EC
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 18 00 13 9B 00 00 02 00 C4 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A8 (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: txTransmitTicks 2, txHopCount 0, txRSSIs 196 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 04 04 86 14 26 04 8E
Z-Wave Debug . . requestVersInfoCmdClass: node 004, class command 26 using version 4
Z-Wave Debug . . requestVersInfoCmdClass: node 004, combined class list: 20v1 26v4 27v1 5Ev1 85v1 59v1 86v1 72v1 55v1 5Av1 73v1 5Bv1 9Fv1 6Cv1 70v1 22v1 7Av1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Dimmable Power Switch (04 : 11 : 01, base 26)
Z-Wave Syncing - retrieved command classes: 20v1 26v4 27v1 5Ev1 85v1 59v1 86v1 72v1 55v1 5Av1 73v1 5Bv1 9Fv1 6Cv1 70v1 22v1 7Av1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 04 02 85 05 25 9C DA
Z-Wave Debug RCVD requestAssociationGroupCount: 01 18 00 13 9C 00 00 03 00 C9 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A3 (node ACK)
Z-Wave Debug RCVD requestAssociationGroupCount: txTransmitTicks 3, txHopCount 0, txRSSIs 201 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 04 03 85 06 03 B3
Z-Wave Debug . . requestAssociationGroupCount: node 004, group count: 3
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 04 03 85 02 01 25 9D DF
Z-Wave Debug RCVD requestAssociations: 01 18 00 13 9D 00 00 02 00 C4 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 AE (node ACK)
Z-Wave Debug RCVD requestAssociations: txTransmitTicks 2, txHopCount 0, txRSSIs 196 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 04 06 85 03 01 05 00 01 B2
Z-Wave Debug . . requestAssociations: node 004, group: 1, num associations: 1, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 004, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 04 03 85 02 02 25 9E DF
Z-Wave Debug RCVD requestAssociations: 01 18 00 13 9E 00 00 08 00 C4 7F 7F 7F 7F 00 00 03 00 00 00 00 03 02 00 00 A4 (node ACK)
Z-Wave Debug RCVD requestAssociations: txTransmitTicks 8, txHopCount 0, txRSSIs 196 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 2, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug . . requestAssociations: requeuing 1 unsolicited packets
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 04 05 85 03 02 05 00 BF
Z-Wave Debug . . requestAssociations: node 004, group: 2, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 004, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 04 03 85 02 03 25 9F DF
Z-Wave Debug RCVD requestAssociations: 01 18 00 13 9F 00 00 09 00 CA 7F 7F 7F 7F 01 01 03 00 00 00 00 02 03 00 00 AA (node ACK)
Z-Wave Debug RCVD requestAssociations: txTransmitTicks 9, txHopCount 0, txRSSIs 202 127 127 127 127, txACKChannelNum 1, txLastTxChannelNum 1, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 2, txRouteTries 3, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug . . requestAssociations: requeuing 1 unsolicited packets
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 04 05 85 03 02 05 00 BF
Z-Wave Debug . . requestAssociations: node 004, group: 2, num associations: 0, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 004, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 04 05 85 03 03 05 00 BD
Z-Wave Syncing - complete

Read Set snippet:

Z-Wave Debug SENT readConfigValue: 01 0A 00 13 04 03 70 05 0C 25 8F 32
Z-Wave Debug RCVD readConfigValue: 01 18 00 13 8F 00 00 02 00 C3 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 BB (node ACK)
Z-Wave Debug RCVD readConfigValue: txTransmitTicks 2, txHopCount 0, txRSSIs 195 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 04 05 70 06 0C 01 00 45
Z-Wave Debug . . requestConfigVal: node 004, parm index 12, value 0 (size 1)
Z-Wave retrieved parameter 12 value: 0 (size 1)
Z-Wave Debug SENT setConfigVal: 01 0C 00 13 04 05 70 04 0C 01 01 25 90 2C
Z-Wave Debug RCVD setConfigVal: 01 18 00 13 90 00 00 02 00 C9 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 AE (node ACK)
Z-Wave Debug RCVD setConfigVal: txTransmitTicks 2, txHopCount 0, txRSSIs 201 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave device "Bonus Room Lights-Main" parameter 12 changed to 1
Z-Wave Debug SENT readConfigValue: 01 0A 00 13 04 03 70 05 0C 25 91 2C
Z-Wave Debug RCVD readConfigValue: 01 18 00 13 91 00 00 02 00 C9 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 AF (node ACK)
Z-Wave Debug RCVD readConfigValue: txTransmitTicks 2, txHopCount 0, txRSSIs 201 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 04 05 70 06 0C 01 00 4F
Z-Wave Debug . . requestConfigVal: node 004, parm index 12, value 0 (size 1)
Z-Wave retrieved parameter 12 value: 0 (size 1)

Jan 19, 2023 at 3:02:06 PM
Z-Wave Debug SENT readConfigValue: 01 0A 00 13 04 03 70 05 04 25 92 27
Z-Wave Debug RCVD readConfigValue: 01 18 00 13 92 00 00 03 00 C3 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A7 (node ACK)
Z-Wave Debug RCVD readConfigValue: txTransmitTicks 3, txHopCount 0, txRSSIs 195 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 04 05 70 06 04 01 00 4D
Z-Wave Debug . . requestConfigVal: node 004, parm index 4, value 0 (size 1)
Z-Wave retrieved parameter 4 value: 0 (size 1)
Z-Wave Debug SENT setConfigVal: 01 0C 00 13 04 05 70 04 04 01 02 25 93 24
Z-Wave Debug RCVD setConfigVal: 01 18 00 13 93 00 00 02 00 C3 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A7 (node ACK)
Z-Wave Debug RCVD setConfigVal: txTransmitTicks 2, txHopCount 0, txRSSIs 195 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave device "Bonus Room Lights-Main" parameter 4 changed to 2
Z-Wave Debug SENT readConfigValue: 01 0A 00 13 04 03 70 05 04 25 94 21
Z-Wave Debug RCVD readConfigValue: 01 18 00 13 94 00 00 02 00 C3 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A0 (node ACK)
Z-Wave Debug RCVD readConfigValue: txTransmitTicks 2, txHopCount 0, txRSSIs 195 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 04 05 70 06 04 01 00 4D
Z-Wave Debug . . requestConfigVal: node 004, parm index 4, value 0 (size 1)
Z-Wave retrieved parameter 4 value: 0 (size 1)
Z-Wave Debug SENT readConfigValue: 01 0A 00 13 04 03 70 05 04 25 95 20
Z-Wave Debug RCVD readConfigValue: 01 18 00 13 95 00 00 02 00 C3 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A1 (node ACK)
Z-Wave Debug RCVD readConfigValue: txTransmitTicks 2, txHopCount 0, txRSSIs 195 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 04 05 70 06 04 01 00 42
Z-Wave Debug . . requestConfigVal: node 004, parm index 4, value 0 (size 1)
Z-Wave retrieved parameter 4 value: 0 (size 1)
Z-Wave Debug SENT readConfigValue: 01 0A 00 13 04 03 70 05 0F 25 96 28
Z-Wave Debug RCVD readConfigValue: 01 18 00 13 96 00 00 02 00 C9 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 A8 (node ACK)
Z-Wave Debug RCVD readConfigValue: txTransmitTicks 2, txHopCount 0, txRSSIs 201 127 127 127 127, txACKChannelNum 0, txLastTxChannelNum 0, txRouteSchemeState 3, txRoute 0 0 0 0, txRouteSpeed 3, txRouteTries 1, txLastFailedLinkFrom 0, txLastFailedLinkTo 0
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 04 05 70 06 0F 01 00 4C
Z-Wave Debug . . requestConfigVal: node 004, parm index 15, value 0 (size 1)
Z-Wave retrieved parameter 15 value: 0 (size 1)

Sorry for taking so long to reply.

I did some more research and some tinkering, and I found all sorts of documentation on supported parameters, some of which should apply to my device, but it seems they have changed things between iterations.

Long story short, I sent requests to the device for every parameter from 1 to I think maybe 200? and found what is/is not supported. And unfortunately on the newest generation of device, the delay I want to change does not appear to be a parameter that can be modified.

I ordered a no-neutral Homeseer device to see if that is better.

I have several of these. Thanks for looking into the various parameters. Could you post your findings?