Works great with no proxy, thanks!
One comment: it looks like some “friendly names” in the UI went away.
Ooos You posted this weather driver topic to my vEdge topic! 
Nevertheless glad to hear you’re working with the new no-proxy option. 
There is a problem with the SmartThings app right now where custom capability labels are not being displayed properly in the device Controls screens. It impacts all community drivers. Hopefully this will be fixed soon…
Sorry, had multiple browser tabs open.
Todd,
I use your vEdge Creator V2.3 and was wondering if when using the virtual dimmer that instead of the tile text showing on or off (which information is duplicated by the switch color), could it display the dimmer setting level?
Yes, I think I can do that. I’ll probably make it a device Settings option.
Thanks, that will be appreciated!
@TAustin - can I request a new virtual device type? I would like a device that shows up here in routines:
It looks like there is a “speechSynthesis” capability, which would take a phrase in a “speak” command. I would then need the phrase passed in to be recevied as an event.
Is this doable?
Thanks.
A virtual speaker won’t actually play anything… were you looking for something you could pass over to a device on a different platform?
Otherwise, each real world physical speaker would need an edge Driver/Cloud integration with Messages formatted in its preferred manner, and that would be outside the scope of this particular thread.
In other words, you couldn’t use a virtual speaker to get sound out of a Sonos device or a Samsung sound bar or an Echo speaker. So is a virtual device actually what you’re looking for? 
Right, a virtual device. Ideally, I would get the text passed to it in an event that I can subscribe to in my webhook SmartApp hosted by Node-RED, which is where my Alexa integration is. Then I would send it to Alexa for speaking.
1 Like
Hi @TAustin
I have started the move to Edge and have been playing around with the Sharptools Rules engine. I added a few Edge drivers to my hub I had come across on the forum and which I expect I’ll need. Next, I moved only one Z-wave switch (a Fibaro single relay) to an Edge driver by excluding the switch and re-onboarding it.
Somewhere along this process, devices stopped responding. Even (old) virtual switches are taking forever to respond or don’t respond at all half of the time. This has been ongoing for 3 days now, so I started to reverse what I had recently done to see if I could get things going again. (I’ve tried all the usual stuff like z-wave repair; hub reboots; turning hub off for 30 minutes etc. without any improvement.)
I excluded the single Z-wave device I had added with an Edge driver; disabled all Sharptools Rules and started uninstalling edge drivers from my hub.
When I got to removing your Virtual Energy Meter, I received an error "Error: Request failed with status code 504: “\r\n504 Gateway Time-out\r\n\r\n
504 Gateway Time-out
\r\nopenresty\r\n\r\n\r\n”
(Sorry, the message is messing around with the formatting on the forum.)
Does that mean the driver is in use? If so, is there a way to tell which device is using this driver? I’m concerned that the Fibaro Z-wave switch (which I removed from the hub as part of my troubleshooting), is still living as a ghost device on the z-wave network and that might be the reason for my unresponsive hub/devices?
(The only edge driver remaining on the hub apart from the Virtual Energy Meter, is your Envisalink 2.1 driver, but removing that would be my last troubleshooting step.)
Thank you.
Hi there - sounds like you are having a nightmare scenario!
I’m not sure I can be of much help with most of it; you probably need help from nayleyz or the broader community which would probably be best done from a separate topic.
Are you using the CLI to remove your drivers? If so, that Gateway Time-out error does happen occasionally but usually it clears if you wait a bit and retry. It has nothing to do with the driver being in use; it’s an indication that the communication with the SmartThings servers failed.
I do have a Linux bash script for for the CLI that will list the devices that exist for a particular driver:
#!/bin/bash
myid="\"$1\""
echo 'Devices for driver id <'$1'>'
smartthings devices --json | jq -r '.[] | select(.lan.driverId | . and contains('"$myid"')) | .deviceId'
…but I suspect this won’t be of use to you as is. You could do this command:
smartthings devices --json
And then manually comb through the results to find the devices using a given driverID.
EDIT: You probably want to redirect the output of that command to a file and then bring the file into an editor where you can do searches:
smartthings devices --json > mydevices.lst
notepad mydevices.lst
1 Like
I tried both via the website and the CLI. Thanks for taking time to respond. (I have still not been able to determine what went wrong with my setup.)
Not sure if anyone has chimed in yet on this but I am using the Wi-Fi hub and your driver installed and worked perfectly. I was able to create a virtual switch and contact sensor. This is a fantastic resource. Thanks!
3 Likes
Agreed. Since I’m planning on the end of the Life360 integration, I realized I could create presence switches that look just like my Life360 presence sensors and I can turn them on or off using routines or SharpTools rules. Neat.
3 Likes
Can anyone confirm if routines using virtual devices created in this way will run locally? I can’t seem to find a way to do that.
I can confirm that I have routines running locally with virtual devices based on this driver.
1 Like
Thanks. I just realized it seems to run local unless the routine requires something to stay on or off for a period of time prior to being triggered. I guess that is still a cloud dependency?
1 Like
There are few conditions that won’t run locallu, yet. There’s a list somewhere what those conditions are. 95% of my routines run locally. Only a few I’m forced to run through cloud.
1 Like
please can we have a virtual siren and if its not too much to ask (please can it send get comands,)
thanks
martin
I am missing something obvious? Installed the vEdge creator OK. But when I click on the vEdge device, all it shows on the “Controls” page is Status Connected. I don’t see any buttons, etc to start process of creating virtual devices.
New Aeotec Hub, ver 2.3.5-9, Firmware 000.044.00009