@gopher.ny I'm having some odd mesh issues after my migration.
I migrated my C7 hub to my new C8 hub (it took a second pass at restoring the backups, as the first one failed). After migrating (the old hub was unplugged prior to staring the migration), I renamed the new hub to the same name--"RHub1"--the old one had.
I also have a second hub (still a C7) called "RHub2" (this only has apps, etc. on it).
After that, things mostly seem to be working (things seemed to restore and work properly on RHub1).
However, I did have to use the function on RHub2 to restore the mesh from the original RHub1. And, initially I thought that seemed to be working properly. But...
The first issue is that I now show two hubs with the same name in the list of meshed hubs on RHub2 (the list shows "RHub1" and "RHub1").
Also, the meshed devices on RHub2 no longer seem to "promptly" reflect their updated state (when they change states, it seems to either wait until the next sync or it requires a manual mesh sync to get RHub2 showing the correct state). Previously, this seemed to be nearly immediate.
I have (at least) one RHub1 device that now wants to show up as "OFFLINE" (disabled) on RHub2. It is perfectly fine on RHub1. Oddly, it shows up under "Available on RHub1" TWICE on the Mesh Settings for RHub2--even though it was previously linked, and working. I even managed (somehow) to get it to temporarily show up properly on RHub2--but it's currently messed up. Note that this device does have a child (but it is not unique in that regard).
Any ideas how to clean up the duplicate hubs (the "old" C7 RHub1 and the "new" C8 RHub1 both seem to be meshed with RHub2)--and how to fix that device that isn't staying properly mapped?
Is the C7 that you migrated from still up and running? Names shouldn't matter, but it's agood to rename the old hub to avoid the confusion.
What are the options in the Source hub dropdown on the Settings - Hub mesh - Update tab? Please rename the old hub before checking and give it a few minutes to propagate the new name through hub mesh.
Can you boot the hub with two RHub1 entries? The poor thing is all confused.
I suspect that once rebooted, it will show RHub1 and a hub id in the list instead of two RHub1 entries.
@gopher.ny - I renamed RHub1 to RHub1n and rebooted it.
I restored RHub2 from prior to migrating RHub1. Then, I had to "refresh" the hubs on both sides to make them appear in each other's lists. Then, I migrated the "Unknown" hub with the old HubId to "RHub1n".
Now, we'll see how things work for a bit....
Is there any issue at some point in renaming "RHub1n" back to "RHub1" (on the new C8 hub)? Any tricks to doing that now?
I had to do that with around 50 devices (every device that was shared) after migrating to the new hub. On thing that I learned- disable hub mesh on the device you are replacing prior to the swap. I ended up with some very strange results before figuring that out. Other than that, the swap devices app worked amazingly well.
I had already restored the "app" hub to before the migration and did the huh mesh migration again. This time, leaving the new C8 "radio" hub with a different name then the old C7.
The hub mesh is now seeming to work properly and I don't have the screwed up light and child device. Success!!
Will things get confused now if I change the new C8 hub to have the same name as my old (replaced) C7?
I have a similar issue. I have two C-7 hubs. Called Home1 and Home2. Home2 was migrated to a C-8 and now every single meshed item on Home2 is flagged as offline in the mesh. Is there a quick way to restore functionality?
