Wasn’t there talk about V2 having Bluetooth? Did this protocol get removed during the development process? Or is it one of the “other wireless protocols” mentioned in the product description (I think on Samsung’s ST preorder page).
V2 has Bluetooth capability, but it won’t be enabled at launch. It will be enabled at some point in the future (I’m not on that team and have no idea what the actual timeline is).
So a migration tool is still planned? Good. I will wait - although local processing will be a welcome addition, having to start over, re-adding, re-building etc is a complete no-starter for me.
[quote=“JDRoberts, post:139, topic:20607”]
Note the device classes (!):
[/quote]Typical “everything but the kitchen sink” filing.
I see I am in the same boat as many others. Glad to see it was acknowledged, looking forward to the upgrade.
AMEN!!! Can’t understand why there are not more options remotes/controllers. People on the forum have responded that it is because ST focus is on TOTAL (hands-off) automation versus control. “With total automation, you never need a control, because the automation will know what you want and do it.” I love that ST turns on my coffee pot in the morning, the family room lights when it gets dark etc, but It is going to be a long time before it KNOWS the difference between me sitting in my studio reading vs listening to music vs watching TV vs working on computer vs composing vs rehearsing. Until then, I need controllers (preferably handheld wireless ones).
2 Likes
[quote=“garyd9, post:149, topic:20607, full:true”]
Look again: the kitchen sink is in there (class 11) 
but they did not trademark SmartThings for medical devices (class 10) Which surprised me if they’re going to use it with Artik and Sami. Made me wonder if that’s intended to show they really are serious about serving as infrastructure for other brands in that area. They did grab the wearables, but they left for example the big medical monitors out of it.
1 Like
Thanks for the feedback. After suffering through years of X10 frustration and hell, I was hoping Z-Wave/SmartThings might be the answer. While it’s way more reliable, it can still be maddening. Plus, none of the devices are inexpensive. And, I can’t believe how horrific their mobile app is. Whomever designed it hasn’t a clue regarding making it user friendly.
I appreciate the information and I understand there’s no requirement to upgrade. I’ll wait until the new hub is out, the glitches fixed and users can say it’s worth upgrading.
My two cents for those waiting for a migration tool.
I wouldn’t hold my breath.
The complexities of migrating zigbee and zwave mesh networks from one controller to another are hard enough.
Then combine that with moving all the cloud and local IP devicetypes.
Then combine that with all the smartapps installed.
I would love to see ST get this right, but realistically, it will cause far more problems for users then just creating a new location and moving what you want to move over, one device or group at a time and set up new or duplicate smartapps for the new location.
I have moved all my code and devices from a hub v1 to another hub v1 a couple of times as I’ve swapped out hubs due to some technical issues, and yes its a pain but that pain is over quick.
I wouldn’t wait for a migration tool, but that (and the above) is just my opinion.
6 Likes
Adding my +1 to my disappointment about the sold out status. I tried to buy a bundle within an hour of getting the mail (it was in stock) but the store was completely broken and would barely load pages. The next morning, poof sold out.
Looking forward to an actual loyalty bundle that I can buy as an actual loyal v1 customer.
Thanks for the insight, @pstuart. The idea of completely starting over has been my main hesitation, but if there’s unlikely to ever be a good solution, I may as well not worry about it. Any tips for the best way to set everything up? Can you still easily reference the old setup in the process to try and duplicate everything?
I have no idea how hub v2 will work when it ships, but assuming it will be similar to replacing a hub v1 the process for replacing a hub v1 was simple.
Just add a new location, call it whatever. Register the hub v1 to that new location.
Pick a device you want to move over. Remove it from old location, and any smartapps connected to it. This is the potentially painful part. Might be best to tackle by smartApp if you have a lot.
Once removed from old hub, switch locations, click + to add a device and put the device in pair mode.
The new hub v1 should find the device and pair, set it up again and you are good to go.
Install the smartapp(s) that used the device and reset that up.
For any IP / cloud based stuff, much easier, just go into ide and change the location and hub to new location and new hub v1. Those don’t need to be re-setup because they can just move. Might want to re-add them if you plan on using two hub v1s on same local LAN network. As it can get confused.
Depending on number of devices and smartapps it can take a few hours to a couple of days.
During the transition, you have access to your old location and everything still works. You can set up everything in the new location to your liking.
It is not like you have to do everything at once, or remove everything and start over.
I have no idea how hub v2 will work when it ships, but I have to assume the process should be similar to replacing a hub v1.
3 Likes
My idea of a “migration” tool would be something that would simply exclude/remove/uninstall every device (disassociating it from the SmartApps) from the v1 hub with one simple button push. I am left with a bunch of “orphan” devices which I can reconnect to my new “Customer Appreciation Bundle” 
Wait… They are sold out 
That’s not quite as bad as I imagined. Will still suck, though. I’ve got around 45 devices and around 130 smart apps listed in the IDE.
1 Like
I am going to be doing it and I have 100+ devices, devicetypes and tons of smartapps to set up.
I’ve been waiting a year for hub v2 and I see no reason not to do it ASAP. Just ship the dang things already!
Frankly, as long as it just does what hub v1 does and has a local scheduler as stated previously, this will solve most of the issues with smartapps not firing.
My wishlist is long, but the basics are pretty simple. I see no reason why any hub v1 user shouldn’t want to upgrade to a hub v2 besides not being able to order one.
However, since no one has a shipped hub v2, who knows how I’ll feel once I have mine. But frankly, it seems like a no brainer to me, especially at $99 even without the loyal customer bonus free sensors.
I was expecting maybe 150 - 200 price point.
It’s all speculation until we get a shipped hub v2. Can’t wait.
1 Like
If V2 did nothing but give us a Z wave plus controller, I’d upgrade for that. 
We’ll have to see what we actually get, but it’s hard to imagine it wouldn’t have zwave plus.
2 Likes
I’m not holding my breath for a V1 to V2 migration tool, but SmartThings will absolutely need at least some migration features (e.g., device swap / replacement) soon; and full Hub V2 to Hub V2 after that… Why? Because Hubs will fail from time to time in households with hundreds of devices, groups, and SmartApps.
Having the Hub fail (even / especially under warranty) is frustrating enough, but good customer service will have one overnighted to you. It will be essential that a Customer can be “migrated” to the replacement Hub within hours after receipt.
If SmartThings is to be taken seriously, then they have a responsibility as in some homes they will be a “critical” appliance.
I know the problem is complex… But it’s not rocket science and… NASA is about a 15 minute drive from SmartThings HQ. 
1 Like
And 2 of our 3 technical founders are Aerospace Engineer grads. 
4 Likes
Rather like my Ozzie cousins, as a UK KS backer, I was disappointed to hear from Support that International models were still in the pipeline.
So what happens to my loyalty discount?
Why cant I order US version, at my risk, to use US frequency ZWAVE.
Can you categorically state that you will actually produce international versions?
I asked the question at the London IOT events and didnt get a straight answer.
I just got a version 1 HUB that has the Z-Wave Plus logo on it. This one also does not use micro-USB to power the HUB. Haven’t taken the time to do the HUB swap yet. I might as well wait until version 2.