Have seen several of these posts, none seem to contain an answer.
I've tried a few times. I've done a full reset, I've done the shutdown, unplug/plug-in. I've tried recreating the backup on the old. I've made sure both are on the same version -2.3.9.201. I've manually reset the zwave and zigbee radios on the new hub. At a total loss. I've done this in the past from c-7 to c-8... so I can get it to work, but not today.... Anyone?
Where did you purchase the C8-Pro - in some cases Amazon will ship used product, in spite of HE asking them repeatedly not to. You might have gotten a bad hub that someone else returned.
You can create a warranty case for HE staff to investigate/resolve.
purchased direct from HE.
Regardless, given the things you've tried you may have just "won the wrong lottery" and have a HW issue, so I'd create the warranty case.
1 Like
Well look at that... after the 3rd "successful" migration backup on the original, and the following restore it seems to have gotten past that point... zigbee isn't working, but I'll chase that with channel/power changes first... thx for the Sunday assist!
2 Likes
Part of happy ending is better than none. 
On the C8 generally the recommended channel is 25, and I keep power at 8:00 or at most 12 to start with.
1 Like
Really? I randomed ch25, so that lucky, but what's the logic in lowering the power level rather than raising it when signal strength is weak (according to notification)?
I'm just curious,... and always up for learnin'.
I had to reset the zigbee devices and re-add them, but didn't remove first from the hub, so they seem to be healed. Thx again for the nudges.
The message is a bit generic unfortunately, and really meant to be ignored if you're on a hub and not having problems. You're on the right channel and I'd stick in the power range I mentioned and see how things go.
This is a huge oversimplification, but more power means more "noise" overall-- sure, it can potentially travel farther (and that's usually all folks think about), but that increased noise also makes it harder for the hub to hear responses coming back in.
Lower radio power helps clear that noise spectrum across the board, but it's then dependent on having a strong mesh that can carry the water getting message traffic back-&-forth.
My radio's at 4 -- any higher, and I get zigbee issues. Heck, I'd try 2 if they offered it. But I have a very robust mesh of ZB3.0-only repeaters that shoulder the traffic workload.
ETA -- Like all things, YMMV... Some folks here are happily hummin' along at 16+. But lowering radio power is often a helpful step in improving/fixing zigbee network issues. It's not a silver bullet, but it often helps.
4 Likes
I would add, that lowering the power forces your devices to go through repeaters instead of direct to hub.
For one, the hub can only directly talk to a limited number of devices, (I think it is 32?). Because of that, you have to have repeaters in the system.
My understanding (maybe I am a bit wrong here) also is that the repeaters act like a cache of sorts. They are much better suited to distribute the messages than the hub itself, especially in a busy environment.
In theory, you should be relying on the repeaters to do the heavy lifting, and the hub just talks to the first level of repeaters. In reality, things do what they want to do, we can just try to encourage good behavior through power levels, a strong mesh, and so on.
4 Likes
Thanks all! Great explanations, I've learned something new.
1 Like
Looking for part 2 on the Zigbee issues resolution. That is the only thing preventing me from going PRO. Although maybe my collection of 5 hubs also has something to do with not migrating. That and running out of places to hide the hubs so they don't disturb my wife's feng shui
1 Like
I think she's more concerned about the socks you drop all over the house. 
I don't think there is/will be a "one ring to rule them all" solution. Many folks don't have issues, some have had minor issues, and others moderate to major. Fixes have been mixed (increase power, reduce power, change channel, keep channel, replace some devices, add some devices, move some devices to a different hub, etc.). A lot of YMMV...
I'd send your wife on month-long cruise, and while she's gone do a migration and see what happens. (I'm only partly joking.)
1 Like
In case I wasn't totally clear on my 'fix'. I've only got a few zigbee devices, 5 atm. One 'migrated' on its own, 4 (two battery powered temp sensors, one chinese relay of no particular brand or quality, and one generic on/off plug puck of dubious lineage). Those all came back with a device 'factory reset' and then just re-adding them to the new hub where they were found and linked the existing device just fine. Due to the small number of devices it wasn't too bad.
The sketchy part was the migration backup didn't report any errors and said it was successful, but it wasn't until I redid the backup two more times that the restore would work. So it MAY be more linked to the migration backup integrity rather than other black magic. it may make sense to allow local saves and restores of migration backups. more reliable imo. Requiring cloud backup/restore on a device thats strongly selling as 'local, not cloud' that's an odd direction to head.
Of coarse I don't know what I'm talking about and some other part of the random on/off'in and poke this and that might have been the true fix. Just documenting in case it helps others!
1 Like
Given the fact that the hub runs local for anything except integrations that I may choose to add that rely on the cloud, I can forgive them for using the cloud for the migration/radio-incuded backups. 
2 Likes
