I've actually done that. Im on my third HUb , all have had the same issues.
Yep, I have always shut down the old hub and pulled power from it before begining the migration to the new hub. has not made any difference
If his radio was dead, all the devices would not be working.. He is having post migration mesh issues.. Short of sitting in his home with a zniffer, I'm not sure how else to troubleshoot..
2 Likes
Ok, understand your frustration.
I didn’t notice that you confirmed that you tried a reboot with the advanced “rebuild database” option selected.
1 Like
On the old hub the mesh seems fine. no weird delays, everything trigger like its supposed to.
I have an extra UZB7, I'm willing to convert if someone can point me into how to do that .
Haven't done one of those conversions in a long time.. Don't really remember how it's done.. I use the pre-made zniffers for normal mesh, and dev kits for mesh and LR zniffing..
I would say quite the opposite, if you had 3 different hubs that all didn't accept the migration, that suggests to me that the originating hub is not giving a good backup that can be successfully migrated.
If it were a C8 Pro issue, there would be nothing but post after post of people with migration issues. Granted there are a few, but not on the magnitude if this was an underlying issue with all hubs.
I would suggest that it is something unique to your setup or environment that may be causing this issue.
2 Likes
The Z-Wave chip is identical in firmware and hardware to the C8..
5 Likes
I know this wouldn't be the answer you would want, but what if you migrated everything but the Zwave radio.
Perform a full factory reset so everything is clean on the C8Pro. Restore everything but the Zwave Radio. Then once everything else is working remove the zwave devices one at a time from the C8 and add then include them to the C8Pro.
I know i had one heck of a time with my migration as well. Ultimately my problems centered around a backup problem that put my restored environment in a bad state. I don't exactly remember for sure what i ended up doing to work around it, but by the time i figure out the issue with the Jobs getting messed up i had already trashed my zwave radio and had to reload everything.
I think what I ended up doing was something like restoring the migration backup for the radios and then i used a regular backup(non migration local backup) to recover my installed rules and apps. It was a mess.
The key way to identify what i was experiencing was to look at the "Scheduled Jobs" tab on the "Logs" page. There were a ton of jobs that got hung up and were not running even though they were scheduled.
Here is the thread of my experience. Not sure how much it mimics what you are having though.
So After migration, still on Zip Gateway, this is what the Zwave Details look like (just started Zwave logingge)
That is what I thought. But then why is the problem suddenly there with the C8 Pro but when I go back to the Standard C8 in the same environment, everything is fine??
The only other devices on there are a handfull of Matter bulbs, those work fine when commanded from the device page. but since they motly rely on motion from Zwave motion sensors that havet been coming on line they don't get the message to trigger when needed.
I've done a full reset a few times. Just did one this morning. The zwave devices above are after that) Zwave logs have been blank since. I have NOT yet switched it to ZwaveJS. I guess I could now.
I actually don't have any rules on the C8pro. All the rules reside on a seperate Standard C8. The devices are on a seperate hub, and meshed to the "server" or apps hub .
Are you evaluating the C-8 Pro from the identical location as the C-8 after the mesh has settled for a few days and with C-8 turned off? Any deviation could gain significant different results.
Did you try this? Can’t hurt; might help.
After you do this on C8, THEN make backup for migration. (Ensure you are migrating sane database.)
1 Like
Very Close, actually the C8Pro is in a MORE open space than the standard C8. My hubs have all been wall mounted for at least four years.. I just didnt go the the effort to Mount the Pro until it was up and running. I have gone ahead and pulled the Standard C8 down and put the Pro in its place.
I usually do the advance rebuild anyime Iver done a reboot, But I dont know that I have ever specifically done it before doing a cloud backup. You are right, cant hurt to try.
Its been about 30 -45 min since I switched to ZwaveJS.
I just noticed that you are powering your C8 Pro through power over ethernet.
There have been lots of problems with various POE units.
I definitely suggest you use the Hubitat supplied power supply when you’re doing your migration and testing.
5 Likes
I just thought of that. Been using POE splitters for years without issue, and these are the ones there said to work better. Working on it. Not an easy change in this location.
Here are the Zwave details after switcih to ZwaveJS
Looking more promising than it has in a while.
Unless this clears up soon I def would get an extension cord and do a quick "just for testing, honey, I know I can't have an extension cord across the living room" run to the C8-Pro w/the stock power supply just to kill that variable dead. 
I live in an M. Night Shamylan movie. I can pull this off during the day. but once the sun goes down.. theres big Red X's on the door..
2 Likes
Keeping in mind that he switched to JS after migration and re-interviews still have to happen when the rest of the devices come online..
1 Like
Migration was about 11:30 CDT. power switch was about 10- 15 min ago.
Clarification. switch to Zwave JS was about 1130. Migration was about 1000,
About an hour in from the power switch and this is where it stands. Look like most if not all main powered devices have checked in,in cluding the LR devices that have been problem children this whole time. Now it seems like it s waiting for all the battery powered stuf to wake up from thei nappies and check in . Wich there was an easier way to force that.
