I know this is a relatively old topic. I finally migrated to the C-8 Pro. I did the cloud backup and subsequent download with the Zwave option.
all my non-zwave devices migrated great including my lutron hub.
My zwave devices all show up but none are operational. all zwave sensors are working. locks are not working but they post accuratelty (on or off and even the battery amount) with logs. Lights will not post status or turn on or off. Lights andsmart switches are leviton, lock are Schlage (I knew these could be trouble) and accent lighting controllers are Zooz.
I did a zwave repair and 10 of the 14 are complete, while 4 failed. I cant even get the devices excluded to even try a inclusion. Any ideas on getting these things operational. Again all devices are showing with nodes on the Zwave page but only passive items are working
I assume that you are using ZWaveJS not legacy? I think it defaults to jS. You may need to give it some time to settle, or try running configure on the misbehaving devices as well as what @thebearmay suggested.
I did the Z-wave radio reset. That removed all the nodes but kept the devices. I deleted the devices and excluded. I then reincluded them and tried to do a replace device. That part didn’t work so I had to manually update rules, scenes, etc.
Considering the same upgrade and very worried about this. The wife gave me a C8 Pro for Christmas and I'm currently running with no issues at all on a C5 (other than memory and processor run right on the edge of green according to the Hubitat Detailed info app). I don't have a very large z-wave mesh except for my most important device: the main thermostat which is used pretty much everywhere...
I'm considering not upgrading unless something happens to the C5, ie the C8 is my disaster recovery plan, but it seems like a such a waste.
You can run the migration and then if things are not working on the new hub you can just unplug and boot up the old hub. Then you can regroup and come up with a plan to try again.
With zigbee devices I've read that some may need to be re-paired after downgrading depending on if they communicated with the hub on the new mesh or not. Assuming this has something to do with the negotiated encryption key. My entire environment is pretty much zigbee (~80 devices; many of them Inovelli switches) so not sure what amount of effort that might require.
WAF would be extremely low if she came home from work and the automation was down again. It happened to me once before when a Sonoff outlet took down the zigbee radio. We had no idea how much the lighting automation did lol... All of our table lamps not controlled by inovelli switches are attached to plug-in zigbee dimmers with no other way to turn on/off other than to crawl under a table to manually press the button on the dimmers themselves.
Just a quick update here. I successfully migrated to my C8 pro because I have a need to leverage Z-wave LR. The process was remarkably smooth! Kudos to the HE team for coming up with a pretty much painless upgrade workflow. I followed this gameplan:
First, I disabled integrations. Specifically mine were:
Airplay Integration
Amazon Echo Skill
August Home
HCA App (an integration to my legacy home automation controller)
Homekit Bridge
Then I took a cloud backup and powered down my C5. After that, I placed the C8 nearby, connected up power and network and powered up. When the led turned green I followed the "Set Up your Hub" workflow at go.hubitat.com which took me through discovery, registration, a firmware upgrade, and the restore process itself.
After the restore completed and the hub was rebooted, I went over to settings and re-enabled the static IP (all my IP address info was filled in from the restore). Then I re-booted and began testing. I did notice that I had a "weak zigbee channel found" warning but was prepared for that since I was using channel 20 and had previously experienced no mesh issues. So I dismissed the alarm and quickly determined that my ~75 device zigbee mesh was running normally. Then I checked my small z-wave environment and determined it was also running normally. Finally, I re-enabled integrations. Several notes on this:
Airplay integration came back in its uninitialized state. So I allowed it to add addtional components. When that was complete, my selected configuration was still in place and all I had to do was re-enable the integration again.
The Amazon Echo Skill did not work until I went into the app and then pressed "Done". I was prepared for this ideosyncracy as well.
All other integrations worked immediately as soon as they were re-enabled.
Next, I pointed my mobile app over to the new hub. Documentation was a bit out of date here; the hub change capability is no longer in settings but rather on the "Local" page of the app's home screen. After the switchover, I re-enabled geo-location for my phone and everything worked fine. Since I was using the original IP address, local connections were working before I changed over but the switchover re-enabled cloud based connectivity.
Finally I jumped over to the hubitat website and transferred my subscriptions to the new hub. Then I reloaded my entitlements in settings -> backup/restore to re-enable my cloud backup subscription.
Now its all good. Hub performance is noticably better too. My final step will be to power down and switch over to PoE to see if that will be reliable. That will insure that the hub remains powered during any power outages since my network infrastructure is UPS backed. I have a Procet PT-PTC-AT for this purpose (which is one of the highly recommended C8 Pro PoE adaptors). If I experience z-wave reliability issues I'll go back to the power adaptor and then connect it to a mini ups.
Again, kudos to the HE team for a pretty much pain-free upgrade workflow. As an IT infrastructure architect, I know how difficult this can be...
