As always, you never disappoint, you have no idea how grateful we are and how many smart homes you just saved. BTW, here is an Idea for your next video. We were wondering about some other handlers such as (the Lan device trigger, Lan device monitor, Web request multi-tasker, etc... ) They sound like awesome helpers, but we still have no idea what they are or what they do. It would be a great help if you can do a deep-dive tutorial for the rest. And several of my smart home enthusiasts from Dubai are huge fans of all your content, so keep it up Sensi
Wow! This is huge! This type of video is why I support your channel. I only wish that Samsung had added this feature rather than relying on the community
Thanks, Brian. This obviously didn't come from Samsung who continues to be a huge disappointment with their recent "announcments' but it works and thank you for sharing it. I went on to see if the created virtual devices (I made several types) were available as triggers or actions in IFTTT using SmartThings and none were available but it might have been me. On another positive note, though, the virtual devices do show up in Homebridge using the SmartThings plugin so that means the're exposed in Homekit as well as Alexa. Awesome job, my (our) friend!
Hey Hugh! Ohhh, I think some of the Samsung announcements are really good. It's not perfect by any means and they're still playing games that we don't want, but some of it is really good. And yeah, these are just Alexa devices. Or at least that's all I meant them for! That HomeKit thing is a happy extra!
Fantastic! I have a couple of SmartLife switches that work with IFTTT and not SmartThings (Rookie mistake). Instead of replacing the switches I created some virtual switches / IFTTT work arounds. Looks like I’m going to make some updates!
Your content is simply fantastic. I've had at least 3 times I needed then did not this functionality. But knowing you created this video and I can return to repeat these steps is ever so appreciated. Thanks so much.
Hi Brian. Thanks for the detailed step-by-step on this. Many of us have wanted a Widget on an Echo Show 15 to trigger an Alexa Routine via a touch on the screen. I now using a vEdge Virtual Contact/Switch in the Smart Home Favorites Widget to trigger an Alexa Routine.
What is the difference between, for example, a virtual switch created with this edge driver, as opposed to a virtual switch created via the Smartthings Labs option? Which is better? Thanks for your great work here - really appreciate it!
This is for a specific purpose, and not officially supported. So I'd use it for that specific purpose. If you just need a switch, use the labs one. Official support and there's more to come about those ones.
I don't have any Alexa simulated switches but I do have a lot of virtual switches going through ifttt in order to trigger Alexa routines. I'll be replacing all of those with this and have one less potential point of failure in my automations. Very useful!
I love to see a video on how to add Amazon automation to smart things,from start to finish. This is a good video, but I am setting it up now from the beginning.
How can I trigger a SmartThings Routine from Alexa. For example, Alexa recognizes Ring Smart Lighting Motion Sensors, but SmartThings does not. How can I trigger an Aeotec Siren on SmartThings when the Motion Sensor Goes Active on Alexa?.
You can use these virtual switches in a routine in Alexa. So Ring Smart Lighting Motion Sensor goes on = SmartThings Virtual Switch On, then in SmartThings IF SmartThings Virtual Switch On, THEN trigger Aeotec Siren.
@AutomateYourLife it works! Thank you Brian. I'm currently using ten of these switches. My house got lame for few weeks without my "amazing deviea". Now it's back!
@AutomateYourLife I like how you said that some may even not know what are you talking about 😅 and that's 100% true right there. But that other group like you or me, it's critical to have that running and working. This works way faster than the previous "amazing device" version, I got that from you 😉 and it's way easier not to create button, don't have to go on my computer anymore! Huge thank you! 🍺 🍻 🍺 🍻
I had routines using simulated switches using thje old groovy protocol to turn Alexa guard home and away based on ST phone presence sensors but when I tried replacing with the TAustin v edge simulated contact sensor last month, I never go it to function right. Guess I'll try again.
@@AutomateYourLife thanks for getting back. The device shows in main devices list but not in available devices when I try to change trigger in Alexa routine. I'm using iPhone if that matters. Thanks, Brian!
Brian: Awesome video as always! Thank you! Now I can reanimate my pseudo smart home alarm. Brian: please add the new Amazon Alexa remote to your Amazon Affiliate page so I can buy it through you & support you.
Thanks Reid! You know...I got lots of work over on that Affiliate page. For now, Alexa Voice Remote Pro - geni.us/AlexaVoiceRemotePro (Amazon affiliate link)
Awesome video. On Alexa I was able to use the contact sensor just fine, but when I use the door sensor I can only figure out how to trigger the virtual switch to lock as default action. I can't figure out how to open, close, or unlock the virtual switch. Any idea how to change this?
Hi Brian, only just happened upon your channel. I currently only really use Amazon Echo devices to control lights, receive ring doorbell alerts and control a set of gates with a WiFi linked jog module. I do however have a Samsung S21 with the SmartThings app and I was wondering if there was a way to create a routine within the SmartThings app that will trigger an Alexa routine. My use case for this is that my car has an Android Auto enabled head unit, and within the AA configuration, it is possible to add a shortcut to Samsung SmartThings so I was really hoping that I could create the SmartThings routine, display it on the car screen and when I get home press the short-cut which would talk to the Alexa app, and run the routine to open the driveway gates. All a bit convoluted, but since there is no Alexa support directly within Android Auto, it seems like a possible workaround - however, although I have enabled the SmartThings skill inside the Alexa app, I can’t find a way to achieve what I want. Might this be because I do not have a physical Samsung SmartThings hub? Any advice you can give would be very welcome.
Hey Mike, you're exactly on to it when you say that it's because you don't have a physical Samsung SmartThings Hub. The SmartThings Hub will give you access to this Edge Driver (Edge Driver is just a fancy name for teaching a hub how to work with something). That Edge Driver allows you to make a fake device, called a Virtual Switch that you can turn on and off with your shortcut button. That Shortcut button would be a scene you create in SmartThings. The Scene turns on the Virtual Switch, which you use to start an Alexa routine. But an Edge Driver is required for this method to work. Some people will tell you that you can just make virtual switches with the app, but it won't work right...and based on what I know it won't work for long. Get a hub. Aeotec or SmartThings Station.
Excellent video! This was my number one concern when I learned that Groovy was going away. Maybe you could help me with an unrelated question. I need a smart plug with energy monitoring where the energy monitoring works natively in SmartThings for automations. I bought a Kasa KP115 but energy monitoring does not work natively and requires a customer device handler. Any recommendations?
And an outdoor set of them in this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Iy7dOmRrFgU.html Plus a whole power bar with energy monitoring
@@AutomateYourLife Thanks for the response! I took your advice and bought the Zooz plugs as well as the Tilt/Vibration Sensor, the Open/Close Contact Sensor, the Temp/Humidity Sensor and the ZSE18 motion sensor to try them out. 3 of the 4 devices (not the Temp/Humidity, that showed up correctly) show up as Aeotec Door/Window Sensor 7 Basic when I paired them to SmartThings. I paired with and without QR code with the same results. I removed them from the hub and repaired with the same results. The Tilt/Sensor I was able to change in the IDE in the Type menu, but the other two devices aren't listed. I've used Aeotec exclusively since getting into ST a year ago and am kinda disappointed. Any ides?
This is very helpful. I was wondering if this will be necessary once SmartThings adds Thread or Matter or whatever combo of the two? I have about 6 of these virtual switches integrating all my automations and stuff for both HomeKit and Alexa. I duplicate all automations using the same voice commands between both eco-systems. But I do not want to waste time recreating these now if I would have to do it again once each ecosystem sees the other's devices. Thoughts? Also I had read Samsung would start deploying the new firmware starting last night, but no dice for me. Is there a way to trigger a firmware update on an Aeotec hub v3?
Adding Thread and Matter won't change what happens to Groovy. Groovy is going away and when it does, if you're using these specific Alexa Simulated Switches, they will die. So it's a fix for that, not for overall Virtual Switches.
Great video ! I"m trying to create a water sensor in Vedge, i get that to create and it shows up in smartthings and Alexa. but when making a routine in Alexa it doesn"t show the water sensor switch. but it when i create a contact switch it shows up.
Right and that's because of Alexa. You have to use the right kind for Alexa routines. So just use the contact sensor but turn it on in Smartthings when your water sensor shows a leak. So water leak sensor in Smartthings -> Contact Sensor Virtual Device Alexa routine triggered by Contact Sensor Virtual Device
This looks really interesting. Just a thought, as it's created on the hub, unlike the Groovy virtual switches, does that mean it is stored there? In other words if I then for whatever reason get rid of the hub will I still find these new virtual switches on my account? I should mention because I have never been a user of a Smart Things hub, although I like the app and use it a lot.
Yeah that's totally the case. It's an Edge driver, so it's going to live on the hub itself. There are still the base Virtual Switches available, but they won't work this way with Alexa sadly. So it's kinda...one or the other now. However, if you watch this video...you're going to end up with a Samsung hub in your home: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-tgXetdqhXt8.html
@@AutomateYourLife I'd already seen it - great analysis as always! But TBH I was almost decided on buying the hub but have now stalled. Disappointing that Matter is still not being used to open things up as was originally envisaged. So for the moment continue watching your videos 👍
Thanks for the video. In old times, Smartthings Alexa Switch is trigerable (and run routine) even without hub, just purely virtual device run in cloud. Anyone know the idea is this is possible still? Thanks
@@AutomateYourLife Thanks for replying. Yes, you are right, we still can create a virtual switch and Alexa can detect this virtual. However, not able to create a Alexa Routine for this virtual switch (such as when On and Off). I guess this is a limitation that we cannot bypass
Thanks, Brian. I was able to follow your tutorial and get these working... However, They behave slightly differently from Alexa Simulated Switches that I was using before - While we get Switch and Contact sensor functionality in SmarthThings, when adding to Homebridge they only show up as Contact Sensors not Contact sensors AND switches so there is no way to turn these on and off in HomeKit. Any ideas?
Thanks for the suggestion, Brian! The “garage door” actually is a combo switch and contact sensor. I played with that solution for a while until I realized that HomeKit actually sorts garage doors in the security group. Which caused other problems since I am actually just using my simulated Alexa switches to trigger music streams in various rooms. After some experimenting, I was able to add both a virtual switch and virtual contact sensor through the vEdge Creator. I gave them both the same name, and then I created a SmartThings Routine linking the two so that when the switch is turned on or off the sensor, acts the same. This is the same functionality I had before. This gives gives me dummy switches and contact sensors that act as one in HomeKit and allows me to trigger my Alexa routines through switches in HomeBridge/HomeKit. Hallelujah! Thanks again for the videos and all of the updated info - I have now removed all of my nonEdge custom device drivers and everything works as before - ready for the decommissioning of the Groovy IDE. Hope this helps some one else’s use case to create HomeKit Switches that trigger Alexa Routines via SmartThings.
Generic question: I've enrolled in a couple of these community device drivers. Do they update themselves automatically (when an update is available)? Or do they have to be updated manually?
will you be able to add it to use it in the cloud because i do not have a smartthings hub my simulated switches at the moment runs in the cloud and not locally
Is there anyway to implement a virtual switch now without a hub? Can a PC or smartphone host the code rather than a smartthings hub (my TV is 2021)? I had been using virtual switches before (Amazing Devices), but they all quit when smartthings shutdown the cloud. I hate to spend >$100 merely to host a couple simple automation. Thanks
Hi. I have a question: is it possible to link Alexa App with SmartThings without duplicating all the devices and routines etc? The only way I know how to connect both is via the Skills in Alexa and Linked Services in ST but this causes duplications. Thanks 🙏🏻
At the moment, there's not a way. The routines won't duplicate but your ST scenes will and so will devices. ST is aware of it but haven't fixed it in a long time
@@AutomateYourLife thank you. That’s frustrating as I’d like to use SmartThings for an easier interface and some slightly more complex routines but with the ease of use of the Echo for the family generally. Great content btw and thank you for replying 👍🏻
I thought these new vEdge Switches and Contacts sensors all ran locally now? I create several Contacts sensors and switches using VEdge but when I went into IDE, says execution are in the cloud. Had another question: How would vEdge Door work with a real door lock like Schlage’s Connect zwave lock and door sensor like SmartThings’ multi-purpose sensor?
@@AutomateYourLifeOh ok. So vEdge switches basically all run locally, in spite what IDE says. That’s a relief and will save me lots of time trying to figure out what’s wrong. Lol As for the vEdge Door question, at 5:57, it shows Contact and Lock state, but where I’m confused is that these are essentially just virtual. How would this virtual Door know the actual physical state of the door lock and door sensor? Unless, your linking in to other devices there via a routine? And thanks again for all the support!
Can i use virtual switches on bixby to trigger alexa routines without a samsung hub? My home automation is all on alexa and my devices are not smart things compatible. Also, i have a samsung smart washer which doesn't send out announcements of cycle complete to alexa and I've been doing that using virtual switches using the groovy platform. Hoping to recreate it once groovy dies. As the Virtual switch creates from the smart things app shows in the alexa app but is not allowed to trigger alexa routines.
I have been using numerous Vedge (virtual contact sensors) to trigger Alexa to announce messages. I recently added two more, but they intermittently trigger the Alexa routine. I need to investigate if previous Vedge switches are acting flaky too. I see that others recently are having similar problems. Have you heard anything about this issue and do you know of any resolution?
You're the second person to tell me. Not sure what's going on but I haven't had a problem yet so I can't help right now. Waiting to experience it myself
So can I use this to control Amazon Alexa smart plugs ( gen1) with smartthings and by extension Google home/ assistant? seems like you could , and have an amazon smart plug in a room group via the virtual switch and Alexa routine so that I could use Google home/assistant to control an Amazon Alexa brand smart plug as part of a room group via a virtual switch?
@@AutomateYourLife Ok thanks Brian ,yes I have the aotec hub Glad I can make use of them because I was going to sell them because I don't like anything I can't control with both assistants
Strange enough post Oct 15th my virtual switches and govee lights still work. I have hubitat waiting for the crash 🤣🤣. Was there a delay on the groovy depreciation?
Actually I just found this and makes sense why my stuff is still working. Oct 15th · Update IDE to only allow updates or deletion of existing DTHs · Disable the ability to add new SmartApps · Remove the IDE debugging tools (Live Logging and IDE simulator) December 12 · Start migration of 3rd party DTH’s to a ST-owned lua driver if they fingerprint match, if not will move to the Thing driver Dec 31st · Shutdown custom Groovy DTHs · Shutdown SmartApp execution · Removal of SmartApps from catalog · Graph IDE access will be limited to read-only Q1 of 2023 · Complete 1st Party DTH migrations · Shutdown Graph IDE
I'm relatively new to this, and don't have a hub (just using the ST app for some basic automations). Will this prevent me from installing these virtual devices? i.e. do I need a hub? Thanks!!
This method does require a hub, however I believe at this time you could use some basic virtual devices available in what's called the Labs section of the app. Those won't allow you to do this method of starting Alexa routines though.
Too bad the Harmony remote with smart control cannot trigger a 'contact sensor'. Can anyone recommend a remote control that works with TV and SmartThings? Or how to trigger Alexa routines with device that is not a contact / motion sensor/ lock? I have a workaround where I create two virtual sensors, one that Harmony recognizes that then triggers Alexa via an extra ST automation. Klugey but works.
Edge Drivers are now out on almost all SmartThings Hubs, so you shouldn't need to enroll in the overall program. Just the one for the special Edge Driver being used here. The virtual device one.
@@AutomateYourLife Thanks for the reply! I am looking for the one in this video though. Ultimately, I'm trying to get amazon routines on my apple watch. any guidance is much appreciated!
Would it only affect my ability to create new Virtual contact sensors OR would it cause my already created Virtual contact sensors to no longer work? If yes, what would your advice be on choosing a “reliable” option. I hope this creator leaves it there for good but it seems like this one creator holds a lot of control of big parts of my automation. I wish SmartThings made it part of their app. Thanks
Well, I'm stumped. Followed the steps right up to the point where I scan for nearby devices. The scan always ends with 'no devices found'. In your video you said you had to try it a few times to get it to work. I have tried many times with no luck. Is there something I'm missing?
You'd need an Edge Driver for it. If you can't figure out how to change it or it's not letting you in app, use this web app in this video as it lets you change Edge Drivers quickly and easily: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-4MZEPIiWHJ0.html
@AutomateYourLife I watched video no matter which driver I choose the devices don't show and commands and I don't see the edge driver. I did enroll the vedge and have added those devices in the smartthings app I just don't know how to pair those to these old devices.
Hello, I decided to give this another shot. This is to control my iaqualink pool controller connecter to Alexa via smartthings and Google home. I've successfully got my edge contact switches working between smartthings and alexa. But the switch in alexa will not trigger the routine for pool! If I trigger the routing manually in the alexa app it works. But the routine will not trigger from the alexa switch! Makes no sense. Also my alexa app does not have a change trigger option when editing. Any ideas? Thanks!
I have found some bizarre behaviour using any of the virtual switch opens available. Using the Amazon/Alexa Switch available in vEdge driver I am able to set up the relevant routine and this works when testing through the Alexa app (Manually turning the switch on or off), I also seem to be able to get this to work 99% of the time when triggering the vwSitch on and off in the smartthings app, but for some reason when a device triggers the vwSitch this doesn't seem to play the Alexa routine. For example, I have a motion sensor that includes light level, I have this trigger a certain light level and motion to trigger the vwSitch which Alexa then uses to play a routine and turn my lights on. When I trigger the sensor I can see the vwSitch turn on in SmartThings and Alexa (The same as if I manually turn it on) but for some reason Alexa will not play the routine. It seems really odd as it can see the status change and manually doing this does work! Has anyone experienced similar issues? I can only assume the fault is with the sensor triggering the routine but as far as smartthings and Alexa are concerned the vSwitch is triggered. Very odd!
That IS very odd. Not sure what's happening for you here. It seems fine for me though, as I was just testing it the other day. Maybe try a dedicated Alexa Switch. That's a new type to create here.
Regular virtual switches will be fine and you don't need a hub. If you're using the specific Alexa Simulated Switch and need to replace it, then you would need a hub to use this. I haven't found anything that doesn't so far.
@@AutomateYourLife Thanks so much for the video. Your last one was a lifesaver for me! However, I’m a right that this means that those of us who use Simulated Alexa Switches without a hub are, for the moment at least, left without a working solution? For example, I use one of the old type of simulated switches to trigger an Alexa routine that turns on my HTPC. I can therefore trigger this from my Harmony remote. Is that gone for good?
I previously bought a SmartThings hub. Samsung removed my hub from my account and discontinued it. Why would I buy another hub when I've been burned before?
@@AutomateYourLife Disabling working hardware doesn't feel right to me. Neither does trashing it. How long before we have to dump the new generation of hardware in the trash because samsung declares it so?
I gotta say, the new SmartThings web interface seems to have ditched a ton of functionality and replaced it with trendy graphics that don't actually do anything useful. Kind of disappointing.
