I have a new ST V2 hub to replace one with a faulty ZigBee module. However when I try to migrate the hub. It says the New V2 hub hasn’t got enough memory. What limitations are there for the migration process ?
Hi, @Jeff_Gallagher
Can you provide support access to your account, please?
- Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (⋮) and choose Settings
- Toggle on Account Data Access
- Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
See more information about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support
HI it worked on the 3rd time of asking. not sure why. I’m trying to rebuild my whole landscape with a new Smart Home Hub 2 and I’m having to move stuff all over the place. Forgot to join the new Smart Home Hub 2 to my existing Thread network so have to now move them back again 
Can’t you use the Manage Thread Network in Settings for the hub to unify them?
Yes but can only be done before I add devices. Doh.
I’ve all my Google devices and Apple on one thread network so want to have all my ST hubs on the same thread for stability. Will take a while to get it right. But will be better longer term.
Hi, @Jeff_Gallagher
So, just to confirm, the replacement is already completed, but only the process of having the hub in the same Thread network as the other devices is pending?
Yes. I had to move everything back off the new Home Hub 2, back to the original hub. Reset the HH2. Change the Thread network, then move everything back again. All worked seamlessly, except for my poor planning. I should have thought it through properly in advance. The only devices not working normally are the Locate the SmartThings Arrival Sensor. I’ll remove them and add them manually later.
1 Like
1 other minor “bug” and not even sure I would use bug. But the links to any community based drives are lost in the move. The drivers are moved, but the link to the drivers are not linked in the HUB
Hi, @Jeff_Gallagher
Do you mean that you can’t see a link to the channel where that driver is included? Where are you trying to see that link, for example, from Advanced Users App?
I will ask the engineering team about this, but I need support access to your account and the name of one of those drivers (to use as an example) to check if it’s only the link or the driver is currently unerolled from its channel.
Also having a very strange issue with the SmartThings Arrival sensors. They add no problem to the original hub and are picked up (V3) hub. But the Aeotec Hub can’t nor can the HH2 hub
Hi, @Jeff_Gallagher
Following up on the issue with the “driver links”. Whenever you’re available, please share more details about this. I know you keep working on migrating your devices.
After migrating the Hub to a new hub. The links above all disappeared. I created them manually. but I would strongly advise as a workaround that anyone mograting to the new Hub should export the driver channels to a csv or JSON before they start, so they don’t lose any of the links
This is a well-known issue. Channel enrollments for existing hubs do not get migrated to the new replacement hub.
2 Likes
I checked with the engineering team and the channel enrollment isn’t part of the migration, so this is expected behavior.
However, it’s important to note that this doesn’t affect driver updates, they’ll continue working normally.
We’ll create a ticket for the team that handles the Advaced Users app to be able to provide the corresponding links in both “Driver channels” and “Installed Drivers” > “Driver Channel”.
Just a heads-up, the implementation of this change will depend on the team’s workload.
1 Like
The problem is that it isn’t what many of the users expect. It can be seen as counter intuitive.
However it is also understandable as enrolling a hub in a channel is typically carried out manually by users, with a user subscription to the channel a prerequisite. So when it comes to a hub replace, and in particular to a hub backup in an automatic migration, who would the user be and by what authority would the enrolment occur?
This is the particular area of concern for me, mainly because I don’t like spreading misinformation. I have been one of the more frequent flyers when it comes to popularising the idea that, with the exception of the production default driver which is a special case, channel enrolments are a requirement for updates, and unenrolling a hub from a channel a valid weapon in preventing them.
Things could have changed of course. Hub replacement may have moved the goalposts. My having been talking cobblers all along is still a reasonable assumption though.