may be a silly question Todd, but how do I update the driver?
Drivers update automatically once the developer publishes a new version. You can also force an update by using the edge:drivers:install command in the ST CLI tool.
You can also compare your installed version of the driver to the most recent version using the ST CLI using the command “smartthings edge:channels:drivers” to see the most current version.
You have latest driver version but you have to update (recreate) creator device
You driver is up to date, just the banner on the creator doesn’t get updated unless you recreate it. As of this date, current version is 2023-05-17T04:17:21.217313249.
Read this post regarding the issues with the combo switch/sensor devices not reliably triggering Alexa routines and the two alternatives that @taustin created to deal with it.
Thanks, will check the post. I asked because original post lists Current Driver Version as of 5/5/23: 2023-05-05T17:22:09.83804519
Thanks for pointing this out; I’ve just updated it.
Excuse my ignorance but haven’t played with virtual switches before and hoping this can solve a issue I’m having.
I use Hue lights connected to ST connected to GH.
I use ST to setup scenes and routines and trigger them in GH. Works perfectly for me.
The issue is when my wife tries to use them. Because she shares the home with ST and GH she experienced the old duplicate devices issue. The main issue is that the scenes from ST aren’t available for her automations in GH.
Will setting up virtual switches to mimic the routines and scenes work?
Hope this makes sense…
Hi, i’m new here and i use your virtual device creator and it worls great!
Is there a possibility that you can create a virtual device that looks like a tv remote? Because i want to map these remote with the actions from the logitech harmony edge driver!
I know you have a virtual tv device but it is very limited and so useful to control a tv or an other av device like an av receiver or a fire tv stick.
Sorry for my bad english, i’m from Germany
Daniel
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.
Ahh, okay thanks anyway! Maybe in the future Samsung will make it possible for developers!?!
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
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:
@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+ !