Its been a while since I have had to do any modifications. At least a year. How do I use the driver pointed to above? Before we used to point to the repo in IDE and then choose the driver. Is the process the same?
What’s the future? I have a few custom drivers contributed by the community. Some ceiling fans that I would like to keep running. I know some folks are switching to hubitat and others are switching to home assistant. I dont have the time for home assistant and it lacks alexa integration without paying a fee or jumping through a ton of hoops. Hubitat seems to be getting more support but doesnt seem quite ready yet.
I believe 2137B is a date or production code, not the model number. I say this because when you have a warrant claim they want a picture of that code to verify how old the switch is.
Install @philh30 driver, and if the device is already using an Edge driver do the following: Open device tile, click on 3 dots in upper right corner, select driver, select change drive, pick @philh30 driver.
Beware the switch driver function is currently broken on many devices, so you will need to wait until ST fixed this.
With my devices switch driver works on Android 9, but is broken on Android 11 & 13.
Which, as he said, iis true if they’ve been added to the table. But that’s just a table in the community-created wiki and it depends on community contributions to update it. And it’s brand new, so there are quite a few things missing still.
There are a number of community developers who are creating custom edge Drivers just as there were ones before who created custom DTHs. And the fastest way to find those is the same as it was before: check the quick browse lists in the community-created wiki. Edge drivers have their own page:
I see thank you for the information. I enrolled my hub and installed your driver.
Apple OS doesn’t appear to have the option for driver. My Samsung tablet I am seeing the driver option. When I select driver → select different driver → no results found
Maybe it takes a bit for the new driver to get pushed to my hub?
I also enrolled to your king of fans. I might wait and see if this one gets transitioned automagically with the fingerprint. As I dont want to mess with those at this point. I assume if they stop working I remove them then add them back and the edge driver should get loaded.
I like the idea of things running local instead of in the cloud. But does the smarthings hub have the storage to support all the drivers running local?
It could take a while, or it could be that I don’t have your fingerprint added to the driver yet. Jasco has an annoyingly large number of fingerprints and are constantly churning out new ones.
Try navigating to your hub in the ST app, hit the three dots, and then choose Driver. That will display the list of currently installed drivers.
Is your hub a V2 or V3? V2 seems to handle up to the max of 50 drivers just fine. V3 has half as much memory, and it can run into memory problems depending on how many devices and running drivers you have.
Took me a minute. I dont remember the hub being a selectable device. But I found it in the room its placed in. Under driver it shows your king of fans and GE Zwave Motion Switch/Dimmer
I went installed the other driver the GE Z-Wave Switch/Dimmer/fan/outlet. That one now shows up under select different driver but when I select it the page just goes white. Only way out of it it to choose back. Which then looks like nothing got installed. I think just the generic z-wave switch driver is what its using.
I am running the V2 hub. I have 52 devices. I think a good majority can use your driver though. I have a few I will have to go searching around for. Where do I find the fingerprint for current devices?
SYLVANIA Smart Flex RGBW
kwikset door lock
dome motion sensor
This is the current bug with driver switching that Paul mentioned. It was introduced with the most recent app updates. You can still swap drivers using an older version of the app, or by using the CLI (which isn’t tough and is good to set up since it’s pretty useful, but is a bit on the technical side). Otherwise, we’re just waiting for ST to fix it.
You shouldn’t need to worry about memory. I haven’t seen anyone complain about a V2 running out of space, and you’re not running that many devices.
Start by checking the old IDE. Most of your stuff should still show the fingerprint there if it’s still using a Groovy DTH or was installed using one and then automatically migrated. Anything installed directly to an Edge driver won’t show there though, so you’ll need to either use the CLI or one of the browser-based community-created device viewers.
CLI (instructions are to get logging going, but the basic setup is the same regardless of what you want to do).
Thank you appreciate all the support. I kinda have the hang of it now. I will probably wait for the Android app to get updated or the Apple app to have driver support. We are mostly Apple or PC in this house. I have one android device for things such as this.
Sounds like there will be some growing pains. Will need to think about my automation needs in the future and re-evaluate. Automation is great but can consume your life if you let it. Smartthings has been the happy medium that has been well supported and hasnt been a huge time sink. That may have changed.
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.