No idea what they are referring to. There is no published configuration setting called "sensitivity" or anything close to that. It might exist as an undocumented command, but that doesn't really help you much.
You can certainly adjust how FAST it dims (parameter 6 - 0 or 1 value with 0 [the default] being fast), but nothing I would call "sensitivity". In my driver that parameter is called "Adjust the speed at which the ramps to a specific value".
Yeah, me either.
I'm not aware of any standard zwave command that sets or resets a response delay time, in fact no such command exists...
The delay is just under 2 seconds.
I sent an email request to Enbrighten technical support . After 2 weeks I got the following reply. This is beyond my skill set. I would appreciate any help.
Thank you for contacting Jasco Products Company. There is a slight delay with just pressing it once as it ramps up and down to the light setting. So it is normal for that to happen. Z-Wave devices typically have parameters which allow you to tweak settings like this in order to change their default behavior. You use your hub to make these edits but how this happens differs from one system to another. I have provided a link to the parameters below:
This is nonsense, I know you don't understand why.
I'm not seeing a specific parameter in that list that would fix this issue, if you wouldn't mind please ask your guy which parameter is supposed to change this behavior, however he doesn't understand the issue, and there is no parameter to fix this problem.
So for those with any interest in this, and this is why Jasco's response is crap, and this firmware is buggy...
What the tech is referring to is level reporting, and for zwave dimmers they typically issue a final level report once that level is reached.
However we aren't talking about that here, we're talking about the central scene class, which in the world of zwave, translates into button events in hubitat.
For both the switch and dimmer models the key pressed one time event for both on and off is delayed by almost 2 seconds while key held down and key pressed two times are sent immediately as they should be...
additionally the binary reports (that represent on and off) for both the dimmer and switch are also delayed, and this is also not right...
I can tell you that I personally tested EVERY report type on my 46203 devices after the OP posted this, and none of them - and I mean none - took 2s. Heck, none took over 1s either. That includes the single press events.
I guess it would be interesting to understand exact steps to reproduce, to make sure we're talking about the exact same thing, as I am just not seeing what you and the op are describing on my 46203 devices.
Or maybe there is more than one firmware, and it only happens on certain ones?
But I do agree that the tech's response was complete garbage. None of those parameters could cause, or fix, what the op reported.
Easy, fire up sniffer, hit the paddle on the device, on or off doesn't matter. Device produces a node information frame immediately, (and only on single press), ~1.8 seconds later a basic report followed by a central scene are sent from the device...
Yup. That is NOT what my two 46203 do. 
It wouldn't be the first time that different firmware or hardware revisions did different things...
I'll take a look again when I get home tonight, but I am 100% my on/off reporting happens in less than 1s.
They must have updated the firmware, though my embrightens aren't even a year old yet...
Firmware listed on back of dimmer and switch is 5.4...
I only have two of them. One is about 9 months old and one is about 2 months old.
I'll pull the nine month old one out and see if it lists any version numbers on the device.
Enbrighten technical support says it is parameter 16. Is this something that can be changed in z-wave parameter tool and if so what do I change in parameter 16. Or-- is this just another bit of incorrect information.
yes this can be changed using the zwave tool, no idea if this fixes the issue or not.
I can try later, or you can give it a shot.
set parameter 16 with a size of 1 to a value of 1 (the default value is 0)
nice..., kind of wondered about that...
But ON/OFF is probably SUPER fast... 
All smart assiness aside, I ran one of my 46203 in switch mode for months until I got around to replacing the LED bulbs with dimmable models. So I'm quite familiar with what Parameter 16 does.
I'm beginning to think support really doesn't understand the issue, this is somewhat typical at this level of support...
Only an engineer would understand this in all probability, and even he/she might not understand the implications until an explanation is provided...
yeah, except the switch exhibits the very same behavior, and presumably doesn't have this parameter setting...
Jasco support is still stuck thinking that the issue we're on about is the device providing a multilevel report at the end of it's dimming tranistion, this is not the issue.
The issue is that the central scene class for pushed is held up for 1 to 2 seconds, central scene has nothing whatsoever to do with the dimmers level or transition times...
Agreed. I don't think that they quite understand the issue - as you say, not atypical at 1st line support when it comes to technical problems.
Since I am now only using the switch for ON/OFF This would be exactly what I need. I changed the value to 1 as suggested using the Z-wave parameter tool per instructions. However, no change. I must have done something wrong. Any ideas?
Did you do a parameter read to verify it changed?
Other than that, no advice. I use my user driver, and switch mode it one of the configurable parameters in it - so that's how I did it.
I stand corrected. I see the same thing on my 46203s.
It is about 1s delay on mine, but definitely a noticeable delay for the on/off central scene report receipt. As you mentioned, the other central scene reports seem to be quicker, as is the multilevel report.
Sorry for the misinformation earlier. I would swear that I tested exactly this and did not see the delay. But I am clearly remembering incorrectly, as it is there.
Download the Hubitat app
