[ST Edge] vEdge Creator: a virtual device generator for end users

If I used the Alexa switch and set it to create a separate contact sensor, what happen if I turn that setting off and then back on? I see no reason to do that, just popped into my head.

My real question is if I have a bunch of these and get confused on what I have named what, is there any way to see which switch goes with which contact sensor?

Yes, turn on/off a switch and see which sensor changed state. I had that recently where I had two sensors named the same and wasn’t sure which went to the similarly named switch.


It’s just me or virtual locks are also getting unreliable on running alexa routines?

I think possibly yes. I’ve changed almost everything over to Taustin’s seperate contact switches, including locks as I had noticed some inconsistency.

@TAustin the new IOS update fixed the issue with the Alexa Multi-Trigger switch with the creating routines and only showing trigger 1. Now you can see all the triggers under the “Then” section.


@TAustin the old Alexa Switch is working fine now. I left 2 that I didn’t switch to the new Alexa Multi-trigger and they have been working working fine for the last 3 days.

1 Like

hi - I’m using vedge creator V2.91. Three virtual momentary switches are exactly what I need to control an awning through ifttt.

I had successfully added two yesterday, but then things went south and I couldn’t see any more as triggers in ifttt after adding the third, fourth, etc. v-switch. I’ve uninstalled v-switches and the creator, restarted the smartthings app and the hub. Logged out/in on ifttt. Reconnected ifttt to the smartthings service. Now I don’t see any Smartthings v-devices when trying to identify a trigger and assemble an app in ifttt. heres the logcat, after tapping a new switch:

I’m on an Aeotec V3 hub.

Help! Any suggestions?


Never Mind! :worried:

I found momentary switches under the open / close triggers. I had been looking under switched on / off.

I also tried to tread my awning as a shade, but that didn’t seem to work with ifttt at all.

Is there any way to programme in the values of the virtual sensors created using this tool? For example, I would like to create a virtual temperature sensor that shows the average of all my thermostats.

AlexaSwitch device is unreliable for me. >50% of the time it does not trigger my Alexa Routine.

How does one add another device? I am trying to add another device to see if there is one that is more reliable. When I try adding a new “SmartThings Schema virtual device” the ST Schema Virtual Devices login page loads and when I try to create a new account its asking for a “SmartThings Approver Email”. Am I doing this wrong? Basically I am trying to get back to Step 3 above^.

See post 1600 above for reliable Alexa trigger options


Thanks @Terri_Baker. Post 1600 above worked for me. I have reliable Alexa triggers now.


I’m afraid there’s no ‘end-user-friendly’ easy way to do this. If you have some coding skills you can certainly do it by using the SmartThings RESTful API or writing a SmartApp. Unless someone has found a clever way to do it, I don’t think Rules logic is sophisticated enough to be able to do this.

My only other suggestion would be to check with @Mariano_Colmenarejo to see if he has any drivers that might meet your need.


Oh, understood. Thank you for your reply! :slight_smile:

12 posts were merged into an existing topic: Smartthings Android app ( update ) May 10 2023

Hi, everyone.
Following up on the issue with Alexa automation for certain virtual devices, in this case where the device had the contactSensor and Switch capabilities. The team checked the events in the backend and here’s the feedback:

  1. In this case, the integration tried to categorize the device based on its capabilities.
  2. However, due to the fact that having “Switch” and “contactSensor” together is not a usual case, the categorization failed
  3. When the categorization fails, the device is dropped during discovery or in this case, the event was dropped.
  4. The team cannot confirm it used to work before because the logs saved don’t go back further than 30 days, but if it was, it could have been broken by updates made to support any of the other official devices.

Thank you for the follow-up!

So, the implication is that if the combination Switch/contactSensor worked in the past, there is no guarantee that it could/should work going forward and we need to rely on single capability devices for the integration to work properly.

1 Like

Thanks for the feedback @nayelyz

So it would seem that the changes that @TAustin implemented for multi trigger and/or adding the synched/separate contact switch are the long term solution. The only question i have based on @nayelyz feedback is whether the base combination of the switch and contact sensor may put the switch functionality at risk at some point given her comments that multiple devices together may cause issues and are not supported. Does this imply that a long term reliable Alexa Switch should be a standalone switch and a standalone contact sensor kept in sync by the driver?

The Alexa Multi-Trigger, a pure contact switch, could be the safer solution than the new combo bearing in mind that

happened and could happen again.