This is an Edge driver for GE/Jasco/Honeywell Z-Wave switches, dimmers, fans, outlets, and plug-ins, covering the range of generations from the legacy non-Plus devices to the current Z-Wave Plus devices with central scene support. Depending on the capabilities of the particular model, the driver supports:
Setting configuration parameters
Adding nodes to association groups 2 (load) and 3 (double tap)
Double/triple tap button events
Hub is automatically added to association group 3 for models that support double tap but do not support central scene
The list of fingerprints currently included can be found here. If you have a model that’s not included, let me know and I’ll look into adding it.
To install:
Use the following link to enroll in the channel and install the driver on your hub: Channel Invitation
If your device is already using an Edge driver, you can use the driver utility in the app to switch drivers.
If your device is currently using a Groovy DTH, you will need to exclude and then add it back to SmartThings to pick up this driver. If you have any custom Groovy DTHs installed that have the device’s fingerprint, either delete the DTH or comment out the fingerprint before attempting to re-join the device.
Is yours the toggle (46202) or paddle (46201)? I’m trying to track what’s verified as working and realized I had both set to be named 46201 when joined.
Wouldn’t (shouldn’t) Smartthings be making edge drivers for these switches? I have way too many on these, and no desire to remove and rejoin them, and then redo the automation.
At some point ST will transition your devices to Edge drivers without requiring any action on your part - no exclude/include. The process should be seamless for you, and they’ll map your devices to an appropriate stock driver. It’s completely ok to wait for ST to transition your devices, since that should be less disruptive for you.
ST has written an Edge driver for z-wave switches, and if you wait then that will likely be what your GE switches are mapped to. In its current state, that driver has all the basic functionality covered, but none of the additional features like configuration parameters, association, or double tap. After the transition, you’ll be able to swap drivers just like you can swap DTHs, and there may be other community options to choose from by then.
Added. I couldn’t find anything on that model, but I found 3235 which supports central scene. I’ve put yours in the central scene profile assuming it’s the same. The choice of profiles only matters for the button events (which you may not care about on an outlet) so if you find that double tap isn’t working I can shift it to a different profile.
I recently asked about this, and the answer I received is that there is a difference in this regard between groovy DTHs and edge drivers.
With a groovy DTH, you can just manually assign it to any DTH you want.
With an edge driver, the fingerprint of that specific device must be listed in the driver, or the driver must’ve been written to specifically accept a generic pairing, which not all do.
Hard to tell how much of an issue this will be once everything goes live, but I just thought I’d mention it.
@damohabir If you log into the Groovy IDE and list your devices, those devices using a driver will be of type “placeholder”. Alternatively, if you list your devices using the CLI, those using a device handler will be type “DTH” while those using a driver will be type “ZWAVE”.
I know the IDE will list device fingerprints for all devices that use a DTH. Is there an equivalent in the CLI yet? I have a few devices that were initially added with the samsung generic switch driver, and I’m not sure how to view the fingerprint.
Also, what should the hexid be in devices that are using drivers? A device network ID is no longer shown in the IDE.
I had some time today, and I wanted to see what it is like to install an edge driver. So I decided to install this one and change one switch over to use the driver. I was pleasantly surprised at how easy it was to install. So now I have one switch using this driver. However, IDE is showing that this is now “cloud” execution instead “local” execution. Did I do something wrong?
