SmartThings Hub Version 2.0

CTO Hagins’ definition of “stability” works for me:

We are working round the clock to get the experience to the point where it needs to be. From a customer experience perspective, my simple goal is that SmartThings should be the last thing you suspect as being the cause of a problem, not the first. We need to be more reliable than the devices that are connected to our platform, and we want our customers to expect that day after day, month after month, year after year.


That’s an absolutely admirable goal and disagreeing with it would be like saying I disagree with the goal of world peace and balanced budgets…

That is a very literal standard, and anyone who expects Hub V2 to meet that this year will likely be disappointed. I expect wonderful improvements from Hub V2, but let’s be realistic: For the first few months, Hub V2 (and/or the rest of the SmartThings Platform) will be the first thing I suspect when there is an issue.

Shaking out bugs and scale issues in a complex system converted from a cloud to hybrid architecture requires considerable time in the wild.

Furthermore, that literal standard not only requires excellent stability, but it requires time to establish trust in this stability in order to redirect “suspicion”.

As I wrote previously, the mixed-blessing case is what I’m optimistic will be averted: ie, Priority to avoid appearance that the benefits of the new architecture could be outweighed by the glitches that are inherent in a new product. The simple solution: patience. Wait to see others’ experiences before jumping in.

1 Like

My expectation is that launch criteria for hub v2 would be that it as reliable and perform as well as the current hub for all currently functioning device types and community smartapps. Migration from old to new hub should be tested and reliable (better testing than some recent mobile app revisions). And advertised new features should work most of the time.

New features or capabilities shouldn’t be announced or marketed until they actually work most of the time (see the 2014 ST Harmony integration announcement and user experience and months of “we’re still fixing/testing” for an example of how NOT to launch new features or integrations). It seems it always comes back to good testing processes… That’s always been the weakness. So take the time needed to test properly.


Are you saying hub v2 should never be released?


Testing doesn’t take that long if you recruit lots of volunteers.:slight_smile:

Wouldn’t agree with that. You are probably better of with a few very knowledgable testers who understand the technologies behind the product. Less feedback, more relevant feedback, aka faster, more accurate testing.


Not sure I agree with your disagreement. Having an army of beta testers in the wild can expedite testing exponentially due to sheer volume. In addition you get the added benefit of being able to test the completely random hodgepodge of real user environments (devices, networks, etc) that are nearly impossible for ST to replicate in their labs. Of course you would have to have an ace system for collecting user data and categorize.

A good example of success would be the Windows Insider program for Windows 10.

1 Like

Wait, isn’t that what releasing a product is for :slight_smile:

Gmail was in beta for what, 5 years? Lots of moving pieces with hub v2. It isn’t as simple as new hardware, its essentially an evolution of the platform, software, hardware, apps, etc. All are interrelated and will take a ton of time and resources to launch properly. I hope they will test externally, but the tools to test on a massive scale need to be in place before a public or private beta can be executed.


I work for a Hardware and Electronics manufacturer. We periodically have to revise release dates but I would rather explain to a customer why we had to push a release then explain why the product isn’t functioning as promised. I know this widget doesn;t work correctly but hey we released it when we promised. I’ve never had anyone not understand.

1 Like

Windows is probably the worst example you could use to prove your point…

1 Like

Why is that? The insider program has been wildly successful. Some stats from just the first month of the program:

  • Over 1 million registrants.

  • Over 200,000 pieces of user-initiated feedback.

  • 68% of users launch on average more than 7 apps per day.

  • 25% of users launch on average more than 26 apps per day.

  • 5% are launching on average a massive 68 apps per day.


It was a generic statement. I am not against Windows or there business model (it works) and my primary development language for last 13 years has been C#.NET

The negative reputation Windows has / is known for is making the public their “army of beta testers”. When I was reading your post, before I got to your last line, I was thinking geez, that sounds like Windows strategy to the public.

I am not familiar with the insider program, but you really cannot claim success until the product has been stable-y rolled out for some time. Even then you need to show that there was an ROI on your budget and schedule.

86 percent of the users get time to drink their coffee as they reboot their system


So has there actually been a revised launch date yet?

No specific date beyond “most likely Q3.”

Meaning not the previously announced Q2, but could be later than Q3 as well.

One staffer said they personally were hoping for July, but that wasn’t an official launch date announcement.

Darn, I was hoping there had been some additional info. I would like to have something to play around with while my house is being built.

It’s unfortunate that development can’t provide a firm response as to when the v2 hub will be released. I just implemented the Smartthings starter kit containing open/close sensors, motion detector, smart phone proximity sensor, etc… And I’m really enjoying learning about all the cool things Smartthings can do. I liked it so much that I ordered more sensors, garage door opener, etc… total investment in my HA is close to a thousand dollars.

Granted I should have done my homework sooner, but long story short I’m now reading about a v2 hub that will localize the processing and could potentially improve response time of the apps. Currently with 4 sensors and 4 smartphone proximity sensors I’ve noticed that the response time has gotten longer in some cases. With more z wave toys, I fear this may get worse.

I would really like to be part of any beta testing for V2 hub otherwise I may have to consider a competitors hub/solution if Smartthings is not scalable to handle more devices.

It does get a little scary. I was pondering this in regards to kickstarter product, Plastc, that is “due the end of summer.” If found myself thinking that if I was in a situation at work, where I less than three months from the expected completion date of a project, and I couldn’t give a final delivery date with a 98% confidence that I could meet that date… boy would I not only be in hot water with management, but it also means that some uncertainties in my project at that juncture have me bent over a pipe.

Huge difference: Kickstarter and IndieGogo are NOT STORES; though it is completely understandable that people don’t notice this, since campaigns promise deliver dates, discount “prices”, flash “sales”, etc. But that’s a can of :poodle:.

SmartThings is a fully operational consumer products company backed by a huge corporation (Samsung). SmartThings has wisely chosen to not promise any release dates, features, or pricing.



I’d rather a company say “hang tight we are trying to get it right” then the other option… “Ooooops we tried to appease you by releasing it ‘on time’ but we got it totally wrong”

SmartThings is playing it right.