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

Here is an Edge driver that will enable end-users to create virtual devices that run locally on-hub.

Features:

  • Supports switch, switchLevel, presence, momentary, contact, motion, lock, smoke, alarm, window shade, and thermostat virtual device types
  • Includes a switch in each virtual device to control device state (also useful for Alexa triggers)
  • Create any number of virtual devices
  • Easy and fast to use: No coding or CLI required
  • Enables you to create 100% local automations with virtual devices

I’m happy to expand the list of virtual device types supported if the community finds this useful.

Please leave your feedback here!


Instructions:

  1. Use this channel invitation link to load the driver to your hub: SmartThings. Add a little smartness to your things.

  2. Go to your mobile app and do an Add device / Scan nearby
    This will fire up the driver and a device will be added called vEdge Creator

  3. Go into the device details screen for vEdge Creator and select Settings via the 3- vertical-dot menu icon in the upper right corner of the display.

  4. Enter the total number of virtual devices desired for each type.
    Note that the number you input here is the total number of devices for that type that you want. So if it is currently a 0 and you want 2 devices, enter 2; if it’s currently 2 (you had created 2 previously) and you want 2 more, enter 4, etc.
    Note that this value currently has a max of 50 for each type, but this can be increased if needed!

If you have any problems, it would be helpful to get a log output, but for that you will need the CLI:

smartthings edge:drivers:installed
smartthings edge:drivers:logcat <driverID> --hub-address=<hub ip addr>
24 Likes

Does it automatically run every time you put the hub in pairing mode? Any way to kill it so you can pair other devices?

Not sure what you mean. The initial scan nearby is just to initialize the driver and create a ‘creator-device’. From then on any new scans initiated are ignored. The virtual devices themselves are created via the settings options within the creator-device. You may need to try it out to see what I mean.

1 Like

ah, interesting. will play later when I can get a log opened.

This works great!
Amazing work @TAustin
Any chance of a dimmer?

2 Likes

This is great. Lot of my automations run in the cloud due to virtual switches. This will allow them to now run locally.

Ah right. I’d got so fixated with the driver discovery process that I didn’t think about being able to generate more devices from a device life cycle.

Ironically I use the update() method in a DTH to do a broadly similar thing, albeit with child devices.

Serves me right for not following the Hello World example and trying to throw in custom capabilities which didn’t work.

3 Likes

A virtual presence sensor (on = present, off = not present) might well be a real game changer for me.

Much as I like messing around with code, the Edge drivers really don’t have any appeal to me so the less I need to do with them the better.

4 Likes

+1 on virtual presence sensor

6 Likes

@TAustin Virtual Motion works well with IFTTT connected to Wyze.
Fyi after creating virtual device, renaming and moving to different room, and if you go to vEdge Creator, and type 0 for same type of device, it does not delete virtual device(s). This is good

1 Like

My first installation of a community created edge driver, most excellent thank you @TAustin

I do have a suggestion, on the drivers main page, under the instructions, would it be possible to have a count of the devices already created, or a list of the devices names once they are created and renamed similar to the old DTH of v switches which used to list the created devices

Even if not possible it is an excellent driver, thank you

1 Like

@TAustin,
I have tested the 4 virtual devices with automations and scenes and they work very well.
In the logcat I have not seen any errors during the installation and operation with the automations.

If it was possible to add the virtual dimmer, I would use it to encode a sequence of multiple button presses to arm away, at home and disarm STHM.

Great job !!!, Thanks

2 Likes

Echo also instantly found the created v switch and motion sensor I created as a test, I mean, really instantly :+1:

2 Likes

So can you use these to trigger a echo routine? How do you actuate the virtual Sensor?

RIght; that works as intended. If you want to delete devices, you can delete them manually.

If you do change a setting to 0. You’ll have to use an incremental number to get more devices created. It simply subtracts the last number from the new number to determine how many devices to create.

Yes, you should be able to trigger an echo routine with a virtual contact. You trigger a virtual sensor by turning the included switch on and off (on == ‘open’ or ‘active’, off == ‘closed’ or ‘inactive’).

1 Like

Thanks for the feedback!

I’ll look at a virtual dimmer type. I may have more question for you on that one, but will get back to you.

1 Like

Virtual dimmers have in the past been used a couple of different ways:

  1. to act as a master control for a group of dimmers

  2. to act as a Value holder for a variable that can have more than two values. For example, some people use them for fan settings, some people use them for sound levels, some people use them for humidity ranges.

Adding a count would be fairly easy; a list might be a bit more challenging to format nicely. Will consider…

Thanks for your comments!

1 Like

Presence sensor: will do!

5 Likes