im glad you are somewhere better with device B, there is nowhere other than where the slider is in the device type that sends a dimmer value in the device type.
Looking at your results the only difference between device A & B is parameter 8 which is 3 on device a but 1 on device B. I suggest you change this to match device A
I cant exclude either that there isn’t an undocumented parameter, in which case you will be shooting in the dark
I’ve got to be honest though actually envisaging how these parameters should relate to the lighting is a bit lost on me. Im not sure I can help further. Maybe @JDRoberts could assist with ideas for this?
5 how to process the start level sent with a network dim command. Valid values: 0 (use the start level sent with the command), 1 (ignore the level sent with the command)
7 number of steps used for the change when receiving a network dim command. Valid values 1-99
8 change timing (length of pause between steps.) when receiving a network dim command . Valid values 1-255
9 number of steps used for the change when the manual dim button is pressed. Valid values 1-99
10 change timing (length of pause between steps.) when the manual dim button is pressed. Valid values 1-255
11 number of steps used for the change when receiving an “all on” network command. Valid values 1-99
12 change timing (length of pause between steps.) when receiving an “all on” network command. Valid values 1-255
29 how to process load sensing. Valid values 0 (load sensing disabled), 1 (load sensing enabled)
Those are the only ones listed in the manual, so I don’t know if the others can be reset or not. So 7 through 12 confirm 3 different control methods (network dim, manual dim, network “all on”) and define the ramp rate for each of those 3 by using two parameters, one for the number of steps in the change and one for the Pause rate between steps.
As far as parameter eight, that’s the timing on the ramp up changes for a network dim command. I’m not sure the human eye can see the difference between a one and a three except maybe as a slightly less smooth Flicker… A 3 is the default and means 30 milliseconds. A 1 is a change rate of 10 milliseconds.
There’s also something about four options for processing an “all on” command, but I’m not sure which parameters those are.
OK, i’m not 100% sure about this, but it appears that Jasco may be using the same firmware for both the dimming wall switch and the dimming plug-in module, which is why some of the parameters are not defined for the module. If that’s true, here are some of the ones that don’t apply:
3 LED behaviour. Valid values 0 (LED turns on when the switch is turned off, default), 1 (LED turns off when switch is turned off)
4 used if the wall switch was accidentally inverted when installed. Just changes which end of the rocker is on and which is off. Valid values zero (default) or one.
That’s all I found so far. I still don’t know what parameter 6 is for.
Thanks guys. After a little more playing with it last night (without making any changes to the handler) Device B sort of stabilized. I think it had something to do with me cycling the device on and off, both from the app and from the lamp itself (testing load sensing). It seems like wait longer after shutting it off to re-cycle it, the dim level starts at a higher level.
I think this leads credence to the path you guys were heading down with parameter 8.
Either way I think I have both devices stable enough that I put them in to production. Thanks a ton!