The device limit does not seem to apply to adding virtual devices. I 'am running at around 200 devices and can add plenty of virtual devices (just added 6) , but if I have any issues with physical devices I have had to delete virtual one’s to be below 200 in order to add/scan.
I saw a post here somewhere that said the described limit is 200 devices, but it’s not being enforced…so, no limit…at least for now?
My recent experience has been that if you have 200 devices you can add virtual devices but not physical devices, and if you have over 200 devices and you remove one physical device or one physical device needs to be re-onboarded it will fail to add over 200. I’m in the U.S and some others do not seem to have this limitation.
It’s more complicated than that. The 200 device limit is intended as a UI limit for the app, they didn’t want to list more than 200 devices. So it didn’t matter what the protocol was, and virtual devices also counted towards the limit. But it depends how the device is created.
Something created through the API, which is how Vedge Creator does it, won’t get caught by the limit. But it will count towards the limit the next time the app is opened and you try to add another device by scanning there.
Something added through scanning in the app will run into the limit.
But at various times, historically the limit was imposed in iOS, but not android, or vice versa, and it can all get pretty confusing.
Also, historically it was sometimes applied in one region, but not in another.
In any case, there are definitely people still hitting it today when they go to add a device by scanning through the app, you can find multiple discussion threads in the forum about it.
2 Likes
I have less than 60 devices, so not about the limit.
It is happening with different types of devices (vSwitch, vLock, vAlexa Switch…), I also noticed that when I set quantity to create to 2, the issue is less frequent to appear, but it just creates 1 virtual device instead of 2.
I am deleting the creator and re-adding it everytime this happens.
I have the exact same issue. I am able to set the quantity of virtual switches I want to create, but the “select and create” as well as the “virtual device inventory” are grayed out. This has worked brilliantly in the past, just not at the moment. Any help would be appreciated. As many have said @TAustin this driver has been a life saver, so thank for all of your hard work on it!!!
1 Like
I can’t get virtual switch to add in google home routines. It doesn’t show in google app. What i can do?
1 Like
You’ve recently deleted and then recreated the creator device and this is still happening?
I’m sorry you keep having this problem. Would it be possible for you to install the SmartThings CLI so we can see from the logs if anything unexpected is happening in the driver? You can down the Windows install file here.
You get driver logging using the CLI command “smartthings edge:drivers:logcat” and selecting the driver for the vEdge creator.
1 Like
Just to be clear, vEdge driver creates devices through the Edge platform developer API’s, which is something different from the SmartThings RESTful API. And I’m pretty sure these vEdge devices DO count towards the total device count.
On the other hand, if you create the SmartThings native virtual devices either with the app, the CLI, or the RESTful API, then those virtual devices may not count towards the device totals: a good reason for going that route if all you need are simple virtual switches and such.
3 Likes
Thanks for the correction. Same idea, though: I’m pretty sure that the restriction is implemented in the mobile app UI itself, since we do know that historically there were times when it applied in one version of the mobile app, but not another.
So since devices created through the Vedge Creator aren’t seen as devices being added to the account by the mobile app UI until after they are created, they don’t get caught by the limitation. But they will still count towards the total the next time you try to add a new device through the mobile app.
1 Like
Aren’t you playing with fire here imagine some coding changes and IP address isn’t fixed someone mistakes and Mac address all of sudden middle of night shit I’ve been cut in half biomattress and his final last words would be Bixby help haha
@TAustin I am having the exact same new issue as some other users posted above. I could not create a new virtual device or see my device creation history (all greyed out in the plugin) I tried deleting the virtual device creator plugin v2.9 and now I can’t add it again - uninstall option remains greyed out and it just says “driver already in use”. When I attempt to install any other plugin, none install as well. Any ideas how I can fix this TAustin??
I’ve had the same issue. I was eventually able to create new devices by waiting a minute or two in between my attempts to create them. After about the third or fourth try it succeeded in creating devices.
1 Like
@ndavis82 thanks. I ended up deleting the creator app and then rediscovering it in SmartThings. Seems to have solved my issues as I can now create additional devices.
1 Like
@TAustin I’m having the same issues as others have listed but removing the vEdge Creator and rediscovering it did not help (now at V2.94). In fact it made things worse. Now the one vSwitch I did create previously won’t show me what devices it controls or let me change them. It does still work though.
Are you able to create new devices and view inventory?
I’m not following you here. Are you saying you can’t display its automation routines in the app?
No, I mean when I look at the vSwitch I can no longer tell what devices it controls. It still works to control the devices I originally linked to it thought.
I can occasionally get it to create vEdge switches but I cannot add inventory to them. They are just empty. When I go to them there isn’t even a spot to add devices to control.
I’m really sorry, I just don’t follow what you’re saying.
Can you provide some screenshots to show what you mean? Other than examining the routines you have created that use the vswitch, I don’t know what you are expecting to see.
Are you saying that when you open the virtual switch device to its Controls screen you aren’t seeing anything?? You don’t “add inventory” to a virtual switch you have created. You create automation routines to link them to other actions and or conditions through automations.