Right now I am running a 3rd generation “Samsung” Smartthings hub in a smallish townhome with merely 20 something zigbee and z-wave devices with some virtual devices and my hub is failing constantly. Routines are not running until minutes later when conditions are met or not at all (seems to be a resource saving feature). Its really great sitting in the dark until something decides to function. Devices like my z-wave smoke detectors bounce on and off line on a daily basis even though they are in the same room as the hub. Seems really effective to me. I made a post about it and the Smartthings developers were unsurprisingly of little help (Smartthings has been killed by the update). Now my smart home is starting to become useless if it doesn’t work. My question is, while my hub is the same as the Aeotec, would upgrading to the Aeotec be of any use? Are there any custom options that are more robust? Or should I finally make the switch to Home Assistant and not look back? Any advice is appreciated!
The Aeotec “ works as a SmartThings hub“ is a clone of the SmartThings-branded V3. Not an upgrade. So you won’t get any improvements by switching to that.
Your smoke detectors will not function as zwave repeaters, so in terms of a robust network, the first thing to look at is the “backbone“ you have set up for each protocol. How many mains powered Z wave devices do you have and what is the brand and model of those? And the same question for Zigbee.
Also, in the thread that you linked to, I see you did get a response from a SmartThings staff member, who said
>”However, while I was checking your Hub’s info, I saw it went offline a few times and noticed it has the memory properties at “hard limit”.
This means the Hub is running out of resources, and we’ve seen the Hub stopping certain services to free up some memory or sometimes, rebooting itself.
For now, my suggestion would be for you to check which drivers you’re using and if you can reduce their number, for example, instead of having a separate driver for each light device, see if a single one can control all of them.
Also, if the driver has many custom functionalities, its size will be bigger and thus consume more memory.”
did you follow that suggestion? Have you looked on the advanced webpage to see if there is a memory warning there?
I made sure I have one mains powered smart plug (as repeaters) in each room. I am well familiar with how the networks work so I designed what I thought would be a robust network. For the smoke detectors, one is in the same room as the hub and the other is in the room right beside. hardly a situation where it seems a repeater is necessary, especially if the one that is in the same small room is bouncing offline constantly.
I did see the page and made an attempt by deleting a few drivers and it showed little impact. A lot of the drivers I use are from @Mariano_Colmenarejo and his are much more useful than the generic smartthings drivers. My main issue is I use very few devices in my eyes and I can’t really get more given this limit. A lot of my devices require custom drivers to function the way I need them to. I really wish I could permanently delete the crap pre-installed to my device like random drivers for bose and Harman that I will never use.
So does the advanced page still show a memory warning, either hard or soft?
If it does, it really doesn’t matter what else you do until you get that resolved. 
(my understanding is that the preinstalled drivers for things like Bose will not affect your memory limit. But I don’t know if that’s still true.)
Right now it says:
-
driverMemoryLimitStatus: SoftLimit
-
driverCountLimitStatus: HardLimit
My thinking is that if the few drivers I have really create such a big problem it becomes unusable and there are no better hub options, maybe I just need to get away from Smartthings.
Hi, @Docga
Is the delay only happening with routines or also when sending direct commands to the device? Also, are using the “delay” function and it’s lower than 1 minute? I’ve seen reports of that not triggering on time
About the hub, is it still going offline often? The Softlimit on its memory shouldn’t cause a full restart to make it offline
Some devices go offline due to them being sleepy. I can continue an investigation about this to get more info on why the devices are going offline because it can also be to a poor path from the device to the hub (we’ve seen several cases like this), but for this, we need your help to collect more information.
Its both routines and devices take forever to do anything. Sometimes I will turn something on/off and it will load continuously in the app and then revert to the original state. So I have to click it 3, 4, or 5 times to get it to cooperate. The hub is no longer bouncing offline as much. Just occasionally. I believe the hub is still open for developers to read the logs or whatever you had me setup last time. Never got any definitive information last time. Please tell me Smartthings and/or Aeotec has a better device in the pipeline!
Hi, @Docga
The ones you mentioned that don’t respond are LAN, Zigbee, and Z-Wave equally? I see that the majority of your devices are LAN and belong to drivers that create Virtual devices.
According to what I pulled out, you’re only using 14 drivers but have 53 installed, which explains the “driverCountLimitStatus: Hardlimit”, so, you still have the opportunity to clean some of them. They shouldn’t take too much space if they aren’t active, but since you’re running into these issues, it is suggested.
Also, now that we can focus on other things rather than the Hub’s restart, we need to analyze the delay case. So, please choose a device that you’ve seen affected by it, then follow these instructions:
- Start listening for driver logs. For this you need to set up the SmartThings CLI in your PC. These are the instructions: Get Started With the SmartThings CLI | Developer Documentation | SmartThings
- Then, try to control the device where we can see a delay. There, we’ll see if the command reaches the hub and if it’s sent right after or if it takes some time.
- Copy those logs into a file and send them to us at build@smartthings.com
- After this test, submit the hub logs:
1. In the Advanced Users app, enter the “Hubs” section
2. Enter the corresponding Hub and click on “Dump Hub logs”
3. Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
4. You’ll get a green box at the top confirming the Hub logs were requested.
Note: If this same device goes offline constantly, submit the hub logs when you see it go offline and take note of the date and time and share it with us including yout timezone. For example: 14:20 GMT-6