Once you enroll and install the driver it is on your hub. Any future updates that Phil makes will automatically update your hub within 12 Hrs.
To see your installed drivers in the mobile app click on: Hub > 3 dots in upper right corner > driver and it should list all of your Installed drivers.
So far as I know, the SmartThings āstockā Edge drivers will not support any multi-tap operations, same as it was for the stock DTHs.
If you have switches that support multi-tap, youāll need to find a community-developed driver that will do it. Iām not a fan of multi-tap so donāt have any recommendations. You might be able to find a community-developed driver with the help of the Wiki:
https://thingsthataresmart.wiki/index.php?title=Quick_Browse_Lists_for_Edge_Drivers
Correct, the stock drivers do not support multi-tap. Iām using @philh30 's driver, which generally works great.
Since my above post, I managed to update the firmware on the switches in question. These switches now fall under a newer profile (fingerprint: 0063-4952-3137), which enables ge-switch-scene (allowing double and triple taps) in the driver. However, I have several other switches with the 0063-4952-3038/3037 fingerprint. These initially appear to have had the ZW4003 firmware, which evidently could only use the ge-switch-assoc profile (and this is how philh30ās driver is coded). However, my switches (despite the older fingerprint) appear to have come with the ZW4008 firmware. Thus, they are capable of central scene, but they are using the older profile in the driver. When I have time, Iāll fork philh30ās driver and try switching those fingerprints to the ge-switch-scene profile and see if it works.
For the record, I was able to modify philh30ās driver to make the 14292 and 14293 GE Smart Toggle Switches (fingerprints: 0063/4952/3037 and 0063/4952/3038) with ZW4008 use the ge-switch-scene profile. This worked, and Iām now able to use 3x taps and held up/down commands on those switches. Now how the driver can account for the fact that switches with the same fingerprint may have different zwave firmware, Iāll leave to those smarter than meā¦
See ST-Edge-Drivers/GE-Jasco at main Ā· philh30/ST-Edge-Drivers Ā· GitHub for a list of all the different fingerprints, devices, and profiles in the driver.
Iām looking for Edge drivers for a ZW3102 Energy Monitoring Lamp Modules (0063/4450/3031) . Currently using the Z-Wave Metering Dimmer DTH.
@philh30 Are you still planning to add the parameters (specifically default dim level) to routines in your driver for z-wave switches and dimmers? Eagerly awaiting this feature!
QUESTION:
I would love to switch to these EDGE drivers but canāt even imagine doing this manually (60+ devices not to mention all the routines I would have to redo)
Will this eventually somehow ātransferā it self to edge drivers?
Thanks
What are you running them with now, custom DTHs or standard?
At some future date there will be an automatic migration from Groovy DTHs to Edge drivers. How it works will depend on if your devices are on stock or custom DTHs and on what, if any, custom Edge drivers you loaded onto your hub. The automatic migration is supposed to preserve the devices places in your automations.
Once a given device is using an Edge driver, itās easy to change to a different, compatible, driver.
Yes - the migration is underway now and ST is slowly converting existing devices. The only devices Iāve seen reported here as automatically migrated, or observed myself so far are ST buttons and Z-wave repeaters.
If youāre currently using stock DTH (have not installed custom code), your devices will eventually convert to stock Edge drivers. If it goes smoothly youāll never notice a difference.
If you want your switches to use this driver after migration, you can enroll using the āChannel Invitationā link in the first post and install the driver(s) for your devices. If you do it before those devices are migrated, and if the fingerprint for the device matches the one in the driver, the driver should be automatically selected (priority over stock driver). If you install it later, or the preferred driver isnāt chosen during migration, you can change the driver from the three-dot menu on the device screen.
Details about migration are here; the migration is part of the first stage but it seems like theyāre only now really starting to move devices on a wider basis.
I will change all to standard from DTH
Thank you!
Hi @philh30,
As many have said, I really appreciate all that you are doing here with Edge drivers for GE/Jasco Z-Wave products. Thank You.
I have a question based around user experience that I am kind of surprised I havenāt seen mentioned yet. I may have overlooked it, but more than likely Iām just that picky UX guy.
I am running the driver on two GE Z-Wave In-Wall Smart Fan Control (55258 / ZW4002) switches with the fingerprint 0063/4944/3337 that are registered with profile ge-fan-scene. Since this is just a fan control, I do not have use for the Dimmer (switchLevel) or Button capabilities in the device controls in the app. Is it possible to have the driver recognize the profile and hide these from the device UI?
I understand this may be tedious or not ideal given some users may prefer to leverage the button functionality for with their fan control. It may be better to add functionality that allows the user to show/hide the controls via settings in the app. Or perhaps there is an existing way to disable the device capability via the cli that would hide the control? I checked but didnāt see anything stand out in the command help for managing device capabilities
Let me know what you think, and if I can provide any additional details. Thanks again for all you are doing.
-AC
Do the motion sensing switches support multi tap?
I just installed the GE Outdoor Outlet and I am having a weird issue.
It paired the Philās Edge driver immediately but I cannot get any status updates nor turn ON the outlet from my phone. I can however turn OFF the outlet from the SmartThings app, with the caveat that the status is never updated.
Anyone have this issue?
P.S. how does one look up device information anymore? The IDE doesnāt show anything anymore for devices on Edge drivers and I do not see any information in the IOS app.
Hi, thanks for this driver it works great. Would there be a way to disable the power meter setting? It fills up my history and I canāt debug my routines. Thanks.
The dimmer control is there to allow the fan speed to be controlled by voice assistants, but I can hide it from the device controls in the ST app since itās not necessary there. Iāve added the button capability to the devices that support multi-tap, and I donāt intend to remove it or add any option for the user to remove it. My source code is posted to GitHub, so if thatās something thatās important to you then youāre welcome to fork and make any changes for your own use.
No - those donāt support any button events. The best they can do is report that they were physically turned on or off, which includes both the button being pushed and motion triggering them to turn on.
The only time Iāve seen something similar is when I had a device showing up twice in ST - one with an Edge driver and the other with a DTH. In that case, both instances could control the device, but status updates were only reaching the DTH version. I would suggest excluding the device, making sure that the device actually gets reset in the process (recently when Iāve deleted z-wave devices, the app processes the deletion very quickly without actually resetting the physical device). Then start over with a fresh include. If youāre still having issues then Iād suggest setting up the CLI to pull logs, though if the z-wave commands arenāt being routed to this driver then they may not show anything useful.
The CLI is the only official route right now. There are also a couple of community-created browser-based solutions - here or here.
Which device do you have? Most of the z-wave devices covered by this driver donāt have power metering.
GE zigbee switch.
Thanks
Hi ā wanted to bump this up in case you missed it. Back in January you wrote about intending to add parameters (specifically default dim level) to routines in your driver for the switches and dimmers (just like youāve already done for the motion sensing switches and dimmers). Do you still plan to do that? Big fingers crossed for this feature! Thanks for all you do.