While there isn’t a central location for all community-created edge drivers, just as there wasn’t for all community-created DTHs, the community-created wiki does have Quick Browse Lists (just as it did for DTHs) that can help shorten the search time.
Author topics in this forum are tagged with the appropriate device class. So there’s a list for Edge Drivers for lighting, another for sensors, another for virtual devices, etc.
It’s not as good as a full database where you could look things up by model, of course, and I still wish SmartThings would provide one of those, but it can be helpful.
For example, @philh30 has just created an Edge Driver for the popular Hampton Bay/KOF fan controller. One of the quickest ways to find that in the future will be to check the Quick Browse List for HVAC and Fan devices.
Or if you are looking for a community-created Edge Driver for virtual devices, you can see all the offerings together on the Quick Browse List for Virtual Devices.
It also has links for the Manufacturer-provided channels, like the ones for Aeotec and Zooz.
It’s not perfect, obviously, but at least it’s something.
I asked the team and they mentioned there’s no problem with this. Those that are added to the beta group got migrated to the drivers in the beta channel, and those that aren’t will get migrated to the drivers in the default channel.
Drivers in both channels should have the same content, the beta drivers were tested first by some users, so, any issue detected is corrected on both sides.
Are the production channel edge drivers pre-installed on the hub or are they only downloaded and installed when a device that uses it is joined? With memory apparently becoming a concern, I’d hate to have two copies (prod and beta) of all the standard drivers on my
Hub.
No one answered this question when I asked it, but presumably when everything related to groovy dth disappears from the firmware and Hub execution, some more memory will be freed up, hopefully.
What can the USB port on the hubs be used for? Expanded memory? Adding a Thread dongle on the V2 hub? I am just wondering if they can be used to solve some of our problems.
As is right now… Nothing. They (and the Bluetooth radio) were there for future expansion that never materialized.
ST could change that through software but considering this thread is now talking about memory limitations and ST doesn’t manufacture the bub themselves I doubt seriously they have any plan to do anything with the old hub.
I am still amazed the v2 hubs are still supported and part of the current and latest home automation update !!
Very unusual in todays world of 3 year support max
As soon as it becomes discontinued I’m off. There’s no way I’m going through the whole process of setting this up again. Still can’t believe there is t an easy way to back up everything and move it to a new hub.
This issue has been raised numerous times on this forum and even discussed directly with support. The fact that years later we don’t even have so much as a roadmap toward such a feature is a true embarrassment for SmartThings.
@Jeff_Gallagher How many devices? How many running drivers (not just installed, but with devices assigned)?
My own experience is that the v3 starts going downhill at around 15 running drivers on fw 45. I’m sure there are other factors involved (I have around 125 devices, almost all hub-connected, some interacting with the hub quite frequently), so your number may be different.
@Automated_House Are all 27 drivers actually running, or are some installed but not in use? That’s a lot to run based on my experience (though with fewer hub-connected devices, maybe it’s ok). Try running logcat for a little while on all drivers to see if you’re getting frequent driver restarts, which would be a sign that you’re running too much. My understanding is that the message is based on memory, not storage, so I suppose you could see it come and go depending on what’s actually happening on your hub.
Well, the ST V2 Hub has twice the memory and CPU of the ST V3 Hub. It also has the option to use the built-in battery backup (although most users removed their AA batteries after the firmware update that caused them to leak! Great memories! )
The V3 hub brought WiFi LAN connectivity, instead of only Ethernet, and an extra radio or two, one of which will now be used for Thread. In pretty much every other way, the V2 hub was a better piece of hardware.
Ha, so THAT’s why my batteries leaked. I obviously removed them at that point like everyone else because battery back-up to the hub when the devices you want to control have no power, nor the router for the Internet is useless
LMAO - well played, 
Great memories! )