The goal here is to migrate my C8 to the new Pro and have the Pro do all the app work while having the C8 do just the RF. My C8 will not handle the new OS build in the works.
I have read, and printed, a lot of advice but making sure I don't miss a biggee, gotcha, step is important. Please feel free to hack this first draft up and advise.
Pause all pistons and backup WebCore and C8
Change C8 IP to new assignment, reboot. New Pro will assume old IP (for Dashboards etc.?)
Backup C8 to cloud using "Create a cloud backup for C-8/C-8 Pro migration" + how-to doc
Restore to C8 Pro without Migrate Radio buttons ticked.
Turn off Pro radio after restore.
Confirm basic functionality/device/apps migration
Boot C8,
Enable Hub Mesh on Pro and C8
C8? "Settings - Hub mesh, Update" to migrate all device
Unlink all virtual devices from C8 and move to Pro for Webcore or just leave as linked?
Resume Webcore pistons on Pro when devices sync
C8/Pro remove duplicate apps with HPM
Fix Dashboard/API links/Bitly/Tile Builder etc.
Agree that it’s worth testing to see if the Pro can handle your needs first because it is a bit more administrative overhead to manage another production hub. I ran 4 hubs separated by protocol for 5 years and then migrated to 2 hubs when the Pro came out.
My 2 production Pro hubs is a similar setup of what you are proposing, one radios only and one apps only. I have 200 radio devices on one hub and a total of 360 devices on my “coordinator” hub which includes radio meshed devices and a ton of LAN and virtual devices.
Your steps above are accurate for a 2 hub migration though you dont need to create a migration backup. You can just download a hub backup from your radio hub and restore it to the new Pro since it will contain all your existing apps, virtual devices and radio device records. Then you can use device swap app to swap the old radio device with the new mesh device.
Ok, sounds like I should give the Pro a try first before playing Meshy meshy.
It seems like that would be the less frustrating premier step. @ritchierich I thought you had to do a migration backup as it was the only method that captured and repopulated the actual radios?
I have a C8 pro and have been adding new devices regularly, as some are in an adjacent building I have been running into signal strength issues. Just added a C8 in the new building and Hub Mesh was really easy to set up.
Question - if a device was paired with the C8Pro (with a weak signal) and is now shared with the C8, which radio is the device communicating with? The devices work from the new C8 dashboard, but seem a little lagging
Also all devices appear on the C8pro network map, nothing on the C8 network map (even though they are on the C8 dashboards and working)
The radio you paired it on, so by your description, the C8Pro.
If all you did was plug the C8 in and share Hub Mesh devices to it, you have not helped your signal strength situation at all. "Hub Mesh" just shares the device data between the hubs, it does not do anything with Z-wave or Zigbee meshes.
You need to exclude/remove the device from the Pro and pair it to the C8. Then if you want to use it in rules or dashboards hosted on the Pro you share it back to the Pro via Hub Mesh.
I have just found out my iBlinds are DoA when upgrading to JS as there are issues with the driver (as with the Fibaro 222).
Depending on how far out the release from beta is and how dedicated the community creators are for the driver updates I may have to run the mesh after all and move the failing devices to the ZIP/Gateway C8 to keep things working.
