We have not been told yet exactly what’s going to happen with the current groovy virtual devices and whether they are going to be automatically transitioned or not. But there are alternatives for the new architecture.
Edge drivers are only available if you have a hub (the old virtual switches created through the IDE did not require a hub). But if you do have a hub, there are several options. You can find them on the virtual Devices list in the community-created wiki. Each has somewhat different features, so different people use them for different things, but many should work to trigger Alexa routines.
How exactly did you create them? It’s definitely possible with some of the edge drivers, that’s a very popular use case.
It’s probably best to ask in the author thread for the specific edge driver you are using, but in most cases, if it is one of the community-created options, the device will have both sensor and switch capability. You can turn the switch on and off with an automation. And you can use the sensor as the trigger in an Alexa routine.
BTW, this is exactly the same way it worked with the old groovy devices. An “Alexa switch“ was typically a virtual switch that also had the sensor capability. Turning on the switch made the sensor look like it was open.
Virtual switches (both the built in one under Labs and the popular community drivers) do not appear under the trigger list for Alexa routines anymore. They used to appear if they had a contact sensor component that mirrored the switch, but it looks like that’s been filtered now.
I may not be understanding correctly, but virtual switches with built in contact sensors appear in Alexa as they always have for me. They are still able to be used as a trigger. No change for existing or creation of new.