Migrating 3 hubs into a single C8 project

I know you've journeyed beyond the google home thing, but I've never been able to have >1 hub connected to Google. I have my C4 and all Google controlled devices meshed to my C4. Previous I tried to also add my C7 and it never worked

I pondered doing this, and there are mixed successes out there, enough to make me hold off. Certain zigbee devices not pairing, Z-wave issues. It'll probably get resolved at some point, but like you, my tinker time has been curtailed. Good luck to you

1 Like

I've always had only the one hub speak to Google Home. It was the middle man hub which managed all the meshed devices on the other two hubs. Worked fine for a while until recently.

After a few hours with a single C8 I'm probably gonna need the Pro. :rofl: It's hanging in there, but gets elevated/severe far too often for comfort.

The LIFX devices are the biggest culprits by a longshot. They top the list of busy % work, so I don't know what's going on there. If I can calm them down somehow, it may be manageable.

I see others in the forum have noticed LIFX bogging down the hub as well. Strips are the worst offenders due to creating 20-40 child devices, all refreshing at the same time. A workaround is to set the Strip device driver to LIFX Color unless you absolutely need HE to have access to each individual zone.

I would keep the C5 for the LIFX, other LAN integrations (Matter?) and for any Zigbee devices that doesn't play nice with the newer C8 Zigbee chipsets.

I have most of the LAN stuff on my C5, and it makes a big difference in how snappy the C8 (non-pro) feels, and the memory levels. Just have to hubmesh these devices back to the C8. It sure seems like it would be the same hit to memory by doing this, but somehow Hubmesh virtual device isn't as brutal to memory as an actual device on the hub.

1 Like

That was how I was set up before, with a dedicated LAN hub. The main reason I'm consolidating back to a 1 hub house is because HubMesh was becoming very cumbersome with so many devices, and all the back and forth... That and just being able to easily upgrade in the future in like, 30mins flat.

I know how that can be. Just be careful of bulbs. Zigbee ZLL 1.2 bulbs do not play nice with ZHA 1.2 devices (sensors and what not). ZLL 1.2 make very bad repeaters/messengers and can cause zigbee mesh issues. These bulbs should be isolated to their own network (Either using a hue bridge or another hubitat). The exception are Sengled bulbs as they do not repeat. Also 3.0 bulbs don't have this issue.

Glad you're getting things sorted though!!!

1 Like

Fo sho! I have my ZLL bulbs on a Hue Bridge, and everything else on the HE hub. I also have a bunch of non-repeating Sengled bulbs on the HE, and chose them specifically because they don't repeat.

1 Like

Edit: No sense in negotiating with limited processing power after all this work, so I'm ordering the Pro now. :star2:

Got the C-8 Pro already. And the migration only took 15 minutes. Could hardly believe it... Absolutely flawless! The house is quick and snappy and the hub is nowhere near capacity. Exactly what I was hoping for.

I have a 2300sq ft house, totally average, so having 1 single hub work without choking should be a benchmark.

I did have to rejoin all my Sengled ZLL bulbs. Earlier in the week I read up on the problem with legacy ZHA Zigbee devices. Somehow I managed to pair a couple Sengled contact sensors, but I'll have to replace the rest (not complaining, they've been a PIA from day one). I also have 4 Iris v2 sensors that I have to replace. Got almost 10 years out of em, not bad.

The replacements in the mail:

  • Ring v2 700 contact sensors: have been rock solid and original batteries have lasted 3 years so far.

  • 1 Thirdreality Zigbee contact sensor: trying it out

  • Zooz 800 ZSE18 motion sensors w/ LR: they have the option of USB power too, which'll be nice.

I have around 15 of those on my c8 pro... They're fantastic. Wish I could still get some.

You must have migrated them from a prior hub?

only about 5 of them. They pair fine with the c8 and c8 pro. I've factory reset a few recently as well. Now the V1's on the other hand will not pair with the C8 at all (there is a note on this). V2's? Shouldn't be a prob for you...

I can't get any of them to pair, but maybe I'm doing it wrong. I reset before each process: hold down the side button and insert battery. As soon as the light flashes blue, let go.

Then start inclusion on HE... It says "found a Zigbee device, initializing..." then the Iris does a repeating sequence of solid red --> flash green. And HE times out.

Same scenario on all 4 of them. I've tried pairing keys in clear, and I don't have any 3.0 repeaters. I have 3 of them that I migrated over from a C7, and they work fine. Just can't do a new pair...

I do have an old Iris 3210-L smart plug paired to the C-8 Pro, which also functions as a repeater... (Has a Z-Wave side too)

I wonder if that's causing issues with the Iris gen2 pairing... Will investigate tonight.

So you’re doing everything under one hub? do you run into any issues with it being slow or requiring any type of reboot? Are you also using rule machine?

C-8 Pro now. Yep, no slow issues or anything bogging it down. Probably have 30-40 Rule Machine rules going. Google Home, LIFX, Hue, and Lutron. Max busy % is like 11% or so from a LIFX strip.

Is their a place to see the process percentage.

Yes, under the Logs tab: you can view Device Stats or App Stats along the top menu.

This is the apps for instance. Some of this may be helped if I rewrite the rules a bit. I likely have a lot of unnecessary device interactions baked in. Still, plenty of overhead.

1 Like

That’s percent of busy is not useful unless you also look at the total busy time up above, it is a percentage of that. It’s also not the most accurate thing, mainly just to help troubleshoot.

Well it's definitely better than the 50-60% numbers I was seeing on the non-pro.