The built in driver will probably never support double tap. they seem pretty happy keeping it generic, and in my e-mails back and forth with support there was no indication that they have any plans to improve the built-in driver to support this.
So you have to resort to either making your own driver, or seeing if there's a community one. The double tap functionality is pretty easy to add on, and I thought I did before on my HE driver. Or maybe I tried and it didn't work. I can't remember. I'll have to go look.
I mainly use the motion switch and motion dimmer at this point so haven't looked at the regular switch and regular dimmer device handlers in a while.
I am also a user of the GE/Jasco 14291 switches and 14294 dimmers, and I am very interested in a driver that supports double tap and associations. So far I haven't found a community driver that works and supports all the features although there are a couple listed as deprecated that aren't fully functional for me. Any suggestions on where to find a driver would be appreciated.
That said, I am teaching myself how to write drivers. There is limited documentation but many community drivers to use as a starting point and reference. I am working on drivers for my needs but I'm happy to share if I get something working. If anyone wants to help to me code or test (or just guide) that will help a lot!
@steven Take a peek at the updated 14291 and 14294 drivers I released this week. They both support doubletap natively. In fact, they support all published hardware features of those switch/dimmer models.
There are multiple people using both drivers at this point, and have confirmed doubletap is working as expected/as described in the posts.
If that applies to my drivers (looks like it might?) I don't have any GE devices that use CRC16 encap commands, so this is going to to tough to troubleshoot. So the driver comment that it won't work on 12xxx devices might be true after all.
I'll look into it, though.
EDIT: @jon1 If you re using my drivers, I redid the CRC16 handling this morning based on the example Hubitat provided. I would update the driver and see if it helps/works.
If you do try it, please let me know. Since I don't have a device that does CRC16, I'm flying blind here.
@JasonJoelOld, I tried your drivers ... Very nice!. I am using associations to create multiway switches. Your driver makes it easy to set up one to many and many to one relationships. I do see some warnings in my log about parse returning null which might be normal? I'll look into that eventually. Also, I find the switch on/off state fails to update with delays greater than about 3 secs. I've seen similar happen with the built in generic driver. Hitting refresh on the generic will update the status but with your driver it doesn't update the status.
Thanks so much for sharing your hard work. If I can find any issues, or better yet fixes, I'll pass them back to you.
I'll take a look at the long dimmer time out refresh issue. I tried to put some logic in there to handle that, but I don't think it's working quite the way I expected.
Edit: I modified the refresh command, and it should update on/off now. I also tweaked the refresh on long delays. It might help, but I didn't really have time to test it.
You're right. I crossed the streams. I have actually been looking for drivers for all four of the switches these GE switches (motion [dimmer|switch] and 14xxx [dimmer|switch]). Sorry for that. And now... it appears you have done my work for me by releasing the two other drivers. You are a gentleman and a scholar. Thank you!
@mike.maxwell Is double-tap support in the generic driver something that is still being looked at or is it not going to happen as JasonJoel's interaction from support has suggested? There is a hardware event for it. It must not be what you're used to seeing or it would be working already though.
If it's not going to happen can you give me a hint at how you implemented the flash command? I have tried a couple of things but it's never as consistent as the OOB driver.
Was wondering if you could assist. I have 3 GE Dimmer switches all the same model. The dimmer driver works fantastic on two of them but for some reason on the third one I can't get on/off to work. I can set the level and that works. And I have associated this third one via double tap to another dimmer and it works fine. Log is below:
dev:5322019-08-22 09:41:51.487 am infoCouch is 99%
dev:5322019-08-22 09:41:37.140 am infoCouch was turned on [digital]
dev:5322019-08-22 09:41:37.124 am infoCouch is 10%
dev:5322019-08-22 09:41:31.659 am errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 311 (on)
dev:5322019-08-22 09:41:18.099 am errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 311 (on)
dev:5322019-08-22 09:41:10.526 am infoconfigure triggered
dev:5322019-08-22 09:41:06.261 am inforefresh() is called
dev:5322019-08-22 09:40:58.188 am errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 311 (on)
Edit: "Off" via the dashboard does not register in the logs.
Second Edit: I have been struggling with this for days and apparently all I had to do was post the question because it somehow miraculously healed and is now working fine. NM.
Gnat I am having very similar issues --- ON And Set Level work. OFF Does not work from the devices screen. I posted full details on the Botched1 release thread. Did you find a solution yet?
I have no idea how it started working. Something I did that morning is click the refresh and configure button a few times and used the set level button too. Then about 10 minutes later it was working with on/off. Not a very technical answer, but that is what I did
No idea here either. The logs look like it should be working.
That said, I would try:
Switch to the in-box driver driver
Hit configure
Wait 30 sec
Hit refresh
Try on and off from the device page
Try on and off physically at the switch
Try on and off from the device page again
If all of that works, then I would try switching to the user driver you want and repeat the exact same steps. If on/off doesn't work on the user driver, but does on the in-box, then there is a driver issue.
If it doesn't work on the in-box driver, well then you probably have a zwave mesh problem.
@JasonJoel, Thanks for your reply. I tried that and the Built in "Generic Z-Wave Dimmer", and it worked just fine. So I went back to the Botched1 driver, configure/refresh as appropriate. Still no luck. It may be worth noting that a "Set Level" of "0" does nothing as well. Set level of 1 works just fine. can you set level to 0? If not we maybe want to update that into the driver, as it indicates 0 is an acceptable value. (I'd be willing to attempt this change, not that this will solve my issue).
I also tried reimporting the groovy driver file, just because. I am using the Import from URL. I'll go try copy paste too.
I am experiencing the same behavior on two dimmers. Please try out that set level of 0 on yours and let me know --- i'm reading the code and debug output (I am a software developer by day, so I think we can figure this out....). Thanks much.
Get a screenshot of your device state options on the non working device. Your experience sounds alot like mine but I noticed mine when my Google home integration wasn't working. Basically the "switch" state on one of my ge plus dimmers vanished. See the screenshots in this topic. I resolved by excluding and rejoining a few times.
If so, and you followed the installation directions in the driver thread ( [RELEASE] GE/Jasco Z-Wave Plus Dimmer Driver ) and setup the preferences, then hit save preferences. Then I'm at a loss. Maybe a different firmware version (?). If that is the case, it will be kind of hard to troubleshoot on my end without a device with the same firmware though.
If it is not one of the new shallow mount Enbrighten models, though, I would definitely not expect it to work - again, unless Jasco/GE slipped really new firmware on the latest GE 14294 dimmers.
@JasonJoel, Getting back to this tonight. I have a 14294 dimmer and yes I am attempting to use that driver. I noticed that the command being sent in your driver for off/on/set level is this == command: 2603. The command being sent in the generic smart zwave dimmer (that works) is == command: 2003. I'd love to switch this number, just to see --- and to learn. I do not see 2603 in the driver code at all.
In your driver, I commented out the code for the check --- "is the switch on" in the zwaveEvent(hubitat.zwave.commands.switchmultilevelv3.SwitchMultilevelReport cmd) function. This did not help.
Is there sendEvent documentation anywhere? I'm not finding any, but maybe I am looking in the wrong place.
Finally, I switched the driver to the basic zwave tool. I ran the version report if this is helpful.
dev:852019-08-28 08:05:12.447 pm infoVersionReport- applicationVersion:5.29
dev:852019-08-28 08:05:12.440 pm infoVersionReport- zWaveProtocolVersion:4.34
dev:852019-08-28 08:05:12.437 pm infoVersionReport- zWaveLibraryType:Enhanced Slave
I did not see any option here to actually send commands, only to set configuration parameter values, so nothing further I could really troubleshoot here.
I appreciate your time -- and by the end of my mess I'll hopefully be able to help you support the driver.
It is interesting it doesn't work on your device. The difference between the in-box and my driver is that it sends a basic OFF command, whereas I dump the switch to 0 level via the setLevel command.
My de vices are mainly:
applicationVersion:5.26
zWaveProtocolVersion:4.34
So mine are older than yours. It would be easy enough to switch the off to a basic set command, though. Maybe this weekend.
