I debated entering this one, and when the Bama/OSU game turned into a blowout, I figured why not.
To be clear, this will have a minimal impact on an individual device tile being loaded. When we’re talking about the above example, and 40+ lights are cloud-executing when they could be local, the actual actuation/control of these devices via the App will be quicker and more accurate. Since in this use case (and most) we’re talking about time elapsed between App Launch -> the device I want to control has verified to me via the App that it has been controlled, this matters. This will also of course benefit actuations that occur while viewing the App, through like someone adjusting the light or switch locally, providing faster/more accurate current state while viewing/controlling. Add this up on many devices and on the cascading impact across your entire Location setup, there will be a performance bump.
There is also the concern of DTHs that have not been touched in awhile in terms of being outdated/borderline obsolete, which I feel like is a good description of any old IKEA DTHs (and many I observe on accounts on a daily basis) that were previously needed. If they haven’t been optimized for the new App (a lot of developers are actively doing this or have done this and I’m not talking about those) they’re going to be clunky and slow. They may not have correct data to show in the plug-in (which results in fallback data being fetched to populate the plug-in, etc) which impacts latency in the case of going from App Launch -> Click Device tile -> Device plug-in.
I won’t claim to have all the answers for improving speed, and obviously there is still work being done, but I have never not used the new SmartThings App. I used Classic a few times just to see what the fuss was about. I have 91 devices on my Location (including the Hub).
People who have been around for awhile are generally those who have serious speed issues. The suggestions I mention above, when taken and performed as a whole, should have noticeable benefits. Individually probably less so (unless we’re talking a complete re-org of your Home page).
I’ve seen many people on here and on Facebook mention that Factory Resetting their Hub and starting from scratch with a new Location has helped resolve many of their issues. What’s done when you follow that procedure (provided you also delete your Location separately or as part of Hub Reset) is that:
- Old/unused DTHs are removed and everything you re-enroll is typed appropriately according to what is currently offered and being actively maintained. Many things that used to require custom DTHs can run locally now.
- Old/unused SmartApps are deleted.
- You are then using the newest C2C integrations instead of legacy/custom SmartApps.
- Maybe some mesh networking benefits that I’m not really sure how to properly articulate. This shouldn’t have App Loading impact, but instead have actuation/status/control/Automation execution benefits.
(Disclaimer: Not saying you should Reset your Hub and start over, just that those who have mention this has helped them. The same items I mentioned above are what is actually happening to achieve these benefits).