Is it worth upgrading from a C-7 to C8 Pro

So many issues around the c8 hub. No thank you..

C8 is fine, but there are some issues w/the migrating from existing hubs to the C8-Pro that do need to be cleared up. If a friend were buying their first hub (doesn't need migration) the C8-Pro would be my first recommentation/choice for them. :slight_smile:

3 Likes

The Pro migration was not fun for me out at the tip of spear, but it appears they've got it fixed now for everyone.

Yet again here, I learned the hard way that life at the bleeding edge has risks :sweat_smile:

But my migration finally went smoothly last night, so I'm pretty sure I'm back in a good spot.

The only consistent issue for some folks unique to the C8 are zigbee related, but that seems like growing pains with the new Zigbee chip. Price of progress, I guess. Most of us have figured out a way to handle it via radio tweaks and/or zigbee device replacement.

But I can absolutely confirm that the Pro is significantly snappier & responsive -- that's a welcome win, and well worth it for me.

1 Like

I have 4 production hubs separated by radio/protocol and with the release of the C8 Pro I will be changing that. My C7 "coordinator" hub that is radio-less and runs most of my apps and rules was always struggling with memory and I would have to reboot it between 10-14 days. I just upgraded it to a C8 Pro last night and have to agree it is much snappier and responsive than the C7. Pico button presses and motion activated rules are much faster than before.

I will likely purchase another C-8 Pro and consolidate my 2 separate C7 Zigbee and Zwave radio hubs into one. These hubs don't run any apps or rules currently so radio only. Then there are my LAN apps on a different hub that seem to be totally happy on the C7.

Now I need to figure out what to do with the C-8 hub I purchased last year that I never setup. Opened box but I never powered it.

1 Like

Speed of rule activation is important from motion trigger to lights on. I’d love someone to do some actual before upgrade/after upgrade timings using the events to prove whether rules and actions are processed faster.

Something seeming faster/snappier could just be the placebo effect. The hub booting so much faster is irrelevant as I’d be hoping not do so too often (other than during update, the need to reboot is indicative of an issue)

1 Like

I have noted that every "little thing" about the UI seems faster - saving new Driver code, saving a Rule, etc.

Additionally, the time required for the nightly backup, which had been averaging 69 seconds from command to file save on the C-7, has been 30 and 34 seconds the first two nights with the C-8 Pro.

3 Likes

I have 4 hubs here. One hub, (C8) houses most of the z-wave and a large amount of ZigBee - 372 total devices - and WebCoRE with north of 75 pistons.

The difference in the C8 pro is HUGE for me. Not only does it reboot faster but the devices page loads much, much quicker and on and on.

I've only had it running for about 24 hours, and maybe I'm excited and hopeful about this hub, but my automations seem like they operate much snappier. I'll know more as time goes on, but I am very happy with the updates here. Also, as I look at my memory and CPU stats the numbers are extremely improved.

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.