New app Virtual switch

I checked with the developer and he concurred. I think I’ll start the process of rebuilding these directly in the IDE.

1 Like

A lot of you say that removing the v device creator will uninstall/delete child devices created, without trying to sound stupid but what happens if i dont delete the v device creator ? If i hit the dreaded migrate button will my classic app v devices continue to work on the new app without issue now and crucially after the groovy ide gets nuked in the future ?

At the moment i use both apps, 98% classic 2% new app and v devices show and work but no sign of an in app v device creator

Yes I saw that. The risks have probably dropped dramatically now you know what could happen but we can all do stupid things. The usage checks also help but you don’t see Automations and Scenes in the ‘in Use By’ list, and nor will you find Alexa and Google there any longer. So they may not be the safety net they were.

1 Like

Paraphrasing your question “If I migrate without deleting the virtual device creator will it still work?”

For me, yes. I migrated with it in place and it still works as expected.

Just migrated, checked to see if the v switch creator had come across which it had, however now going back into smart apps. Its gone ? Kinda stumped now

Im going to correct my finding, the v switch creation app is present in the new ST app but here is my confusion, if you use the + sign which at least to me indicates your creating something new, under “Smart app” the v switch creator is not present, however if you tap the left top 3 bars and then “Smart apps” the v switch creator is a aparent and useable

Tad confusing, at least to me, Smart app and Smart apps, one is plural but how does that logically indicate the users requirement

I cant find this V Switch Creator anywhere…I am new to ST and am using the new app (as far as I know). Question: is there any difference in where the Virtual Devices are run depending on if you create them in the IDE or ‘locally’ in the app w V Switch Creator? I can see they are cloud-based when creating them in the IDE. Trying out ST as also being alarm hub with an 3rd party external GSM transmitter/reciever (no/nc ports) and ‘poor man’s UPS’ for ST hub (Powerbank with possibility to feed when charged). So really interested in running all needed intelligence locally at least for this functionality.

If you create them in the IDE and use device type ‘Virtual Switch’ then they can run locally on the hub. Just about any other option runs in the cloud.

I see a virtual switch creator under SmartThings Labs.

To get there, Hamburger menu > Smart Apps > three dot menu (top rt) > SmartThings Labs > Virtual Switch


Smartthings is still primarily a cloud-based platform. Even if you maintain Internet connection, if the smartthings cloud is unavailable (which does happen from time to time) then you will not be able to get any notifications from the system and you will not be able to change the mode from arm to disarm, etc.

They also have historically pushed out hub updates about once a month which can be neither deferred nor denied and which will take your system off-line. It may be only a couple of minutes, but sometimes it has been a couple of hours.

So it doesn’t meet UL standards as a security system and it’s not something most people would rely on as their primary. It’s OK for convenience updates as long as you understand the potential issues.

OK, all of that said, there’s no difference in where you create the virtual switch. The specific options in the DTH which is used might vary. But you aren’t creating them locally if you use the app: the app itself is cloud-based. It doesn’t communicate directly to your hub even if they are on the same Wi-Fi network. (Technically they didn’t have to design that way, but they did. The app requires the cloud.)

The virtual switch creator was custom code which I believe is not available in the new V3 app, but you can still create virtual switches in the IDE.


Ahh…I accidently created my switches as ‘Simulated Switches’…that type of device seems to share functionality w device type ‘Virtual Switch’ except all Simulated Switch devices run in the Cloud. I’ve however changed all my previous Sim Switch devices to be Virtual Switches now and it works great! Many thanks Nathan!


Many thanks for your valuable input in this! @JDRoberts

1 Like

When you create Virtual Switch in Labs, just go to IDE and add hub, to that switch. Than switch becomes Local. Smartthings “hub optional” approach creates Virtual Switch without hub, and that results in Cloud Virtual switch. See example below


I do not have any Smartthings Lab option !!!..Silly regional dumb stuff (México) ?..

Tap on 3 dots, and it should be there

1 Like

Smartlabs is not available in all areas… God knows why !

1 Like

Thanks my friend !! Im there …but for me only DELETE (Eliminar) and CANCEL option are available, I remember in Classic App Smartthingslab was avaliable, but not anymore… >=(

Labs is USA and Korea only


How do you update the virtual switch?
I’m able to create it but I can’t find where to set the switch to control a group of lights.

There are a couple way to do it but one way is with an Automation. New automation, IF, virtual switch - On, then . . . . .

1 Like

I don’t have smartthings labs in my region so I logged onto my smartthings account using the following link.

Created a virtual switch using made up Device Network Id *
Virtual switch / Simulated switch
Self published
My location
My hub

While I was there I made a heap of generic ones for use later just incase this option becomes unavailable later, which seems to happen a lot with smartthings.

Speaking of changes…SmartThings has announced that they will be discontinuing the Groovy cloud soon, so anything you created through the IDE, including your stockpiled virtual switches, will no longer work when that happens. In fact, the IDE itself will be going away.

The replacement for Groovy DTHs will be Edge Drivers, written in the Lua programming language, which will run on your own hub.

One community member has already created an Edge Driver to generate virtual devices, so many people have switched to that method.

Of course, Edge itself is still in Beta, so all Edge Drivers are in beta right now, but in terms of futureproofing, Groovy won’t be much help. :thinking:

Originally the Groovy cloud was supposed to be discontinued at the end of 2021. Obviously they missed that target and haven’t announced a new specific date, but the changeover is coming.

Official announcement (the topic title is a clickable link)


More about Edge:

FAQ: I have no idea what Edge is. Is that a new developer tool? (2022)

Edge Driver to create virtual devices for the new architecture: