I don’t see a way to script an automation so that the quantitative value would be reported to the virtual device. So, yeah, it just needs to be a detector that functions in the same manner as smoke. An automation based on the qualitative values is good enough for me.
One more question: You mentioned that the state change originates in Google. Exactly what mechanism are you using to send the trigger to SmartThings? The reason I ask is that I would normally want to put the smoke detector and CO detector in separate components. Can whatever you are using deal with multiple-component SmartThings devices? Reason I ask is that some 3rd-party integrations can’t, and can only deal with capabilities in the ‘main’ component.
Oh man, you’re p̶r̶o̶b̶a̶b̶l̶y right. Now that you mention it, a multi-component device will not work the way I had assumed it would. It will require creating a separate virtual device for the CO alert because the scripted automation cannot be written as to send the smoke and carbon monoxide alerts to specific components.
Awesome idea - I’ve been hunting long and hard for a way of getting my many Nest Protects to work in a post-Groovy SmartThings universe. I shall follow with eager interest.
As a novice user, can I ask a simple question: How does one download the vEdge driver? Do I need to go to someone’s ‘channel’? If so, how so. It sounds like this driver then allows one to create virtual devices with specific characteristics. I would like to take the first step but don’t know how. Thanks,
Hi. The first post in this topic has the info, but basically you go to this channel invite, enroll your hub, and select the Virtual Devices V2 driver to install to your hub. The actual driver install to your hub can take up to 12 hours to happen, so keep that in mind. But once the driver is installed on your hub, the next time you use the SmartThings app to do an Add device / Scan for nearby devices, you’ll get a new device created in whatever room your hub device is in, called “vEdge Creator V2.94”. You can then open that device and create whatever type of device you need.
I’ll add that if all you need is a simple virtual switch and nothing more, then I’d recommend using the new SmartThings-native virtual switch devices. These can be created either with the CLI or my API Browser+ web app. If you have an Android mobile device, you might also be able to also create it within the app. Otherwise, my vEdge driver has a number of different device types as well as various options within each that you can explore.
Feel free to ask if you need more help.
All custom edge drivers are installed in the same way.
follow a link that the author will give you (in most cases, as in this thread, that will be listed in the first post of the author thread).
subscribe to that channel
choose the specific edge Driver that you want downloaded to your own hub. In most cases, this will happen very quickly, but there have been some reports of it taking a couple of hours.
once the edge driver is on your own hub, you will be able to use it.
It sounds like you might benefit from reading the community FAQ about edge Drivers, which also gives you information about what will probably be your next questions, like how to tell which edge drivers are on your hub
Thanks for the quick response. I missed the link in the original post to your channel. The link text showed ‘Samsung Account’ which I did not make the connection as a link to your channel account. I’ve requested the install and hope to have it completed by morning.
In regards to using the standard SmartThings Virtual Switch, I tried it but Alexa does not recognize it as a trigger in their routines. My intent is to connect ST to Alexa to allow me to control devices that only Alexa supports. I’m hoping one of the options with your VS creator will be an Alexa compatible switch/contact.
Thanks again for your help.
Ah yes - for Alexa triggering you’ll need to create an “Alexa Switch”. then in device settings, enable the separate contact device and one will be created that will work as a trigger in Alexa. Use the switch device to open and close the contact- they are automatically linked and synced for you.
** DRIVER UPDATE NOTICE **
This update contains the following enhancements:
Virtual Smoke device: device Settings includes a new option to include a Carbon Monoxide capability; if this is selected the dashboard card will show both smoke and CO states (@Dennis)
Virtual Thermostat device: device Settings includes a new option to add thermostat mode to the dashboard card (@jonicunha)
Virtual Temperature device: device Settings dashboard setting now includes option to display both temperature and humidity on the dashboard card (@jonicunha)
- Creating a new device will allow you to see these new options. For the temperature device, an alternative to having to create a new device is to make a change to the dashboard preference setting ; this should result in the new temp+humidity dashboard option appearing once the device is updated.
- After selecting a new dashboard option or adding fields, wait a few minutes and/or try closing/reopening the SmartThings app to see the changes.
- There is currently a bug in the iOS SmartThings app that shows a spinning icon on device dashboard cards that contain multiple states. I’ve reported this, but you’ll just have to live with it for now. It does not appear to have any adverse effects other than being annoying!
This driver update will happen automatically; no further action is required.
Got it all running. I created two Alexa switches in ST. When Alexa saw them, it configured one as a switch and the other as a plug. The switch worked without a contact and the plug did not. I think Alexa tries to be too smart with the devices. In any event, I’ve redone all the Alexa automations to trigger from the new virtual switches/contacts and also update ST with the Alexa status if I initiate a change using Alexa voice commands to turn on the Alexa device rather than ST. Everything is working fine now. Thanks again!
You can have Alexa change a switch (use it in the “Alexa will…” part of a routine definition), but you need the contact if you want to use it in the “When…” part of a routine definition.
Hi, my vEdge creator is stuck creating a device, I tried deleting the Device and re-scanning but still going back to the same status. Is there a limit on how many virtual devices you can create?
Are you having a problem creating the ‘Creator’ device itself, or any new virtual device?
If the former, one thing to make sure of is that you’ve deleting any other vEdge Creator that you might have somewhere before you try to create a new one via Add device / Scan for nearby devices.
I am having issues creating an Alexa switch or any other virtual device. I made sure I deleted any old edge creator.
Try changing amount of devices you are making. My was stuck on single Alexa switch, but when I changed to 4, it created all 4
2 posts were split to a new topic: [Edge drivers] Creation of new devices in the wrong room
It’s been intermittent all day. I created three virtual switch devices this morning, some would time out, others would get created right away. Just tried again this afternoon, created a couple of virtual presence devices, same issue. The number after the name on the vEdge device would be off by the number I tried to create, so it’s like it thought they were created, but the actual device didn’t show up in my list. I just kept trying until I got the devices created that I needed.
Hi, why window shades switches aren’t working with google assistant? It says I have to configure it in google assistant settings. While in Alexa they are working.
I’ve discovered the Google Home app can’t seem to handle the Alexa switches. It sees them as switches but also recognizes the contact as it adds a label of open/closed. They show up, but if you try and turn on/off it errors out. Google Assistant will happily turn them on and off, but I can’t adjust them in the app. Has anyone found an easy work around? Not really a big deal either way as I mostly use voice control via Google Assistant which works fine.