¶ How to Migrate to a C-8
If you have a new Hubitat Elevation model C-8 hub and are looking to migrate from a C-5 or C-7, follow the steps below to perform a seamless migration, including Z-Wave and Zigbee devices.
NOTE: Some users are currently experiencing problems migrating from model C-5 to C-8 when using the current platform version, 2.3.6. We are investigating this problem and hope to have it fixed in the next release. See this post for more information: https://community.hubitat.com/t/investigating-migration-failure-from-c-5-to-c-8-platform-version-2-3-6-146/127859
¶ Migration Overview
¶ Preparing the Old Hub
Ensure your current ("old") hub:
- is running the latest platform version from Settings > Check for Updates.
- is not exhibiting any problems with apps or devices (for example, check Logs for a large number of unexpected errors), Z-Wave "ghosts." etc. – a migration per se will not fix problems.
- is running the latest Z-Wave radio firmware (check Z-Wave Details for a Firmware Update button, which will only appear if an update is available); recommended but not required.
¶ Performing the Migration
-
On the "old" hub:
- Disable any cloud and LAN integration apps and drivers to avoid conflicts with the new hub. See the LAN/cloud notes below for more details.
- If you have enabled lock code encryption on any lock devices, disable this feature on those devices (this feature can be re-enabled on the new hub afterwards if 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.
-
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.
-
Power on the new hub and connect it to your network (wired preferred but wireless is possible; see Registration and Setup). Continue with the next step when you get to the Welcome to Hubitat Elevation screen the new hub.
-
On the new hub, select the Migrating from another hub? link (if this link only directs you to this documentation, choose "cloud" under "Restore from local or cloud backup?" instead). Log in to your My Hubitat account when prompted. This must be the same account under which the backup in step 2 was created.
-
On the cloud backups page that will appear, confirm that you have read all of the instructions in this document. Then, select the Migrate button corresponding to the backup you made in step 2.
- If you used the cloud link in step 6 instead, choose the migration-ready backups link at the top of the page instead (or show all backups if you do not see this), 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 Zigbee and Z-Wave devices.
- If you used the cloud link in step 6 instead, choose the migration-ready backups link at the top of the page instead (or show all backups if you do not see this), find your cloud or migration backup in the list, and select the
-
When prompted, select the options you'd like to restore (Z-Wave, Zigbee, and/or File Manager). If your old hub was configured with a password for cloud backups, enter that password where prompted. Then select Migrate and confirm the restoration.
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.
- Wait for the restore to complete. When the new hub comes back up, it should function nearly identically to the old hub. If you had any LAN or cloud integrations on the old hub, re-enable them one-by-one. See below for additional notes on LAN, cloud, Zigbee, and Z-Wave if applicable to your setup.
¶ Migration Notes
Certain devices and integrations may require some additional action after migration:
¶ 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. Cloud integrations 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 (see: https://help.sharptools.io/article/108-hubitat-migration-tool)
Other notes:
-
Users of the Hubitat mobile app should open the app after migration and choose the new hub under Settings > Select Hub (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 Migrate Zigbee Radio option enables users to seamlessly restore all Zigbee devices to the same functionality as on the old hub.
- Migrating Zigbee to a new hub is supported only on model C-8; Zigbee can be migrated from any hub model C-7 or C-5 (if using internal radios).
- If you decide to switch back to the original hub after migrating and Zigbee has already been used on the new hub, some Zigbee devices may require being re-paired to the old hub in order for them to work again.
¶ 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
- Migrating Z-Wave to a new hub is supported on all C-7 and C-8 models, with migration from these models and select older models also possible; see Hub Protect - Migration for details
- If you decide to switch back to the original hub after migrating, most Z-Wave devices should continue working without additional action (but both hubs should not be used at the same time) if no network/node changes were made. Hub Protect users can also back up and restore (with any changes made) to any supported model.
¶ What Do I Do With My Old Hub?
Most users do not need two (or more) hubs, so if you do not plan to use your old hub again, simply shut it down and disconnect it from power. If you plan to re-use the old hub 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 migrated) on the old hub from Settings > Zigbee Details.
- Reset the Z-Wave radio (if migrated) on the old hub from Settings > Z-Wave Details.
- Perform a soft reset on the old hub (and any related steps you may need to do for your particular situation) as described in the Soft Reset docs.
CAUTION: Do not perform a reset of any kind on the old hub until you have verified that the new hub is working correctly.
If you plan to use Zigbee on the old hub again, besides resetting the radio, the Zigbee channel on the old hub must be set to a different channel from the new hub. (For those who want the technical details: they will share an IEEE address, carried over from migration, even if the PAN ID is different; this will no longer apply if Zigbee on the new hub is ever reset and not migrated.) For Z-Wave, a simple reset, as above, will suffice.