The SmartThings-specific issues are the ones that might be better or worse depending on the specific edge driver you are using.
For example, quite a few community members have reported that their GE/Jasco Z wave devices work better with a community edge driver from @philh30 than with the stock edge driver.
[ST Edge] Driver for GE/Jasco/Honeywell Z-Wave Switches, Dimmers, Fans, Outlets, and Plug-Ins
Some of my devices that were auto migrated to edge had to be excluded and then included again to get them to work properly. I also had to use different drives from the community on my Ge/Jasco switches.
Thanks! Yeah some of these are the GE/Jasco units so Iāll definitely give that community driver a try!
And if any of those GE/Jasco devices are bad and less than 5 years old, Jasco will replace them at no cost to you.
In general Iād recommend not adding any community-developed drivers unless you find youāre having some issue with the stock driver.
From what Iāve seen here, itās fairly easy to run your hub out of memory causing all sorts of problems.
Iāve got a handful of GE/Jasco dimmers and switches, a mix of ZigBee and Z-wave. No issues using the stock Edge driver so far.
There are good reasons to run community drivers and judicious use of them is very much warranted.
The GE/Jasco drivers from @philh30 expose features/capabilities not found in the stock drivers. His Z-Wave lock driver exposes advanced lock features for Schlage locks not found in the stock driver, exposes lock code name as a trigger for Routines, and fixes issues with lock code names being reset by the Z-wave default handler used by the stock driver.
Drivers from @Mariano_Colmenarejo implement capabilities not found in the ST app such as advanced calendar triggers for Routines and support for many, many Zigbee devices not supported by stock drivers.
90% of my drivers are community because the drivers created by ST just dont work or are missing functions that worked in the DTH.
ST should be paying mariano, Philh30, Taustin and manny others as thier drivers actualy work!
Totally agree. I use a couple of community developed drivers myself. But the key is, as you said, judicious use.
Try the stock drivers when they exist, if youāre missing some functionality, them by all means hunt up a community driver. But donāt throw every community driver onto your hub unless actually needed.
Totaly agree with this!
So does āinstallingā an Edge driver use memory in the hub, or only if that specific driver is being used for a device?
The memory problems are mostly tied to the number of running drivers. An installed driver with no devices assigned doesnāt seem to make much of a difference. Probably still a good idea to clean up what you donāt need.
Community drivers donāt seem to have any more load then stock drivers, assuming of course that there isnāt something in their code thatās hogging memory. The real problem is if you have a bunch of drivers tailored for individual devices. Ironically, thatās the path that Aeotec took with their drivers - each of their devices has its own special driver.
If one community driver completely replaces a stock driver and gives you more functionality then by all means use it.
Each uses a tiny bit of memory just to have it on the hub (youāre allowed a maximum of 50, by the way). And each makes the install of a new device run a little bit longer because the system has to check the fingerprints in each.
But if you arenāt adding a new device, and that driver isnāt being used, it should have very little impact.
I have a bunch of Samsung sensors that are zigbee and since Sunday, about half of them have gone offline again. This seems to happen a few times a year and nothing I can do will get them back online other than waiting and over the course of a few days it works itself out. With all the nightmarish changes I donāt know if itās another change theyāve made or whatā¦
Have you tried a Zigbee mesh repair? Unplug your hub for about 30 minutes and then plug it back in and it will force the repir. If you have a V2 hub also remove the battery.
Well so for me, this is not working out 
So I have the community GE/Jasco drivers installed (for a Z-wave switch) and I can see them listed in the drivers section for the Hub in the app. Unfortunately, they are not listed as driver I can switch to on the devices in question and for some reason a lot of the devices donāt even give me the āDriverā option on the menu in settings for the device, Iām a little confused by that, and I have a mix of devices but they are listed with that community driver option as ones supported.
There are two different reasons why a driver that you do have installed on your hub is not showing up as an option under an individual switch, even though they should be compatible.
A) that particular model has not had its fingerprints added to the new driver. Thatās why we really do need to know the specific brand/model of the switch you are having problems with. For Jasco switches, this will be stamped on the metal surround of the switch module, underneath the face plate. Newer models will also have a separate QR code in a paper sticker on the surround.
If this is the problem, then you will need to contact the author of the edge driver that you want to use and ask them to add your model to the driver.
As far as the device that doesnāt have a driver option at all, it is still using a custom Groovy DTH from the old architecture. Right now while both options are possibilities, the custom DTHs are taking priority.
Thereās a fix for that as well, but it takes many steps, itās more complicated, and itās not reversible, so I am hesitant to recommend that until youāve checked the other issues I mentioned above.
But as always, the first rule of home automation applies: āthe model number matters.ā 
Iāll try and get the actual model for the Jasco ones where I get the āDriverā option but donāt have the community driver offered as an option, but yeah it weird about the other ones (GE) where I donāt even get the āDriverā option in settings - I donāt have a single custom DTH installed or listed so I donāt get why I donāt get the option at all, even if it was just to see it using the standard Z-wave edge driver.
That can happen when a device fails to pair properly and ends up with all zeros for the fingerprint. Iāve seen that happen for a number of reasons including not setting the device up with S2 security if it is supported.
It would help to know the fingerprints of these devices so we can point you in the right direction. I would suggest using the API Browser+ from @TAustin to verify the fingerprints.
