There is a central location for the WWST certified Edge drivers. They are automatically handled by the hub/app.
There is not a central location for Community Edge drivers. No different than DTH’s. Hubitat Inc doesn’t provide or support a central location for Community drivers either.
I still don’t get the fake outrage at Samsung for some of this stuff… Its as if people love to just try and create drama…
Personally, I’m looking forward the change. To finally have all devices and (most) automations run locally. I get there is some transition pain, but I believe it will be worth it.
This community has done amazing things to fill the gap, and it is fair to argue that that shouldn’t have been necessary, but SmartThings has already relied on community support for DTHs, WebCore etc.
I just wish they’d pull the trigger and make the switch so I can see what’s broken and fix it.
It seems that there was a big mistake. All my device was offline even they had Edge Drivers. The only Thing I can do ist to pair them again.
This is …
That is a good idea. I accomplish similar things with various routines or… well, I used to use webcore. I’m now experimenting with Sharptools.
I’m going to have to think about these uses. They might make things simpler after the loss of webcore
I can see basically using them as variables. I guess in my mind they were always just location modes. I like the idea of the guest mode and I’ve added a vacation mode and emergency mode.
We’ve unfortunately had a few ambulance visits and it would have been nice to activate a mode to turn on all the lights, unlock the door and suspend certain automations.
I really love this forum. Thanks all.
I second that. I didn’t bother waiting I’ve now moved everything and disconnected all IDE based apps.
Just waiting on the Smart Lighting and the Action Tiles and then I’m finished.
Would be really helpful to know when the migration is going to start so I can set aside some time to deal with any issues…
I’ve prepared as much as I can:
My hub updated to 0.45.9 yesterday so should be ready to go.
I’d update them manually but almost all of my Z-Wave and Zigbee devices are relays in connection boxes that I’d have to open up to press the button to pair again!
There is a central location for the WWST certified Edge drivers. They are automatically handled by the hub/app.
Good. I thought that was what the person was talking about. I thought that because their communication has been lousy, IMO.
There is not a central location for Community Edge drivers. No different than DTH’s. Hubitat Inc doesn’t provide or support a central location for Community drivers either.
I would have liked to see a marketplace that was community moderated by approved moderators but progress shmogress.
I am not outraged. I am disappointed. I think this change is a step backwards because their scripting is limited and has a weird/verbose syntax. Local automation is great and should’ve been done before. Hubitat does that and still uses Groovy. This means that WebCore works for that.
I am finding Node-RED on HASSIO to be very easy to use so I guess; thanks Samsung.
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. 
https://thingsthataresmart.wiki/index.php?title=Quick_Browse_Lists_for_Edge_Drivers
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.
Not true. I use my USB port on the hub to power a small digital clock.
@Automated_House How many running drivers and installed devices put you at that memory warning?
