When I got my C8-Pro, I consolidated down to a single hub. It has been running smoothly ever since. The extra memory and CPU horsepower really makes a difference, for my use-case. YMMV, of course.
Enjoy the new hub! 
1 Like
Yes the retirement of the C-7's is one of the patterns I was thinking of. My kids don't have any automation and I should donate the hubs to two of them to get started.
1 Like
Kids need help finding ways to dispose of disposable income. 
2 Likes
Wow that was fast shipping. It showed up this afternoon. Don't know when I will install, we have a family day thing this weekend and I haven't received my POE to USB C dongle yet.
Hopefully you’ve ordered one of the PoE splitters that were successfully tested in this thread. Otherwise, your Z-Wave radio may have issues.
2 Likes
Fully aware of that many of the USB C POE adapters don't handle surge voltage properly. Was so glad when I saw his post back in 2024. Even though my old hubs and PI's and 5G modems are on UCTRONIC's and work well for many years I ordered the PROCET on just to be safe. I also ordered some 90 degree adapters because I plan on mounting the C8 on the same wall as the C7's and I want the antenna's vertical when mounted.
Can't wait to start the migration.
3 Likes
Good choice! I also have used UCTRONICS PoE splitters for RPi’s, Lutron Caseta hub, Philips Hue hub, and C3, C4, C5, and C7 hubs. But the C8/C8Pro’s Z-Wave radio performed erratically with the UCTRONICS during my testing. Messages incurred a significant amount latency. Changing to the Procet PoE splitter resolved the issue immediately on my C8 and C8Pro hubs.
Have fun with the upgrade!
2 Likes
Got some time to work on the upgrade last night the migration was flawless, the migration backup of the radios and configuration produced a mirror image of the older C-7 and hub mesh between the two hubs worked fine.
Had one hickup with the Govee Integration which is on the "dev" hub and brought to the "home" hub via hub mesh. Only one of my Govee devices has to use the web api and that seemed to get stuck in a loop of pushing a set scene command to the govee servers. I disabled and re-enabled the govee device and it cleared up.
Here is some charts comparing the hubs you can really see the extra memory. As for CPU time will tell but the hub does boot faster. Right now the hub is on my bench with the POE adapter driving it. Over the weekend I will mount it where the old C-7 was.
3 Likes
Glad to see it went well for you, as I also ordered a C8-Pro on the sale (and just got it) to replace my C7... did that before I saw the Hubitat PSA on some users having issues migrating from older hubs with Zwave.
I need to study up on the migration procedures, I really haven't done the dive yet. My system is not as complicated as most, so my intent was to just replace the C7 with the C8 Pro after upgrading... I want to ultimately keep same ip address that I had on C7 address for the C8 pro to keep my other integrations the same. And I want to transfer my cloud backup license from C7 to C8 pro when the migration is done.
Assuming I can do that, I was planning on doing the migration first and stay on ZIP gateway. then if that looks good, cloud backup the C8 pro... and then try the zwave JS switchover. That was if it doesn't go well, I can fallback to zip from c8pro cloud back.
Not sure if there's any issue with that general plan, or if anyone has thoughts on that, but I'll spend some time in the docs and posts here before I get started.
I am like you except I gave my new hub a new IP address. Following the instructions here was easy. Migrating the Hub plans also worked well.
I just decommissioned the old C-7 this afternoon after everything was working well. As for the Z-Wave JS I am not going to touch that for right now. As long as things are working don't break them is my motto.
Yeah I was just studying the doc. I have a lot of homegrown integrations using maker api, and I set the Ip addresses in most of those programs/scripts etc to the Hub IP, and the hub ip is in my iot vlan.. and its the first IP address in that range there as the 'router' of the Iots.
My hub Ip is a dhcp reservation assigned address off my router, so not hard to change on that side, and not impossble to change in the maker device scripts/c code etc, but ...
I think since the procedure recommends disabling all the web/cloud (ip integrated apps ) first on the original hub, this approach is probably safe/fine. Ill keep reading.
1 Like
I successfully migrated this afternoon. Started my own thread for it but looking good right now. I did not jump to zwavejs.. yet. My mesh looks like its all zwave LR devices now (all direct routes to hub). So I think I'll stay put here for a while.
https://community.hubitat.com/t/successful-c7-to-c8pro-migration/156708?u=oktoko
4 Likes
I still have some Z-Wave battery devices that will mesh though switches and one switch that is very far from the hub that goes though a hallway switch. ZigBee is the same everything is mostly tied to the hub with only some non-repeating battery and bubs hanging off of outlets.
It's only been about 24 hours since i moved the hub off my bench to the final location where the old C-7 was. Something interesting also. The C-8 Pro is drawing less power that the C-7:
1 Like
