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

A post was split to a new topic: Best method to synch virtual and physical switches?

The ability to replicate a remote is dependent on what capabilities and GUI is available from SmartThings, and right now they don’t have anything available to do that. SmartThings is using a custom GUI for the Samsung TVs that is not available to driver developers. It was only fairly recently that the media controls capability has finally started fully working, but the channel up/down or volume up/down controls have no graphical elements available.

1 Like

Ahh, okay thanks anyway! Maybe in the future Samsung will make it possible for developers!?!

1 Like

Todd I have just noticed this on a Virtual Momentary Switch They are the two newest ones I created maybe 3 weeks ago all the older ones look normal

I am seeing the same thing in the “If” part of routines and the following in the “Then” parts.

This has been an on-again off-again problem for multiple edge drivers for a couple of months. Discussed with smartthings staff in the following thread:


1 Like

@NickA and @Paul_Oliver

This is definitely an app or platform bug. I see it too.

As @JDRoberts says above it is known but I’m surprised it was reported months ago and appears not to be fixed. Thankfully I don’t think it affects the actual operation of the routine or device.


Correct the routines are working.

Yes, Everything seems to work fine. I was just confirming what Nick reported.

I know that TAustin has put in lots (LOTS) of work to continually be updating his drivers. I have two general questions for him and the community.
First off, how can I support his effort either via contributions, or anything else, and furthermore I don’t have a problem with doing that…in fact, I think it should be “recommended”.
Second, with the changes we’re seeing, as with Matter, and other things, is there a chance of creating these drivers for use, and then going into a forced “pay to use” model. I don’t have a problem with the pay process, just want to prepare for whatever the “future” looks like?
Again, not trying to stir anything up, but this kind of seems like what Smartthings is indirectly doing…they say that they never really supported virtual Alexa type interface, but obviously knew it was happening., and certainly sold a lot of Hubs because of it.

If this is not appropriate for this thread, then feel free to move it.


And - Not just the drivers, also the (incredibly useful) API Browser+ !


Thanks for asking :slight_smile: . See my ‘Buy-me-a-coffee’ link in my profile.

I can only speak for myself here. I think in order to be able to implement anything like that you’d probably have to first go down the path of getting your driver/SmartApp “certified” by SmartThings, which is a process I have not really explored. Maybe there is some mechanism that SmartThings provides once your stuff is on the officially supported list (and showing up in the app in the manufacturer’s device listing), but likely not, as most sw just comes with the purchase of the device.

But for run-of-the mill community-developed drivers, I can’t see an easy way of implementing or enforcing something like this. It would have to be a manual process, and a big hassle to manage and maintain.

Cloud-based drivers and SmartApps are another matter: because they are running on the developer’s platform, there may be more possibility to implement some kind of key mechanism.

It’s a good topic, and if you want to continue a discussion it might be best to create a separate dedicated thread.


I think you have already taken the most important step, which is to consider the implications of using community/third-party software. Just about every day, sometimes several times a day, naive users are being redirected to community Edge drivers as if it is no big deal and it pains me to see it.

1 Like

Thanks to both of you along with many others who have taught me, albeit slowly, what I’ve needed to know to do the simple things that I use I SmartThings for. I was an Assembler mainframe programmer for 40 years, and am doing my best to understand the concepts and basics, of this “Edge stuff” and nothing else…K.I.S.S.

The “future” comment was relative to my thought process that conceptually “I’ve been in bed” with SAMSUNG for about 10 years and it looks like I’ll be at least inviting TAustin to join us. As of now it looks like I’ll be using/converting all my virtual switches(15-20) to the vEdge driver, and I’m ok with that….it just made me think :thinking:

I do need to see what the “matter” discussions are here and maybe start a thread about opinions and maybe facts on its future and directions….for instance, is it Edge drivers.

Thanks for all the help, the reply, and for supporting us community members.


As of right now, Matter devices have Edge drivers like you see here:

From another topic discussing Matter, we’ve already seen that just because Matter is a “standard”, it doesn’t mean each implementation will support all capabilities of a given device (just like today). The Third Reality Nightlight has the ability to turn on/off, change dimmer level, and change color. ST as a Matter controller can only control on/off and dimmer level. Echo devices as a Matter controller can control all three. We also know that ST hasn’t committed to provide bridge support as of yet. So at the moment, I still see there may be a need for 3rd party developers just like today.

Here are a couple of threads discussing Matter you might find interesting.

Matter Device Support - ST platform

Matter - smart home connectivity standard (formerly Project CHIP)

I hold out hope that Matter will make things simpler for the home user, but I’m only cautiously optimistic at this point in time given what various manufacturers have delivered to date.


Hmm… For my monetary buttons, it looks like my routines are showing code instead of on/off. Am I the only one?

No, this is a know problem that doesn’t affect the operation.


Just wondering, has anyone found a way to supress the Alexa multi trigger contacts from the contact tile in the smartthings dashboard? With all the added contact sensors it’s very busy now. You can filter them but the filter dosen’t appear to stick after exiting and returning.

Very easy in Android. Click on the mini tile and when it opens click on 3 dots and then
deselect the items you don’t want.

Yes but I mentioned the filter does not stick. At some point hidden devices appear back in the tile again. Are you seeing that as well?