¶ How to Migrate to a C-8
Some users may choose to migrate to the new C-8 hub for various reasons, including new features such as:
- built-in Wi-Fi connectivity (Ethernet also available and recommended)
- Z-Wave 800-series chip (older models use 700- or 500-series)
- Z-Wave and Zigbee supported for migration to C-8 with Hub Protect
- external antennas for Zigbee and Z-Wave
Many of the steps below applies to all models, but this document is written with C-5 or C-7 to C-8 migration in mind specifically.
NOTE: While tools are in place to make migration as seamless as possible, there are still many things to consider when moving from one hub to another. We suggest reading this entire document before starting your migration, then reading again from the beginning when you are ready to start — otherwise you may miss important notes that are relevant for your setup.
¶ Performing the Migration
To seamlessly migrate the hub database plus Z-Wave and/or Zigbee to a C-8 hub from a C-5 or newer hub:
-
Ensure the "old" hub is running the latest platform version from Settings > Check for Updates.
-
On the "old" hub:
- Disable any cloud and LAN integration apps and drivers to avoid conflicts with the new hub. See the notes below for more information.
- Note that File Manager is included in cloud backups (and can optionally be restored) as of platform 2.3.4.138 but is subject to a 100 MB limit. You may wish to download these files locally for later manual restoration if needed.
- If you have enabled lock code encryption on any lock devices, disable lock code encryption on these devices before proceeding (otherwise, apps like Lock Code Manager will not be able to read the previously set codes after migration). This feature can be re-enabled for these devices on the new hub afterwards if so desired.
-
Create a cloud backup on the old hub:
- Navigate to Settings > Backup and Restore.
- If you are a Hub Protect subscriber, select the Cloud Backup tab, then select Back up now. (Make sure Cloud Backup is selected first!)
- If you are not a Hub Protect subscriber, qualifying C-5 or C-7 hubs will see a Create a cloud backup for C-8 migration tile on the Backup and Restore page that can be used to do the same. (If you do not see this option, your account/hub is not eligible for this one-time option, and seamless migration is not possible without Hub Protect.)
-
Confirm that a cloud backup was created. If you do not see a list of backups at the top of the page, select this hub's only in the Show all or this hub's only heading at the top of the page. Look for cloud or migration (depending on the method used above) under the Type column and the name of the current/old hub under Name to find the backup you just made.
-
Shut down the old hub from Settings > Shutdown. After the hub is shut down, remove the hub's power supply. Shut down the hub as soon as possible after making the backup.
-
If you have not already connected the new hub to your network, do so now. See Registration and Setup and resume with the next step when you get to the "Welcome to Hubitat Elevation" screen the new hub.
-
On the new C-8, on the "Welcome to Hubitat Elevation" screen that appears after booting (and network setup, if applicable), select the cloud link under Restore from local or cloud backup?. Log in to your My Hubitat account when prompted. (If a new platform version is available, the hub will download and install it; wait for this process to complete, if applicable.)
- The new hub must be logged in to the same My Hubitat account as the old hub in order to see its cloud backups, necessary for restoration.
-
On the Restore from backup page, select the migration-ready backups link at the top of the page. Find your cloud or migration backup in the list, and select the
"migrate from another hub" icon (under the Actions column) corresponding to this backup.- Local backups will not appear under "migration-ready backups" because they cannot be used to restore Zigbee or Z-Wave. A cloud or migration backup, created as above, must be used to migrate these devices.
-
When prompted, select the options you'd like to restore (Z-Wave, Zigbee, and/or File Manager). If your old hub used a password for cloud backups, enter that password where prompted. Then select Migrate and confirm the restoration.3
NOTE: A restore will reset and overwrite the main hub's database plus one or both radios, depending on the options selected. You cannot combine hub database or radio backups from multiple hubs.
- After the new hub comes back up, it should function similarly to the old hub. If you had any LAN or cloud integrations on the old hub, re-enable them one-by-one on the new hub after the restore is complete. See below for additional notes on LAN, cloud, Zigbee, and Z-Wave if applicable to your setup.
¶ LAN/Cloud Migration Notes
- Cloud integrations may need to be re-authorized to function again. For some, this is usually simple as opening the integration app on Hubitat and selecting Done. These include:
- Amazon Echo Skill
- Ecobee Integration
- Google Home
- IFTTT Integration
- Life360 Connector
- Rachio Integration
- webCoRE (we suggested backing up all pistons beforehand just in case)
- Other cloud integrations may be tied your hub ID (which is different for each hub) and require additional action:
- ActionTiles (may need to re-create dashboards, as devices linked to hub ID; may also affect licensing once out of public beta)
- SharpTools (consult SharpTools documentation: https://help.sharptools.io/article/108-hubitat-migration-tool)
Other LAN and cloud notes:
-
Users of the Hubitat mobile app may want to launch the app after migration and choose the new hub under Settings > Select Hub in the mobile app (if the app was associated with the old hub).
-
If using Hub Mesh, if the other hub(s) do not automatically find the restored hub within a few minutes, use the Settings > Hub Mesh > Update tab to "swap" the old hub with the new hub.
This list refers to built-in apps only. If you use third-party apps or external systems that refer to cloud endpoints (which are unique to each hub), even ones provided by built-in apps, you may need to reconfigure them. This includes cloud endpoint triggers in Rule Machine, Maker API cloud endpoints, Hubitat Dashboard cloud links, and others.
Local systems may or may not be affected, depending on whether they initiate a connection to your hub by IP address and whether your new hub IP address is the same.
¶ Zigbee Migration Notes
-
Selecting the new Migrate Zigbee Radio option (new to model C-8 only) enables users to seamlessly restore all Zigbee devices to the same functionality as on the old hub.
-
A Zigbee migration should, for the most part, be considered one-way:
- Backwards restoration to original hub may require all Zigbee devices to be factory reset and re-paired to older hub (controller) in order to operate properly.
- The reset requirement will vary depending on the type of device, how active it was on the other hub and how long the other hub was running. Should you need to return to the old hub after attempting migration, it is best to check the operation of each device and reset as needed.
-
If the old hub is used for Zigbee again, it must be used on a different channel
- This is true even if Zigbee is reset on the old hub
- This is because it will now share an IEEE address with the new hub (even if the PAN ID is different)
- If the new (C-8 hub) Zigbee radio is reset after migration from the old hub, the above no longer applies
- This is because resetting the C-8 Zigbee radio will reset its IEEE address to its original IEEE address instead of that of the hub from which it was migrated (so there is no longer a collision between the two)
- However, separate Zigbee channels are still recommended to avoid interference
CAUTION: Do not reset any radios (Zigbee or Z-Wave) unless you understand that this may require re-pairing all devices. For example, resetting the Zigbee radio on the new hub is not a solution to avoid the above concerns while maintaining seamless migration.
¶ Z-Wave Migration Notes
- Selecting the Migrate Z-Wave Radio option enables users to seamlessly restore all Z-Wave devices to the same functionality as on the old hub. This option is available on models C-7 and C-8 (with migration from select older models also possible; see Hub Protect - Migration for details).
- If you plan to use the old/original hub again, it is recommended to reset the Z-Wave radio from Settings > Z-Wave Details.
- This enables it to create a new, separate network that will not conflict with your migrated network
- If you do not plan to use Z-Wave on the old/original hub again (but do use the hub), Z-Wave can also be disabled as long as you remember to reset it if you decide to use Z-Wave again.
¶ What Do I Do With My Old Hub?
If you do not plan to use your old hub again, simply shut it down and disconnect it from power, as described above.
If you do plan to use the old hub again and you have verified that the new hub is working properly, then we suggest the following steps:
- Turn the old hub back on (plug it back into power and your network). As soon as possible after the hub comes back online, proceed with the next step.
- Reset the Zigbee radio (if used) from Settings > Zigbee Details.
- Reset the Z-Wave radio (if used) from Settings > Z-Wave Details.
- Remove any files from File Manager (if used and so desired) from Settings > File Manager.
- Perform a soft reset (and any related steps you may need to do for your particular situation) as described in the Soft Reset docs.
If you plan to use Zigbee on the old hub again within Zigbee network range of your new hub, see Zigbee Migration Notes above for important considerations.
CAUTION: Do not perform any resets on the old hub until you have verified that the new hub is working correctly.
Most users do not need two (or more) hubs. For creative uses other users have found — or more information on any of the above — we suggest searching the Hubitat Community forums.