I would think you would have to do a factory reset first wouldn't you? Otherwise, the params that were set by driver 1 might still be there. Without that, is it truly a test of driver 2?
I had 3 different switches. I only used driver 1 on 1 of them.
And you are right. Once you add the Hub ID to association group 3, it stays until changed or factory reset.
Thanks, I'll look into it.
4 Likes
@stephack just noticed your update to driver 2. I think you have a typo in the version string. thanks for the update.
1 Like
I ported Nuttytree's Smartthings DTH for the GE 14291 Z-wave Plus Switch a couple of weeks ago. It has been working well for me. It supports double-tap and also reports physical / digital events correctly.
I just posted a link to it in this post.
I'm glad to hear that Hubitat may add native support for double-tap for the GEs. This was my first port of a driver or app from Smartthings; it was a fun project in any case 
Time flies when you're having fun 
I forgot we're in 2019 now....version number updated.
Forgot to mention to you that driver 1 (pretty much a direct port of the ST driver) has a lot of these config options already available. I did not need them and I believe they may have been causing issues with HE so I removed them. This was months ago, so one of the many updates may have fixed what I described in the second post.
Regardless, you have a template in place with that driver. FYI.
Please and thank you! Is there documentation on what features the stock drivers support? I'm not finding it in the wiki and I don't have any installed in Hubitat. Are the dimming rate settings and timeout duration settings exposed as well?
There isn't any documentation on the built-in drivers (that I have ever seen anyway). Whatever you see on the device detail page is what it does.
The GE/Jasco Dimmers use a generic "smart dimmer" driver (the motion dimmers use a different driver, though). Typically these generic drivers have the core functionality common to all devices of that type (dimmer in this case), but not any of the vendor specific or unique features.
For instance, double tap is not supported. Neither is dimming rate. The switches don't have a timeout setting at all, so that would have to be handled in RM rules or another app.
If you want to see everything the GE zwave plus switch can do in hardware, the list is here:
https://products.z-wavealliance.org/products/2105/configs
The built in driver only exposes parameters 3 and 4, and doesn't expose association groups at all. Association group 3 needs to have the hub ID (1) added to it to even get the double tap messages from the switch.
Any other feature (like timeout? depending on what you define that as) would have to be done in software - on any system, that isn't unique to HE.
Could the relay switches support double tap? Or just dimmers?
The 14291 supports double tap in hardware, if on firmware 5.20 or newer which came out in 2016.
I probably have a custom HE driver that supports that... Somewhere... Not sure how well it works though, as I don't really care much about double tap - so don't use it/test it.
I do know the 14294 dimmer driver I have floating around supports it, but it has a few quirks versus the built-in driver (can't use it over a Hub Link, for instance due to some timing issue I haven't figured out).
1 Like
Yeah, the switches do have a timeout setting. That's what param 10 is. When the switch is set to manual mode param 10 specifies how much time will pass until they trigger motion again. It's in hardware. I'm not sure if that is a typical use for param 10 since companies are supposed to follow a standard but that's how this switch implements it. I can see it from looking at NuttyTree's original ST driver.
Anyway, thanks for the information. I guess I will be running a custom driver since I super dig having access to the refresh trigger delay setting thinger. In high traffic areas I set it very high so there is less crap going on. In remote locations in the house (like the basement bathroom) I like it very low so that somebody moving in and out of the bathroom can get crisp responses from making mistakes, etc. while deciding what to do while moving around. Not sure if that makes sense for you but it makes a ton of sense for me and I like what I like.
Any drawback to running a custom driver on HE? On ST it meant cloud processing but I don't think that's a thing on HE.
It is getting confusing in here because people are referring to completely different models of devices - which have very different capabilities (both in hardware and in the default driver in HE).
Of course the MOTION switch and dimmer have a timeout. 
The auto off timer for the MOTION switch and dimmer is exposed in the default driver.
Note, though, that the MOTION switch and dimmer do not support the double tap functions I mentioned before in hardware.
Also, you can of course set the auto off timer setting from the switch buttons themselves, if you have no need to change them programmatically.
So just for clarity, there's no more recent community driver for this switch? I thought it was a common smart switch to use...do people just not care about double tap features, or is there a software workaround that I'm missing?
I have GE dimmers and switches throughout my new house (all the zwave plus models of appropriate firmware for double-tap and associations, 14292 for the dimmers). I'm not so worried about associations, as I only tend to associate TO the GE switches from a dumb in wall zwave switch.
The double tap, however, is extremely useful, and the delays on SmartThings to process the double tap was a driver in my looking into Hubitat. Does anyone have this successfully working? I couldn't get it running on the original driver above. I could "double tap" in the web interface, but physical double taps did not function.
I spend so much time on home automation already that my wife wants to slap me, so maybe HE just isn't for me until it's a bit more mature?
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.
