Confirming Details of C-5 to C-7 Migration With Hub Protect

I've read the full Hub Protect migration guide, but just want to ensure I'm understanding all this correctly.
For the most seamless migration, you need the US C-5 and US C-7 models. The migration will transfer all the Z-wave devices without any user interaction (no need to exclude/include). The zigbee devices will all needed to be re-included (but will pair up to the migrated device in new C-7 hub).

Short version of the process:

  1. Purchase Hub Protect for C-5 and setup
  2. Run Z-Wave repair on C-5
  3. Cloud backup C-5
  4. Disable Z-wave on C-5, then shutdown C-5 hub
  5. Register new C-7 hub on same account, then reboot
  6. Select Backup/Restore on C-7, pick Migrate from the latest C-5 cloud backup
  7. Select Migrate Z-wave Devices during the migration process
  8. When migration is complete, verify in Location/Modes that the new hub name reflects [old hub name] (new), rename if desired
  9. Discover zigbee devices by running Zigbee discovery and interacting with each zigbee device to start discovery. When discovered, they'll find and use the existing device setup.

That's it?
Assuming that's all correct, the one confusion is whether the C-7 is required to have Hub Protect plan as well as the C-5 in order to do the migration as outlined?

Appreciate any clarifications/confirmations on this process.

Thanks!

No.

The rest of your plan is pretty much exactly what I did a couple months ago (you don't need to disable z-wave on the C-5 before shutting it down).

2 Likes

Depending upon how many Zwave devices you are trying to move, you might consider doing it manually. Bruce outlined a pretty good procedure about how you do this.

I had about 40 Zwave devices to migrate, and I did it manually last week. If I had to do it over, I would have used the Protect service. It took forever to migrate that many devices.

But if I only had like 10 Zwave, or were replacing a lot of old devices (or leaving them on the C5) with new devices on the new hub, I would just do it manually.

2 Likes

I have a ton of devices, which is why i bit the bullet on this.

I have a question on the Zigbee devices though (step 9 here). I tried interacting (power cycling and pressing buttons) but it really seems like they all require a reset and rediscovery. Am I doing something wrong or is it really like Step 11 in the Hub Protect guide?

Zigbee devices are contained within the hub database and will be retained when you migrate, but it will be necessary to re-join devices to the new Zigbee radio by manually reseting them.

I have some hard to reach or hard to reset devices I'd rather not struggle with...

Thanks!

You put the devices into pairing mode, while the hub is also in pairing mode. They will say "previously discovered device" and everything will be back to normal.

While it is a pain to put everything into pairing mode, it is a lot easier than starting from scratch and breaking all your automations.

I don't think that can be avoided.

Alright. Thanks for confirming! I gotta do what I gotta do, I guess...

Finally got around to migrating from my C-5 hub, using the instructions outlined. The process went quite smoothly, automatically migrating 32 z-wave devices and preserving all my devices, rules, dashboards, etc. I had to manually re-include 45 zigbee devices, which took a while but every one of them found the existing entry and restored the functionality. I had only a couple of hiccups:

  • Two z-wave devices didn't seem to get included. Both are older devices and I've had some issues with them in the past (Enerwave ceiling motion sensor and Remotec ZFM80). Both devices just needed to be run through the inclusion process again, and then they paired up. Remotec was problematic because the programming button no longer works (hooking up the external switch works as a backup programming button).
  • Google Home integration had to be reconnected (to the new hub) via the Google Home phone app.
  • Needed to switch the Hubitat app on my family's smartphones to the new hub, matching them up to the existing entries.

Thanks for the developers for making the migration process about as painless as possible!

1 Like

HI - I just tried doing a C5 to C7 migration, and it seems to have worked well - but I had one issue - and also realized I was unclear on some nuances.

The one thing that did not seem to work was a z-wave Yale lock. It shows up on the C7, but didn't respond to a lock command. Do I need to do something different for a secure zwave device?

My intention was to leave all my zigbee devices on the C5 and only move the Zwave devices to the C7 (18 devices currently, several more to add soon). Since the zigbee database was migrated - all those devices are now visible on the C7 , even though I don't plan to reset them and pair again. Should I manually remove them all from the C7?

I have several integrations via Maker API, as well as a hue hub. I was planning to leave all of these as they are on the C5. However, everything was migrated - should I remove all the apps or at least the children from the C7? Are they going to get triggered on the C7 if I don't? Does he migration process change anything on the source? Or only import things into the target?

I'm still a bit confused about how to use Hub Mesh. Since I"m going to keep my automations on the C5, I assume I will share the zwave devices to the C5. Do I need to then change the zwave devices in any apps to pick them up from the C7?

Thanks!

I would exlude it then re pair it (with security)

Remove unused devices from the c5 page as well as maker api and any dashboards on the old hub

When hub mesh is enabled on both hubs you can share devices from one hub to the other. They will show up as devices on what ever hub is using them. So for instance, your lock. If you have that being shared in hub mesh and you have hub mesh turned on in your C5, that yale lock will show as a lock device on your C5 and your automation can use it simply as another device.

Hi @rlithgow1 , thanks for the reply. I think I asked my questions badly. Let me try again.

  1. I tried to use Hub Protect/Migration to move all my zwave devices from c5 to C7. Are you saying that this won't work for the lock and I should exclude from the C5 and then add to the C7 manually?

  2. I have nearly 60 zigbee devices and a lot of automations and integrations using them. I plan to KEEP those on the C5. I'd rather not reconfigure all my integrations and it doesn't seem like there's a big reason to move all of those to the C7. However the migration copies everything to the C7. Should I manually delete the zigbee devices, Maker API instances, and app children that were migrated to the C7?

  3. I understand that I will use Hub Mesh to share the zwave devices from the new C7 and then link from the C5. Once I've done that, do I need to replace those zwave devices in the automations or will the existing automations recognize the migrated devices automatically? Part of what is unclear to me is whether the migration process reconfigures anything on the source hub - or only copies things to the target hub.

If those devices are still in your device list in the c5, run device swap and pick their corresponding device on the c7 then delete the original c5 device.

Delete anything on the c7 that you want on the c7./ Apps, devices. etc.

I'm saying if for some reason the lock was moved and it's not responding to commands from the device page, I would exclude, factory reset, and re pair the lock again to make sure it's clean.