That’s how installing Edge drivers works. Generally the author will create a discussion thread in the community, with the channel invite in the first post. They might also link to a GitHub repo, but that’s to allow others to view or modify their code; it isn’t necessary (or even useful) for installation.
Without checking every fingerprint, I’m guessing based on the device names that nearly everything you listed above will work fine with stock drivers. You’ll likely only need to install additional drivers if you had a custom DTH for the device on the past.
Yea I was running custom device handler for Iris smart plug, MyQ garage door opener, dome motion sensor, neato botvac, king of fans, and the GE plus dimmer for the double tap functionality. I also use webcore for event based triggers, but looks like that is going away.
All these devices are in the stock smartthings drivers and should be migrated automatically or manually if you want to install the Z-wave Switch or Z-Wave Sensor or Z-Wave Lock driver from the smartthings channel.
You can find the data of your devices in the .yml files of the beta smarttings drivers on github
So I was able to change the driver to Phil’s driver on the 2 new switches I added. I was going to add his driver to the rest of the dimers in my house. However the “driver” option does not show up under the device.
Do I have to remove it then re-add it to get this to work? If I just leave things will things transition automatically eventually?
Bringing back an old thread. All of my switches have been updated to edge drivers except one. There is one GE light switch that refuses to take Phils driver. I assume it must be old but I cant imagine its significantly older then my other GE switches. There always has to be one…ugh.
I’ve also had no luck with drivers for dome motion sensors
That fingerprint is already in the driver. Your device is not getting that driver because it has not registered with the hub properly. The raw description shows all zeros for the fingerprint and it did not set up S2 properly. I suggest you factory reset the device and attempt to add again via the QR code for the device or by adding the DSK when prompted if adding via Scan Nearby or Add by Brand.
I tried installing some of the zwave motion sensors from smartthings. They did not work. I’ll have to try the “old” driver see fi it works
Also another question after updating some cabinets light with new driver. I noticed execution location says cloud. I am also using a smart lighting app in smartthings. I noticed looks like they created a new smart lighting app. This one appears to run local. I use a Zwave light switch that when you double press it it turns on these zigbee cabinet lights. I use the smart lighting app to enable that feature.
To me it appears the execution location is incorrect. I disconnected my main internet connection. Then proceeded to double tap the switch. Lights came on double tap again lights go off. So appears not to need an external connection for it to work.
Ignore what you see in the IDE once you’ve converted a device to an Edge driver. The best place to see execution location is in the API Browser+ from @TAustin or in the ST CLI. Keep in mind, there are many things that can force execution to the cloud even if the device supports local execution. These are things I’ve found will force cloud execution:
Devices from cloud->cloud integrations
STHM triggers and actions
“Any Day” time precondition
Cloud virtual devices
Devices on two different hubs
Also, many of the community Edge drivers expose association groups that allow a device’s actions to be mirrored to other devices without going through the hub. This eliminates using Smartlighting to sync behaviors.
Did you find a solution for the WAPIRZ-1 yet, Mike? Alas, I also have one of these oldies but goodies! Mine paired with Z-Wave Sensor PH–which I had installed earlier for another device. It’s close, but the Linear/Gocontrol WAPIRZ-1 device has both a contact sensor & motion sensor report (as well as Temperature and Tamper). Consequently, it shows in the app as a generic “Z-Wave Sensor,” reflecting the contact sensor state on the main tile. (One can pick motion, temperature, or tamper, as well, when setting up a routine.)