Aeotec/V3 Hub memory full, work around

Tonight I reached hub memory full when trying to add a device.
I’m now on 128 devices, I deleted a few not in use and got it down from 135 devices.
Of those I’d say around 70 or 80 are actual hard devices connected to hub, the rest are cloud integrations or virtual devices.

I also deleted as many as I could unused drivers.
Now the hub is at soft limit rather than hard limit which it was when I started.

I’m at 33 installed drivers including pre installed.
I’m using a fair number of virtual switches using TA Austin’s multi virtual device driver, that could be part of the issue as I know it uses lots of memory.

I tried creating a couple of virtual switches in the SmartThings web but whether they are created as local or cloud they can’t be used within Alexa routines to trigger an Alexa action.

Other than trashing stuff in use I can’t see a way to make a big change here, I would rather keep the virtual switches that work with Alexa, unless there’s another way.

Any suggestions, other than thinning the herd wrt routines or devices?


1 Like

My v3 hub has been “full” for over 2 years. I’m at 275 devices and counting. Usually, I don’t have any issues using the TAustin Virtual device creator even when my hub is full. I have another work-around for adding actual devices with the app. TAustin also has a compatible Alexa virtual device, but I’ve only read about it as I don’t use Alexa. I would try this route instead of through ST’s creator.

1 Like

What hub do you have? I am guessing a v3 or Aeotec.

My Home location has a v2 hub with 43 drivers, and the location has 210 devices. I also have a new SmartThings Station hub with only 8 devices on it that is 2 weeks old. I have been at the Soft Limit on my v2 hub since the AWA came out and have not had a problem adding devices.

It sounds like you need a 2nd hub.

1 Like

It’s an aeotec v3, and I’m using thread too.
I’m not using zwave, is there any way to disable that to reduce memory footprint ?

What’s the workaround? Is it a deprecated version of SmartThings on an old android device?
I don’t have that option and I’d rather not go there.

I only have 4 active Thread devices. Three use a Echo gen4 as a TBR, and 1 uses the Station as it’s TBR.

The virtual switches that you create through the app cannot be used to trigger an Alexa routine, but a virtual lock that you create through the advanced features page of the official web UI to your account can. So I don’t know if that’s of any help or not.

2 Likes

Well, then the only option I can think of then is to add another hub. I run two hubs, one for my regular devices and one dedicated to my security devices. I had an old v2 hub that I had retired, when I started running into memory issues I added it back in. ST’s works just fine with multiple hubs, the v2 actually has a faster CPU and twice the memory of the v3. The only “catch” with running two hubs is that if you create a routine that uses devices from both hubs, it won’t run locally. This may be fixed now, but when I set mine up that was the only real downside. As far as the GUI, everything works the same. When you onboard new devices, the app will prompt for which hub you want to use, if your v3 is full, it will be greyed out.

2 Likes

Thanks for that. One problem I see is that even if I had a second v2 hub it doesn’t support thread. I’ve just ordered another. 6 thread + matter bulbs. I’d sooner get a SmartThings station if it had more memory and was available in uk, which it isn’t. I’ve never found out if it has a faster CPU and or more memory compared to a v3 . Dunno why it was never launched in uk.

I was going to suggest the Station if you’re in the US. I just bought 2 of them on clearance for $40US each with the power supply. Heck, I could just use it just as a charging station for that price. Anyway, I guess the only other alternative is another v3 if you need Matter/Thread. I used my “alternate” method to add a couple of Matter/Thread receptacles to my v3 since my v2 doesn’t support Thread. I picked up a v3 for another location I’m working on from eBay, NIB for about $100US.

1 Like

I found a work around for the dreaded ‘hub memory is full’ when adding a device.

Pull the power on your hub, mine is on a Tapo P110M plug so I cycle my hub from the Tapo App. Reconnect power.

Then in ST App Dashboard/Home Insights keep watching until all your devices go offline. Wait for most of them to come back online, some take longer ignore those.

At that point put your device into pairing mode and go to add device, scan nearby, wait for your device to be added and configure it.

If it’s a matter device go to add, partner devices, matter.

I currently have 184 devices (some virtual).

This method worked for me today with the hub full message and adding a third reality soil moisture sensor.

2 Likes