FAQ: Limits and Guardrails (max # of automations, devices, etc)

While you are at it, can you include this one?

7 months later and still no responses.
apparently this is some treasured secret?

The problem isn’t with there being arbitrary limits on things so much as that they are undocumented, difficult or impossible to debug, and apparently even support often doesn’t know about them (or knows just enough to be dangerous).


@jody.albritton, the problem here is that Samsung would never put into the front window these numbers. Otherwise the people who would buy the equipment would look at it, do some calculations and turn around to look for another option.

All we know that the way forward is the new app as the v3 hub came with that. But look at this issue with @kieranlavin 's setup as a newbie. Those were not even overcomplicated automations. A simple user starting to build some fancy home automation would hit it really quickly. And it is only because the features of the new app push these limits. Then support will give some answer what the user cannot deal with, as how is it possible that with some simple automations a limit has been hit.
The next thing what you would realize that the Play Store would be full of 1 star reviews due to this, then Amazon would be full of it, and BestBuy, etc.

People are starting to read the community forum when they have a passion for the subject. Simple users what things to work. If you buy a home automation hub, then you want to build some automations with the provided platform. If the platform has been built with these shortsighted limits, then you will loose potential clients really quickly.

I understand the main reason of cost efficiency, but then introduce a premium option. But I can guess it is in the pipeline already. The past few weeks’ communication probaly made a few people to rethink their options with SmartThings.
How would you expect that those clients which has been turned down would advise other people to purchase a SmartThings hub? At the enď everybody leaves with a bad taste in the mouth and nobody wins anything.
Honestly I can see shortsighted and most of the time incompetent management behind these decisions who do not really care about the customer satisfaction but their 15 minutes of fame and their bonus if they reach a goal. If an engineer has to fight for these limits to be raised, then something has went wrong seriously.


I am not an engineer, but the recent topics regarding the network errors and creating/modifying scenes or automations in the new app are quite obviously shows that there might be a bug with the new Smartthings app or people hitting the limits continuously.

@jody.albritton? @Brad_ST?

All three of those are different root causes and none are related to hitting a rate limit.

“A network or server error occurred. Try again later.” is a very generic error. They are taken seriously though and reporting these and similar issues via support.smartthings.com or from within the app is still the best way to bring attention to concerns.


Hi @Brad_ST, I’ve attempted to start moving as many Routines and SHM custom rules from Classic to the new app as possible , but unfortunately I’ve run into the same issue creating custom automation in the new app, specifically the message “A network or server error occurred. Try again later.”. I’ve already submitted a support ticket for SHM being broken in the new app, so I just added this to the ticket.

I’m really trying to use the new app, but every step forward seems to take 2 steps backwards…

1 Like

Jody, any updates on raising the limit? My fingers are itchy to convert the Classic routines into scenes and automations but I am afraid that I’ll eat my “behaviors” for breakfast in the Good Morning routine. :slight_smile:


© 2019 SmartThings, Inc. All Rights Reserved. Terms of Use | Privacy Policy

SmartThings; SmartApps®; Physical Graph; Hello, Home; and Hello, Smart Home are all trademarks of the SmartThings, Inc.