Yes Jimmy, It is definitely somewhere between 70 to 94 devices. I believe that the quantity of drivers is a factor as well. I was advised by Chris at Aeotec that the Todd Austin’s vEdge app consumes a lot of memory, but I am very reluctant to remove it because I use a lot of virtual switches.
2 Likes
OK, so now that we know they get added whether you want them or not, and even if you don’t have any of the associated devices, and they can’t really be deleted, what is the reason?
Have you contacted Tod @TAustin about that ? Would be good to hear Tods feedback on that statement
1 Like
I have 5 hubs on 4 (remote!) locations with avg 35 devices. (35, yes I am boring)
Zwave/Zigbee 50/50
My main question is: When things are crashing/hanging/memory error etc will my “old” hub stay OK?
And can I continue as before?
And: (I have a spare v3) Is there any reason to transfer from v2?
My Smartthings environment is not just a hobby. I really need to know the situation everywhere.
ST has helped me already 3 times for inundation and broken deepfreezer. So no jokes allowed.
Maybe of interest to those in the UK?
New UK V2 hubs for £49.99.
Ordered one and just received it, looks to be ‘new old stock’ complete with security seal. Not actually needed at the moment but good to have a spare. My current hub is of 2015 vintage and all these out of memory issues with the v3 hubs got me worried… 10 channels, 39 drivers, 174 devices…
https://www.easygates.co.uk/product/smartthings-hub-v2-for-uk/
1 Like
£89.99 now 
That rise is since I posted - wonder if they monitor the forum 
I have not contacted Todd on this alleged issue, but I will. I doubt that there is anything that can be done to reduce the size of the app due to the variety of available drivers, but I am no authority on this matter.
I had both vEdge Creator apps installed because some devices were using the older app. I changed the drivers for all virtual devices to the newer version of the vEdge Creator and I then eliminated the old channel. I was hoping that the elimination of one of the two vEdge Creator channels would free up sufficient space for a successful hub transfer of data.
2 Likes
2 Likes
Thanks for the link to that info. Unfortunately if you scroll thru that discussion it leaves more unanswered questions. Like do these unneeded/unwanted drivers take up limited memory and limited driver count. Those are the exact questions I had/have and doesn’t seem like we have answers.
2 Likes
The following comment suggests that the drivers are consuming storage rather than memory.
3 Likes
i still find it hard to understand why the F Samsung have not produced a decent hub, they are throwing money at Smarthings so why not a freakin hub that supports the same standards with todays uber complex (supposed to be easier) thread stuff, it just baffles me !
5 Likes
Thanks for the sharing your take. I’ve decided to return the Aeotec hub for now, as I’d rather risk paying more to buy it again in the event that the hub-replace feature is eventually implemented for the Smartthings Wifi hub. But, if that doesn’t happen before my Smartthings Wifi hub fails, and I find myself having to start over from scratch, I’ll want to use that opportunity to consider other platforms.
2 Likes
Here is Todd’s reply to the claim that the Virtual Edge Creator consumes a lot of memory: https://community.smartthings.com/t/re-new-hub-replace-feature-for-smartthings-hubs/273150/2
Thanks for the heads up. Link edited… 
Still didn’t work. Looks like that post may have been deleted.
4 Likes
Todd said…
“I can believe it: the vEdge driver, because it supports so many device types, is rather large. SmartThings doesn’t give us developers any visibility into memory usage or performance tools, so I am flying blind in that respect.
If it is causing significant issues, one option could be to somehow group the devices types into separate drivers. If there is anyone you are communicate with that could provide suggestions, I’m certainly open to ideas.
Besides not having any visibility into memory or performance, SmartThings gives me no tools for even knowing how many people are using the driver, or what devices they are creating with it.”
5 Likes
Which then leads to the question… how does Chris at Aeotec know ?? can he share more information so that developers have a fighting chance
4 Likes
The Nov 8th email that I received from Chris Cheng, Field Application Engineer for Aeotec stated that the SmartThings Team took a deep dive and made a number of suggestions which included the recommendation to “…remove the community virtual edge driver device (as it uses the most memory in terms of resources) which should be enough for the hub to successfully use the replace hub feature.”
So it was the SmartThings Team, not Chris who made this suggestion.
2 Likes