Button 3 & 4 are double tap.
Button 5 & 6 are triple tap.
So you could assign different functions for when you double tap, or triple tap, the buttons. If you don't have any other functions needed, or don't like double and triple tap, then don't use buttons 3-6.
Buttons 3 & 4 and the "doubleTapped" events do the exact same thing. I expose them both ways as if you are using TRIPLE taps, you have to use the button pushed event (as there is no tripleTapped event in Hubitat). In those cases it is weird to use button 5 & 6 pushed events for triple, but doubleTapped for double.
Exposing double tap as button 3 & 4 allows people to just use button pushes for both double and triple tap functions.
This driver seems to work with the commercial Enbrighten switch also. The commercial duty switch comes in paddle or toggle with the part numbers 43074 and 43072.
@JasonJoel I was actually able to invert the paddle direction by using your driver for the old switch. I temporarily assigned the old switch's driver, applied the inverted paddle setting, then changed it to the enbrighten driver and it stuck. So probably able to be added to the new driver as well.
Ah cool. Unfortunately on the new models Jasco/GE didn't document hardly any of the configuration parameters. I always assumed it could be done, but never tried it.
I don't use associations, so it is largely untested. But as I pulled it from one of my other drivers, and I believe it is working there, it "should" work.
Format for associations is a comma separated list of HEX id #s.
I just migrated over to the C-7 hub and included my Enbright switch using the S2 method. The built in driver works fine, but when I load the community driver from this page I'm unable to control the switch (on/off doesn't work). I don't see anything interested in the log.
@JasonJoel will probably know better, but my understanding is most older drivers don't work well or don't work at all with S2 paired devices. At least not without some changes.
I don't think he has updated his drivers, so you would probably be best served to stick with the built-in drivers for now.
The drivers DO NOT support S2 at this time. All user drivers for devices that support S2 will have to be modified to support S2 commands.
This driver should updated by the time Hubitat 2.2.3 comes out (2.2.3 features are needed, so it won't be supported until then), but there is more testing to be done.