Deleting the device and then deleting the custom DTH and then re-adding the device forced to choose the stock edge driver. Thank you very much.
Why does this matter? Will one work and one not after all the changes?
Why does this matter? Will one work and one not after all the changes?
The IDE is being discontinued as part of the changes.
I understand that but why does that matter for a virtual device that was created long ago? Will it not switch to a new edge virtual device?
I think it is a definite possibility that it will given the virtual switch is a stock DTH and a virtual switch Edge driver has been created.
However if you created the device manually you may not have assigned it to a hub in order to have a cloud based virtual switch, in which case migrating to an Edge device wouldn’t make sense.
This is actually the reason I created my virtual devices using the IDE to begin with. When I used the labs, it didn’t assign my hub and then I wasn’t able to do that in the IDE either.
I imagine the Home Assistant integration with SmartThings is going to stop working as well? I have been putting off moving all my Zigbee and Z-wave devices off of SmartThings and into Home Assistant as the current integration has worked quite well. If this change will stop the integration from working I guess I better get some USB sticks and start migrating all my devices…and all my automations too.
This whole rollout seems to have been completely botched and providing users and developers just barely over a month to make massively sweeping changes is totally unacceptable.
Hi @nayelyz
Do you have any feedback on my previous questions regarding the Routine Creator?
Can you please provide some information around the future/launch of this?
Looking through the js files at routinecreator.smartthings.com, it looks like a lot of work was done to create a front end user interface…
Is this product still within the timeline of “coming soon”?
If so, can you give us an estimate?
Or can you say if the beta will be opened to more users?
Or is this project now dead?
Thank you
Oh, I didn’t know the Labs app didn’t assign the hub. That’s surprising.
ST have never got the hang of timely explanations for stuff. We’ve clocked the virtual devices in the API, SDK, CLI and the Edge drivers. That is when we need to know the plan, as the inevitable alternative is speculation or just sucking and seeing.
No, luckily the home assistant integration is built on the API, not groovy, so it will continue to function without issue.
I was in the same boat as you though, but since I have at least a couple devices for which no Edge driver exists, I’ve ordered zwave and zigbee sticks for home assistant and will be finishing the migration over to that platform.
Maybe not.
Well over 90% of ST app users don’t have a hub: they have a Samsung smart television or appliance, all of which now use the same ST app as hub users.
I am still waiting to hear whether there will be a virtual switch and virtual contact sensor available for those in a “hub optional” configuration.
But it makes sense to me that the Labs option, in particular, wouldn’t assign a hub. 
Speaking of virtual sensors, switches etc.
will these still be available come Sep 30th. They were great and the fact they ran locally is even better.
As discussed upthread, there are some options based on Edge Drivers, but those will require a hub, which the current virtual devices do not.
I am waiting to hear what, if any, hub-optional choices there will be in the new architecture.
When you say hub, are you talking about a Smartthings hub?
Yes, SmartThings or Aeotec WASH hub. One of those is required to run an Edge driver.
When the apps were combined into one, the number of ST app downloads in the Google Playstore jumped from about 500,000 to well over one hundred million. Those new users had Samsung smart appliances and televisions, not ST hubs.
You can run a nice setup now with a Samsung smart television, Philips hue bridge (which also gives you motion sensors), Lutron Caseta or Leviton (WiFi) light switches, Ring doorbell, Ecobee or Nest thermostat, a Yale by August or Schlage WiFi smart lock, and Meross smart plugs and not need an ST hub.
This will be even more true once Matter devices are available.
Yeah I have the V2 ST hub so hopefully I’ll be ok. I hope virtual devices like buttons etc can and will run locally. I sure they will
I didn’t realise you could run all that other stuff without an hub though, that’s impressive.
Sure, there are some really nice community-created virtual devices available now as Edge Drivers. All Edge Drivers run locally.
Check the quick browse lists in the community-created wiki and look for the “virtual” list in the Edge Drivers section. 
Thanks.
I haven’t even changed or moves yet to edge. Figured I’d let ST do the merge and take it from there. I don’t see any edge drivers within my app yet.
You think it’s a good idea to just leave things just now and see what the outcome is come Sep 30th?
In general, yes, but it’s a personal decision. And if you are currently using custom groovy code (either DTHs or SmartApps) that you think will not have functional parity with the new official features, then starting your research now makes sense.
To be honest, I personally feel more comfortable right at this moment using the Edge Drivers created by the community developers, which tend to be better documented and with better bug tracking, but again, your choice.
That’s my plan. I run on 100% stock DTHs.
I had played with a few custom DTHs but none were in use. I got on the IDE a few days ago and purged every custom DTH, all SmartApps except Smart Lighting from my account, and removed all GitHub connections.