My biggest fear with the impending shut down of Groovy and the IDE was the loss of Virtual Switches and Simulated Alexa Switches.
I connected to your channel, selected the vEdge Creator and ran scan nearby. It silently created the vEdge Creator in No Room Assigned. Using settings in the vEdge Creator I created a virtual contact which includes an on/switch.
I was able to use the Edge virtual contact to trigger an Alexa routine. An added bonus was that the ST automation using the virtual contact runs locally.
The author of this thread just solved many users needs. This should stand as an example for all.
I’ve been up 3 hours past my bedtime converting all of my groovy virtual switches to these. …updating IFTTT recipes, WebCoRE pistons and ST automations (and other VSwitches that are linked to IFTTT and Harmony, vacation virtual switches, groupings…etc.,)
Yes. I just noticed when I added more switches that they’d all changed to default. That has been reported with other drivers too. Previously it has taken several hours but this took less than one. I’m assuming the app is being eccentric again.
I created 1 contact and 1 switch just as a test, I have not yet enrolled them into an automation, at the moment mine still show correct icons
IDE shows placeholder for all 3 items, Vedge creator and both created v devices
Also of interest , at least to me, the vEdge creator does not appear as a device in Home remote but the 2 created devices do and are fully functional, exactly as I would hope hmm both appeared with a light bulb icon though instead of the correct icons, not a problem as they function as expected
The IDE is a part of the legacy ecosystem and that only really has the concept of device type handlers for devices. Device integrations made using the current ecosystem present with ‘placeholder’ device types in the IDE to keep it happy.