Currently, it’s one combined device that gets created, but you can just ignore the value/control for the one you don’t need, AND you can configure which (temp or humidy) you want to see on the dashboard.
Thanks. Just an idea for a future version.
When I create new devices, does this use up more memory on the hub? Or is it just installing the driver itself that does that? I am sure the devices count against the device limit, but all of the sudden dawned on me that each device might add to the driver “load”.
Most of my legacy virtual switches stopped working yesterday and I’m trying to decide between using switches from this driver and creating stock ones in the new advanced web UI. Besides the web ones being cloud based, I wondered about RAM usage. For the switches I am replacing I don’t need Alexa integration.
I would recommend using the “native” SmartThings virtual devices - especially simple switches - if they meet your needs and you don’t mind them being cloud-based (i.e. not local); or you don’t have a hub.
As you point out, these Edge-driver virtual devices do indeed take a device “slot” and count towards the driver and device quantity limits imposed by SmartThings. Although actual load on the hub is quite minimal. I can’t be very specific about actual hub memory usage but I don’t think that’s a cause for concern.
For more sophisticated virtual device types, controls, and features, that’s where this driver can be useful.
3 Likes
Thanks. I forgot to mention, I’m already using your driver for some Alexa integration, but only needed that for a few. Does that change your answer since I already have the driver installed? I just didn’t know how it works when the base driver already is installed in terms of resource usage when you create new virtual devices that use that driver.
Excellent work on this driver, and thank you very much for your time and effort! The super quick turnaround on the Alexa debacle was much appreciated.
No problem using both the driver and the native SmartThings virtual devices. They are quite independent things.
1 Like
Morning all - trying to figure out the best virtual device to use that google home can use. I want to setup routines that run after a virtual switch is triggered. Problem is that the switch stays turned on so the routine doesn’t run the next time it is triggered.
I tried momentary on but google home can’t see it.
Any ideas?
Hello. I’ve been been using the SmartThings to Home Assistant integration for a couple years now. I recently cleaned up my old virtual switches in ST and came across this new driver to create new ones (momentary buttons). Within ST these seem to work fine. But for some reason my HA integration does not see them. I was curious if anyone else uses the HA integration and has any experience with this. Thanks!
@TAustin Alexa switch has an automatic reset option under settings.
1 Like
Hello. I’ve been been using the SmartThings to Home Assistant integration for a couple years now. I recently cleaned up my old virtual switches in ST and came across this new driver to create new ones (momentary buttons). Within ST these seem to work fine. But for some reason my HA integration does not see them. I was curious if anyone else uses the HA integration and has any experience with this. Thanks!
In case anyone else stumbles on this. I created a switch and that shows up in HA so I guess momentary buttons are not picked up by the integration.
You can add to routine one additional action that turns the virtual switch off after delay. Then the virtual switch is ready for next time.
Thanks for everyone’s help - is it best to use the Alexa one, edge virtual or native in the web API?
I see the problem. Google must not like the contacts included in the Alexa Switch.
Thy taustin’s standard virtual switch with this simple routine to reset it. I tried it and it works in Google with no errors.
1 Like
Legend thanks mate - tried that and all working well. Appreciate the help
4 posts were merged into an existing topic: Creating a presence sensor in a vEdge
This is great! Thank you TAustin you’re a star! I had been using your previous driver and created 3 Alexa routines to speak when the Alarm was triggered in various states but only the last changed Alexa routine would work, the other two stopped responding. The switch in SmartThings and Alexa would come on but Alexa would not speak. In your new multiAlexa driver all three are working as expected.
1 Like
DRIVER UPDATE NOTICE!
Your vEdge driver is being updated automatically. This update contains the following:
-
New Settings option in virtual presence device to choose the state value displayed on the dashboard: either presence value or ‘location’ field value (@Jake_Mohl)
- A new presence device will need to be created to get the new Settings option
-
New virtual device type: Energy. This device includes a switch, power meter, and energy meter. The power and energy consumption values can be set through automations, Rules, or third-party apps; and you can choose which state value you want to see on the dashboard in device Settings. (@georgeh)
- Existing vEdge driver users will need to re-create the vEdge Creator device to see the new Energy virtual device type listed (see below)
- Note that if you are looking for a device that is more of a complete energy tracking simulator, please see my separate Virtual Energy Meter here.
Latest vEdge Driver Version: 2023-07-18T17:24:25.974472533 (“Virtual Devices V2”)
Latest vEdge Creator device label: “vEdge Creator V2.94”
To get the latest Creator device that can create all supported device types including the new Energy device, you will need to delete, then recreate your vEdge Creator device. Do this by using the SmartThings app to first delete the existing Creator device, then perform an Add device/Scan for nearby devices. Your updated Creator device will be created and found in the room your hub is located in. Note that you can do all this safely without impacting your existing virtual devices created by this driver.
3 Likes
I deleted and re-added it, but still have version 2.91…
You may need to wait a bit longer for the driver to reach your hub. Officially, it can take up to 12 hours according to SmartThings, but is usually quicker. Just keep checking the driver version and when you’re sure it’s been updated, try it again.