My C8 Pro is out for delivery (under 48 hours from Arizona to Teesside - pretty good ), I've had a look the docs for migration but have a couple of queries before I begin later:
Edit: It's been delivered - 42 hours Arizona > North Yorkshire
1 - My C8 is in the beta group. I assume that before I restore the C8 Pro from the migration backup, I'll want to get the Pro on the same version. I guess I'll need to power up the C8 Pro, get the hub ID and post a request to get it enrolled in the beta program. Who's the best person to tag for that request, as there'll be a period while I'm waiting for that when I'll need to keep the old hub running too?
Edit - I've registered the new hub to my account john.**.*******on@icloud.com. @bobbyD can someone please add it to the beta group
2 - Zigbee Channel. Does the migration backup contain the channel setting for the Zigbee radio? If not, I'll want to set that on the Pro before I restore the migration backup to ensure the same channel is used and doesn't conflict with my Hue setup.
Edit - I've set the channel manually the same as the previous hub
3 - Z Wave Z-IP or JS. By default what will the Z Wave stack be? As my C8 is on Z-IP I don't want it to be on JS after restoring the migration backup. If the default is JS do I need to switch to Z-IP before restoring the migration backup?
Edit - Confirmed that the hub comes set on Z-IP
4 - Should I expect shenanigans with integrations using maker api? (external dashboards, node-red amongst others) Will I need amend token IDs in connected services? I assume these will be different even after restoring the backup.
I'm sure something else will come to mind and blindside me.....
You can downgrade your existing hub to a non-beta version and proceed that way. You can then have the new hub enrolled in beta after. You just want both hubs to be on the same version before migrating. It's totally your call on how you want to proceed.
I'll wait for beta on the new one, as I'm using and testing current beta features "I could tell you, but then I'd have to kill you. What happens in beta stays in beta" - Though your tag would suggest you're also in beta
So, for clarification, will links to the original hub maker API still work? (the same access tokens carry over?) I thought the new hub created new access tokens you need for maker API. This has been a major factor in my delay in upgrading as I use several tasker integrations that rely on get requests to maker API.
Right - new hub is enrolled in beta and updated. It's game time
Migration backup is done - a bit strange as when I go into Cloud Backups > Migration Ready Backups on the C8 it does not show, however it does show on the C8 Pro. I'm not sure if that's how it's supposed to work but it does cause a bit of confusion....
3rd party dashboards and integrations working (mostly)
To resolve:
Zigbee showing the 'weak channel' warning despite being set exactly as the previous hub (which is now powered down) and the hub is in the precise same location
Apple Home. I use Homebridge. Most devices working but a few not playing (Harmony activities working from device menu but not updating on Apple) - Fixed with Homebridge restart.
Apple Shortcut not working Fixed after editing shortcut - needed to match it to the new url in maker api
I believe that is by design, so you can't use it as a "free" single cloud backup on the same hub. When I got a warranty replacement C8, I had to buy cloud backup to do a full radio migration from bad C8-> new C8.
), I've had a look the docs for migration but have a couple of queries before I begin later:
