That is what I thought too... I thought it was done at the hardware level on this device, and was why I said it should be in the base handler.
I agree with @mike.maxwell, if it is/were a fake software based double tap it shouldn't be in the official driver. But this is hardware based...
See relevant code below. No software magic involved.
def parse(String description) {
//log.debug "Description: ${description}"
def result = null
if (description != "updated") {
def cmd = zwave.parse(description, commandClassVersions)
//log.debug "CMD: ${cmd}"
if (cmd) {
result = zwaveEvent(cmd)
log.debug("'$description' parsed to $result")
} else {
log.debug("Couldn't zwave.parse '$description'")
}
}
result
}
def zwaveEvent(hubitat.zwave.commands.basicv1.BasicSet cmd) {
//log.info "bv1BasicSet"
buttonEvents(cmd)
}
def buttonEvents(hubitat.zwave.Command cmd){
//log.info "buttonEvent"
if (cmd.value == 255) {
createEvent(name: "pushed", value: 1, descriptionText: "$device.displayName Upper Paddle Double-tapped (Button 1)", isStateChange: true, type: "physical")
}
else if (cmd.value == 0) {
createEvent(name: "pushed", value: 2, descriptionText: "$device.displayName Lower Paddle Double-tapped (Button 2)", isStateChange: true, type: "physical")
}
}When I switch to the custom driver listed above and try to do a physical double tap on the switch, nothing happens. There are no events for the device and the "button pressed" status never changes to #2 (double tapping on the bottom). Pressing the command button "double tap" on the device edit page has the desired effect but actually doing it with the device does nothing. I have logs to prove it. If there is something that I'm doing wrong, please tell me.
[dev:548](http://192.168.1.12/logs/past#dev548)2019-01-11 06:57:52.666 pm [debug](http://192.168.1.12/device/edit/548)'zw device: 0E, command: 2603, payload: 32 ' parsed to [[name:switch, value:on, descriptionText:Bathroom Lights was turned on], [name:level, value:50, descriptionText:Bathroom Lights brightness set to 50, unit:%]]
[dev:548](http://192.168.1.12/logs/past#dev548)2019-01-11 06:57:24.444 pm [debug](http://192.168.1.12/device/edit/548)'zw device: 0E, command: 2603, payload: 00 ' parsed to [[name:switch, value:off, descriptionText:Bathroom Lights was turned off]]
[dev:548](http://192.168.1.12/logs/past#dev548)2019-01-11 06:43:17.172 pm [info](http://192.168.1.12/device/edit/548)Bathroom Lights was turned off [digital]
No double tap responses. And yes, I hit configure on the device edit page before doing any of this.
I remember reading on the ST forum post (where the nuttytree driver originated) that this worked with specific models and that some versions had issues with the driver. Do you know what specific version you have? Did the doubletap work for you on ST?
There is some talk about it here and a few posts down
..but I know there was another post somewhere with more detail. I cant find it. When I bought my switch, I opened the box to ensure it was the correct version (f/w version is on the switch itself) to make sure it would work with this driver.
I know that I used the double-tap in ST. So, I assume I have one that supports it.
Don't know what to tell you. This is what my logs and device page looks like. One is 2xtapup and the other is 2xtapdown
Is there some parameter that has to be configured that isn't exposed by the driver? There are no preferences in the driver that you can set. I don't know what to tell you either....but I'm using the driver listed here and I'm double-tapping on the switch and I'm not seeing that showing up in my logs as all.
Which driver? The one in post 1, or the one in post 2?
Post 2.
The one in post 2 doesn't give me any messages on double tap either - I only tried it on a 26933 motion dimmer, though, as that is what I had handy.
I have a 14294 paddle dimmer upstairs though. I'll go try it there just for curiosity. EDIT: Nope I didn't get the double tap message there either.
Oh well.
I really wish I was better at understanding zwave code. Unfortunately I'n better at zigbee stuff but weak even there. I just edited existing code enough to work with HE and changed the button section of nuttytrees driver to follow HE's standards.
What driver did you use in ST?
I have no idea. I set it up in ST so long ago and I know I tried several at first because some had better appearance in ST mobile app.
Bare with me because I'm troubleshooting from my phone....but can you uncomment this log debug, doubletap the upper paddle and send me paste the output?
Did you hit configure after selecting the custom driver?
Nada...nothing in the logs but the off/on commands. And yes, I hit configure.
Lol...yes, I know. You mentioned it before.
Just wanted to make sure I mentioned it. 
I hit configure, too. Change driver, hit save. Hit configure. Tested.
For some reason your dimmer is not sending the same response as mine so there has to be a difference. If you find the driver you used on ST, I could try to make it HE compliant for you....but if you device does not send the response, there is nothing else I can recommend. My guess is that your revision simply isn't supported by this driver. 
. Please post any details you have with the exact model so we could save someone else all the troubleshooting.
Download the Hubitat app
