Yes a few of my automations and devices will cease to function and although I’ve been with ST over the course of like 5yrs, I’m still struggling with exactly what I need to do here if I’m honest.
Which devices?
Not even sure to be fair haha .
Off the top of my head, things like
Harmony Hub ( I have 2 )
My Arlo cameras
Nest thermostat
Neato Botvac D7
There is an edge driver that can manage one Harmony hub.
Nest thermostats can be integrated with the google nest integration. I had the worst time migrating from my Nest account to Google Home account but that has nothing to do with ST.
If your zwave devices support OTA firmware updates then do it first, its well worth it and 700 series devices are ligthning quick.
I use 2 harmony hubs though, although hopefully this will happen sooner rather than later.
Not sure how i go about the nest integration. I don’t think I ever moved my nest to the Google integration. ( I remember this issue back last year and everyone said don’t do it )
That leave my Arlos ( pretty important ) and my Neato
The official Arlo integration already uses the new architecture so nothing should change on that. So unless you’re running some custom code, everything should be fine with those.
What are you using for the Neato integration?
Ah see, I didn’t realise my Arlos would work. I assumed that was a goner
My Neato is a little different and I could easily use a virtual switch and use Alexa to trigger that when the home is in away mode. I assume and hope the new virtual switches can be exposed within Alexa?
I’m using ‘Neato ( connect) ‘ smart app.
Unfortunately, I don’t have information about that. Have you reached out to the Customer Support team to share your concern about these limits?
They handle questions/issues related to the ST app (non-development / customization related).
There HAS to be an increase in automations. 200 is simply not enough
Especially given the fact webcore is going away. I’ve had to move a lot of my automations to webcore because of this 200 limit, now webcore is gone, now what?
Yes, the endpoints of the API won’t be modified. However, remember that each integration has different properties, for example, a DTH has deviceTypeId and deviceTypeName (DTH Name) which are not included in Edge
So, if you developed a program that reacts to those properties, you should update it. If not, there are no actions for you to take.
WebCore is a third-party integration, so, it’s not sure if they will migrate.
The ones created by community developers that run as Edge Drivers can. 
That won’t work after September 30. You should check in the author thread to see if anyone’s working on something for the new platform. 
What’s the deal with these edge drivers.
Is it really just a matter of downloading them onto your hub and then these devices / drivers appear within ST.
If they are official edge drivers written by ST, you don’t have to do anything. They will get automatically downloaded to your hub and matched with new devices as you add them. And there will be some kind of automatic transition as part of the cutover for Sept 30.
If you want to use a custom edge driver, you just follow a link the author will give you to subscribe to their channel, and after that the drivers you select will get downloaded to your hub. Once the driver is on your hub it will get automatically used when you add a matching device. Or you can switch between drivers available on your hub by using the ST app.
So it’s all much easier than using custom groovy DTHs was.
So for example, if I wanted to install a virtual device. What’s the process to that?
Sorry just trying to wrap my head around this new way
Right now there are two community-created edge drivers for virtual devices and they work a little differently.
As your first Edge Driver, @ygerlovin ’s might be a little easier to understand.
First you will follow a link to subscribe to that channel. This will download an Edge Driver, YG’s Virtual Device Controller, to your hub.
Once it is downloaded, you will “scan nearby” in your ST app and it will be added as a device to your account, then you will see a device tile for the controller.
Now the magic happens.
Go into the details screen for the Virtual Device Controller and it will walk you through the steps to create a virtual device.
For more details and any further questions, see that topic:
[ST Edge] Virtual Things Edge Driver
But the steps to use any custom edge driver are the same:
-
follow the link the author gives you to subscribe to their channel
-
wait for the code to be downloaded to your hub
-
use the SmartThings app to add a new device to your hub, probably using Scan Nearby. The device will automatically choose the Edge Driver if the fingerprints match.
-
Once the device is added to your hub, you can see what Driver it is using by going to its detail screen and then tapping on the 3 dots in the upper right.
- to see which custom driver channels you are subscribed to, go to
your hub device page in the mobile app, tap the upper right menu and choose Driver.
Fantastic mate. Thank you.
I’d like to start this now but feel if I start doing this now just before this transition I may screw things up.
Hi @nayelyz! I know it’s mostly just been weekend time since the question was asked, but has there been any clarification on Virtual Switches?
If I’m reading between the lines a bit, it sounds like there’s a potential distinction between Virtual Devices created via the Labs section of the mobile app vs the IDE. Will either or both of those be automatically transitioned to a next-gen platform equivalent?
And will users without a physical hub still be able to create virtual switches?
Im using the new edge simulated switches and they work with Alexa still, not sure if this will be affected on sept 30