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

Devices & Integrations Community Created Drivers
, ,
325

A driver update has just been pushed out.

What’s New:

  • Air quality device type (@troy_owens)
  • Inventory: (@fido) find out how many virtual devices the driver is managing by type. Th quantity will include all devices created + any devices you’ve moved over from the V1 driver.

Notes

You will only see these enhancements on the V2 driver, not the V1 driver. This will be the case for all enhancements going forward.

If you are not seeing the updates on the creator device details screen after you are certain your driver has been updated (can take up to 12 hours), you may have to delete the creator device and re-create it through an Add device/scan nearby. This seems especially to be needed by iOS users. Android users can try their cache-clearing trick. In any case, deleting and re-creating the creator device will have no impact on your existing virtual devices.

Virtual device types now supported are as follows:

switch, switch level (dimmer), momentary, contact, motion, presence, shade, thermostat, lock, smoke, water, air, alarm

New requests for additional virtual devices types are always welcome!

326

I was able to create an Air Quality virtual device.

When I try to use Virtual Device Inventory it spins and spins, I get a “network or server error”, and no answer.

327

Sometimes that happens when you try to move too fast in the mobile app. Make sure you give the app time to be totally refreshed. Then try it again. Either that, or you got the presentation update prior to the driver code update being loaded to your hub. If that’s the case, wait a few hours and try again.

328

Getting the Network or server error when trying to create virtual air quality, other create fine

329

Sounds like the driver code hasn’t been updated yet on your hub. Give it a few hours to get updated and try again later. I won’t panic … yet :confused:

330

My first reply saying you may not have the driver code updated yet on your hub makes no sense. If you were able to create the Air Quality device, then you have it. So now I AM worried. Are you still having the problem with the inventory button?

331

I can still create Air Quality, but I can NOT run inventory.

332

@Paul_Oliver
Do you have the CLI? If so, we can check the log output.

333

I do, but I am on my way to camp for the weekend, and will not have access to it.

334

Thanks for the update!
I did not understand now that I installed the v2, if I can delete the v1 or if doing so I would lose the virtual devices created with the v1 driver.
Thank you

335

If you’ve moved all your devices over to the V2 driver, then you can uninstall V1 with no problems. See my post here for how to move devices from the V1 driver to the V2 driver.

336

I back home, and checked the Virtual Device Inventory in your v2 vEdgeCreator and it is working.

337

ST Wifi Hubs are receiving updates to 38.11 that should enable Edge drivers. Mine has been updated and I’ve deleted and reinstalled the vEdge v2 driver. I’ve done a Scan Nearby, but no new devices are being found.

Same issue here - did you find a solution?

I am on a ST Wifi Hub that has been updated to 38.11. When I go to the “Manage SmartThings Hub” section, Virtual Devices V2 is shown as installed under the “Driver” menu option. I’ve tried reinstalling a couple times, but when I do the Search Nearby then no new devices are added.

338

@charlie969
If you can install the CLI installed, and get the logger working, then I can help diagnose what’s happening, but if you can’t get that far, than something else is wrong besides the driver itself.

339

Sorry, I’m not comfortable with command line stuff. Hopefully somebody else will be able to help figure it out!

340

I could walk you through what to do with step by step instructions, but I perfectly understand if you don’t want to go down that path!

341

I’d be happy have that kind of help. I couldn’t make CLI working in Linux Mint.

342

Do you have a windows computer? It may be easier.

343

Nope, I only use linux. Are there usually problems with linux version?

344

I use Debian linux on a Raspberry Pi and have no problems. I cannot use the binaries from the CLI github because they don’t support my processor. So I install it with npm from within a terminal window:

npm i -g @smartthings/cli

The other issue is that you must have a browser available. The first time you run a CLI command, it will try to open a browser window and you have to sign in with your SmartThings login and grant permissions by pressing a button. Once you do that, it will say you can close the browser window. Then you return back to your terminal window and the CLI should then complete the requested command.

I have seen people with linux - that don’t have a browser installed - not be able to run CLI. I think there are other ways to set up authorization config files with your token, but now we’re getting into major hassle territory…

Let’s take this conversation off to a separate thread, so DM me directly if you want to pursue this further.