SmartThings Hub Version 2.0

Other than bluetooth what else are you referring to? Now that Smartthings has a IFTTT channel there are numerous devices the lay person can tap into.

I would definitely like the next version of the hub to have a backup. Depending on what you have connected you will need to have something in place other than receiving a notification that the hub is offline.

I would also like to see on board memory.

Right now the majority of our events take place based upon a motion or open/close sensor. I think it is only a matter of time before voice integration will become mainstream. Perhaps a speaker/mic built into the.

It would be neat to have indicator lights on the hub in which the user can define. There are so many things that you could do with something that simple. Think about Hue Lights or Blink.

The possibilities are endless.


Well this has much more to do with us getting an interface for “rule-building” than a V2 Hub but we want to do it.


Well you should be pleased. Both Bluetooth and some offline processing are the largest upgrades on the second version of our hub.


I’m assuming not but can you give us a SWAG on the the timing for a V2 hub?

Less lag with Aeontec multi sensor to Phillips Hue.

Q1 of 2015. We will have a lot of details coming out in January.



I like how open you guys are on your plans.

Is this calendar year quarter so we can assume March 31 as more likely?

Isn’t that usually the way of it? :slight_smile:



Yes, for sales it is January 1, but development March 31. I was just curious which camp you are from.

Again, thanks for sharing with us.

Would love to have a drag-n-drop, flow-like interface so that the hub and each thing would have their own icons with their attributes embedded within them. Once a new thing was certified by SmartThings to work with the platform, it would then be available as a new icon to use in the flow.

(Bonus: For consumers, I firmly believe this would drive new thing adoption. Once a person sees that new locks, sensors, or some other thing solution is available and would instantly/seamlessly integrate with their hub, a quick click would let them buy it and then quickly add it to a flow and then configure it once it arrived).

Example of a Flow and the “Time ROI”: We’re on RingCentral for telephony and it’s a configuration nightmare. Initial setup was nearly 30 hours a few years ago. It’s such a pain-in-the-arse to modify or add new hardware to that we basically…don’t.

So last month I did a test-before-switching with two other providers and the usual VoIP setup nightmare continued. While shorter, the setup time was still roughly 20+ hours each and required connecting with tech support several times. “Damn…looks like I’ll have to stay at RingCentral,” I thought.

Then a midsize company CTO buddy of mine told me about Tried the demo, signed up, and created my first flow which you see below. The punchline? It took me 15 minutes to set up and test! I’ve since built two other flows for customer support and incoming sales queries and it took longer for me to think about the interaction flow I wanted then it took to build it.

THAT is the sort of interface I’ve longed for with SmartThings, especially as my home layout becomes more complex. Doing everything on my iPhone or iPad works, but I’d much rather build sophisticated interactions with a flow-chart-like metaphor similar to what Telzio delivers.

My $ .02


Any chance we’ll get a USB host port? The added cost is minimal (just a connector really) since all SoC’s have a built-in USB controller these days. But this would make the hub infinitely expandable and contribute to the Open Platform image the sets SmartThings apart from the rest.

1 Like

That’s a great example Steve. Checking it out.


The plan is to have a USB expansion slot, yes.


What’s the upgrade prospects of the current Hub? I need to buy a few more, but depending on the upgrade prospects, I’d hold off one of them and use the one in my house currently there and buy the new one for my house.

I wouldn’t expect you to be able to upgrade the physical V1 hubs. Firmware alone won’t cut it as the processor and radios will be different. We are also unsure of any monetary incentive or program for upgrading but we are looking into some stuff like that.


For someone like myself who is just thinking of getting into these products, this is making it a hard choice.


We’re giving way more notice than most companies give. People can make their decisions on what value to get now and later. I would love to see a program where you can gift your V1 hub to friend or something and get a discount on a new v2 hub. But I am speaking as @ben and not as SmartThings right now.


As your automation expands, the actual cost of the hub becomes a fraction of the total project cost. At least in this case you should only need to replace the hub. I’m more worried about the time cost of replacing the old hub with the new one when it launches. @Ben, I hope SmartThings will attempt to make that migration process as painless as possible?


Totally agree! SmartThings should learn from Quirky here. They partnered with major retailers and practically gave away Wink hubs for free (albeit for a limited time). This strategy will definitely pay off long term because very few people can resist a “free” offer. Even now, the Wink hub is half the price of the ST hub, although it’s probably at least twice as expensive to build. For the cloud-based services the primary goal should be to build up a user base and get developers on board, not to make money selling hubs.

1 Like

Migration is a very good point to bring up. There’s two aspects to it of course:

Hardware: I would think that it wouldn’t be possible to simply tell a z-wave product to report to Hub x instead of Hub y. This seems like a pretty big potential security risk to do this… I have to think that we’re talking about having to exclude/include every device individually… which will be a royal pain in the butt. But I’d be a little surprised if it’s possible to do it otherwise.

Software: On this side I think it would be at least a little easier to move existing configuration from one hub to the next. Though I suppose this depends a great deal on how Apps indicate which device they are using. Is there some built in code on the devices themselves that ST reads? If so, one I add my devices to my new hub they should be able to see that same code and just work. If not… if it’s the Device Network ID, for example… then it’ll be much more problematic.

I can see this being a potentially HUGE project for individuals who have a lot of devices and a lot of custom setup.