Just realised I took no notice of good advice regarding virtual switch creation, that or I just plumb forgot but I have been happily creating virtual switches with one of the V switch smart apps over the last few months, I now have around 40 damn v switches
I’m stuck on which way to go, do I recreate each v switch using IDE v switch type or do I stick as is
I have just realised if the v switch creator gets removed from smart apps in the future I loose the child v switches BUT if I recreate all v switches to the IDE version, if the IDE goes away as is commonly understood in the future, will IDE v switches vanish as well
None of us know what will happen with virtual switches once the IDE goes away. I have asked this question of staff members now three times in the forum and just never gotten any answer at all. So maybe they don’t know yet.
Virtual switches can be created in the SmartThings App already without having to use the IDE. Navigate to the SmartApps tab → upper right (hamburger) menu → SmartThings Labs and there is a virtual switch option in there.
Nothing is happening to the IDE soon (and we will give plenty of heads up when it does). Existing virtual switches should not be impacted by any changes.
I don’t use Alexa so I can’t check that part of it. However, I just created a test virtual switch using this method and then checked the IDE and the type is listed as “Virtual Switch”.
In order to trigger an Alexa routine, you need a virtual sensor. It’s OK if that device is both a virtual switch and a virtual sensor, which is the DTH that most people use.
Yes, thanks, we know one can be created through the IDE. The open question is what is the plan for virtual Switches once the IDE is no longer available, which is part of the long-term roadmap for the conversion to the new architecture. It’s not going to happen immediately, but it may well happen this year. But it may be that they haven’t decided yet, they haven’t fully completed plans for Zigbee and Z wave devices yet.