I haven’t migrated from the V1 to V2 hub. Actually in terms of V1 hub response times I seem to keep getting faster response times to things like motion triggers the more people migrate to V2.
I hear the migration utility was supposed to be out before the end of the year. Is there any word on when the migration utility might be available?
If it will be out in the next month or two I’m probably going to keep delaying unless my V1 stops working.
I’m in this boat too. While there are some frustrations that I would like a v2 to fix, I simply don’t have the available time to migrate 70-80 devices.
And if I did have 2-3 free days, it would be hard to justify spending them on that, as opposed to a half dozen other things that need to be done around the house.
Hence I’m waiting for the migration utility too, indefinitely, perhaps.
SmartThings is more likely to kill your V1 Hub than have a “migration tool” out by the end of 2015.
Of course, both are improbable.
I definitely recommend NOT migrating. My v2 turned out to be defective, and now I have to migrate my 80 devices all over again. I feel just miserable about it.
Support also said the “v2 is pickier about internet access” and that “it wants to be connected directly to a router or modem.”
Word from support today on the migration utility was that “it’s on the roadmap, but there is nothing coming out any time soon.”
Have 85 devices, between two houses. No problem with migration just took time.
Nice. Worth it though?
Honestly, not yet. But it is done, and any improvements that come I am ready for now
I’m wondering if my V2 is defective now. Crap. I did read all the complaints about V2, but decided to do it anyway because my V1 devices were behaving badly since the new iPhone App. I geeked around with ST early in the year, set up about 100 devices, and then got busy and didn’t add or play around with anything for a while so I may be a bit behind the times… Anyhow, lots of lights going on in the middle of the night against what was programmed, some devices not working @ all, open/closed indicators showing incorrectly on perimeter windows, so I thought starting over would do me good…
Hub was significantly relocated @ my house about a week before the big V2 app release, so could have been any number of catalysts for my issues…
Anyway after 12 hours of migrating (shoot me now) I’m having issues finding devices… kind of geographical in nature, but there are a few oddballs close in that didn’t exclude properly despite the app’s claim that it was successful. Did 2 repairs, no help. they only took 5 mins too, which is suspect.
Now I’ve got some critical items that won’t pair (garage door opener, door lock etc) a distance away that i really REALLY don’t want to unbolt and drag into my master bedroom to pair up close. Just did the unplug/battery removal/replug, and am on repair #1… we shall see… Next step might involve shooting the light switches and open/closed sensors down with a shotgun out of frustration.
If you have a minimote, you should be able to use that to add or exclude Zwave devices other then door locks. They can help a lot with stuff that is wired in place.
Yeah I have 2 of them. Unfortunately they’re doing the solid red thing and not allowing include or exclude mode. I did a reset, and then it started working in exclude mode, but became disconnected from the hub. catch 22.
Any zwave controller can do a general exclude no matter what network it’s on. So your minimote can actually act as its own controller also. That means it can do a general exclude whether it’s been connected to your SmartThings hub or not.
The minimote can’t do the include until it’s on the SmartThings network though. But depending on the device, you may be able to do the include for the wired device just fine from the hub once you can get it excluded. Particularly if it’s a Z wave plus device.
My first suggestion, however, would be to work with support and get the mini motes working with the new hub. They are officially supported devices, they are easy to carry right next to the hub, they have meaningful status lights, and as mentioned, they’re useful in dealing with the other wired devices.
If you can’t get the minimote to pair, there’s a problem to be solved before you throw range into the mix.
OK! Before you wrote this, I actually just excluded the minimote and used it as a general exclude (which worked on the lock as well, which was exciting) and got all the “stuck” things excluded. Then, I did the full unplug/power down AGAIN and repaired 3X. (repairs are still lightning fast - like 3 mins). Finally, The White Smoke!!!
Got all devices paired and now I can start the fun stuff of actually programming. First up, LFM-20 Garage door. I know I Know… I’ll be happy if I can get it to work by just being a momentary switch.
Thanks for the suggestion. Bottom line, minimote is the way to go for exclusions…
Cheers
With the new firmware (14.13), can someone chime in on the status of the V2 hub now, especially compared to the V1? While some new functionality has not been turned on yet, and of course migration to an new hub is a pain, my optimistic viewpoint is that the V2 hub doesn’t appear to have any major issues versus the V1 hub.
Am I wrong? If so, could someone summarize those outstanding issues.
Here is my chiming…
The new firmware has barely been out a few hours, not even days. What could make you possibly think that all of its bug fixes and new bugs have surfaced yet?
I strongly recommend waiting for an extended period of calm before assuming Hub V2 isn’t worse or better than Hub V1. Statistically, debugging takes a lot of time.
OK, let’s ignore the recent firmware. Can someone list the current issues that exist with the V2 hub, that aren’t present with the V1 hub?
Nothing has been confirmed. But there are number of reports from different members that they suddenly lose about half of the network. It could be half of their Zigbee devices, it could be half of their Z wave devices. There are a lot of reports of sensors “stuck” reporting only open or only closed or constant movement, in some cases even when the batteries are removed from the sensors altogether.
Again, nothing has been officially confirmed, but the behavior does look somewhat as though the hub is getting out of sync with the cloud account. That could have something to do with the introduction of local processing for hub 2 even if the local processing isn’t being used very much.
There is also the poltergeist problem where there just seem to be random events sent through the network. At my own house the zwave lock started just unlocking on its own with no actuating event in the log. That is you could see the command being sent to unlock it but no reason why that command should have been sent. Also have the same problem with just some random switches being turned on. This again could be some kind of sync problem.
So I can’t say for sure that that is a V2 versus v one problem, but it’s a problem I never had with v one and I now have every few days with v2.
It could be something altogether different, it could be something that also affects v1, but it could be that maybe local processing isn’t quite fully baked yet.
FWIW…
:)) I love the poltergeist thing! Spooky as heck. Maybe they finally implemented queuing of failed commands and the hub is letting it all out 
On a more serious note I had a ghost set off one if my motion sensors on my v1 hub but just one random event which interestingly didn’t set off my alarm. Weird ghost
My V2 hub quit working altogether… sigh…
So ST sent me a new one and I have to rebuild. I have no clue where to even begin since my old V2 hub is dead and I can’t exclude my devices. I have a minimote so maybe I can use that to do exclusions… not sure how. Should I remove the old devices and the hub and location using the web IDE? Any advice or guidance would be appreciated since the new hub arrived with no instructions at all - not even a return code for the old broken one.
In the IDE, go to “My Hubs”, click on your new hub, then “View Utilities” near the bottom of the page. The first thing on the next page should be “Z-Wave Exclude”. You can use that to do a general exclude on your devices without needing the old hub.
Thanks… got it. I actually got my old hub working so I can do the removals in a more orderly fashion. However, I must admit that there is an evil little voice in my head telling me to just keep the old hub since it is now working. But the good angel in my head is reminding me that this old hub fails with no warning in weird ways that are unpredictable and not reproduceiable. So I guess I should just bit the bullet - but man, I have soooo many sensors. I hate the thought of doing this. Sure would be nice if there was a way to move the sensors from one hub to another by just reassigning them. There must be a way to trick the new hub into thinking it has sensors already associated with it…