Every time I see the sale banner I want to jump into the C-8 pro. But then I start to think why? My Z-Wave and Zigbee devices are really stable. I have isolated rules and radio's to one C-7 and then external integrations to a second C-7 using hub mesh to bring across those devices and services.
Only had one issue where after an update one of my most current rule machine rules just disappeared and most currently a Zigbee radio that went offline. But all in after building out all my automations I never hear a peep from the wife that something isn't working.
So with that said should I risk it and purchase the C-8 pro to use as the radios and rules Hubitat? I remember the migrations I have done in the past from C-4's to the C-7's. Looking for good pro's and cons and opinions.
I went from basically what you have now - 1 hub for rules and integrations, 1 for devices - to now single 8 Pro.
First, it is a pain. You can migrate the devices from one hub to the other (except for child devices - another pain), but the rules and integrations are actually worse to replicate. I ended up transferring from rules hub to 8 Pro, then manually re-adding the devices. Took me days.
Pros for combining - easier administration, no hub mesh that rarely (2 times for me) doesn't reconnect after a reboot.
Pros for not - It was (marginally) easier to swap a device.
Would I do it again?
Well, I did it at two locations.
Would I recommend it?
Only if you have a understanding wife that was at the other location while I did the dirty deeds.
I did the same upgrade a few months back. Main reason for me was because I was running low on memory, and wanted some of the "C-8 Pro only" features like being able to add Matter devices.
I moved from 4 C7s to 2 C8P last year and havenât regretted it. I have both Z radios on one (no apps) and all apps and LAN devices on the other with all radio devices meshed to it.
Iâd consider leaving your radio devices where they are on the C7 but take a database backup and put that on a new C8P so you have a hub with all your apps. Then delete all the apps from your C7. Then migrate/move all your LAN devices to the C8P as it can handle everything. Plus room to grow like HomeKit Controller, Matter, etc.
Regarding upgrading the hub: Since I only run one hub, I'm waiting for an entry level Hubitat (ie a non pro version) with a thread radio. Hopefully that is on the horizon.
ETA: and hopefully a Bluetooth option also!!
No, did not know about that option. Posted the exact quieries above in the screenshot with it's answers, so if someone is interested enough you can do it. I used it in incognito mode, and very rarely use it so presumably it's answer was not influenced by any personal history, so if someone is motivated enough you can find out.
Personally, I'm disgusted with AI
a. the half dozen or so times I've tried it, it has only been marginally useful once, and in that case it was an opinion that I have no way to verify (claimed a document had at least 4 different authors, in different sections. OK.)
b. the rising use of AI is stressing the grid where I live, and the utilities response is to raise the rates for residential customers, instead of making those who are causing the need for more capacity to pay for the buildout of that capacity
c. I've run into it with customer service and it is just plain stupid and so frustrating...it can NEVER solve the issue but is very good at not letting you get past it at all.
The Hubitat Elevation C-7 does not natively support Thread. Its radios are designed for Zigbee and Z-Wave, and while it can participate in Matter ecosystems, it relies on external Thread Border Routersâlike an Apple TV 4K, HomePod Mini, or certain Google/Amazon devicesâfor Thread-based device onboarding.
So if you're working with Thread devices, you'd need to:
Pair them first using a third-party Thread Border Router.
Then integrate them into Hubitat via Matter, assuming your C-7 is on a recent firmware version.
For full Thread supportâincluding direct commissioningâyouâd want to look at the Hubitat C-8, which has a Zigbee radio that can be switched to Thread mode (though not simultaneously).
If you're architecting a hybrid setup, you could mesh a C-7 for Zigbee/Z-Wave with a C-8 handling Thread and Matter. Want help sketching out that topology or simulating failover scenarios across hubs? Iâd love to dive into that with you.
Site Sources
Here are some reliable sources that confirm the Hubitat Elevation C-7 does not support Thread natively, but can participate in Matter ecosystems via external Thread Border Routers:
Hubitat community discussion on Thread explains that Thread support is expected only on the C-8, and even then, it shares a single 802.15.4 radio with Zigbee, making simultaneous use complex.
If you're mapping out a multi-hub topology or Matter-Thread integration strategy, I can help sketch out the architecture or simulate edge cases. Just say the word.
Show me the source for the C-8 that says the radio can be switch from Zigbee to Thread
Absolutely, Ronald. The Hubitat C-8âs radio flexibility is confirmed in several community discussions. Here's the most direct source:
âThe C-8 has a single Zigbee radio. The difference is that the C-8's radio can either be run in Zigbee mode, or be used as a Thread radio.â
This aligns with your architectural instinctsâHubitat designed the C-8 with a dual-purpose 802.15.4 radio, but it can only operate in one mode at a time. So if you switch it to Thread, youâd need another hub (like your C-7) to handle Zigbee.
If you're considering a hybrid setup with Thread on the C-8 and Zigbee on the C-7, I can help you simulate device routing, latency trade-offs, or even sketch out a dashboard topology. Just say the word.
C-8 here. 150+ assorted devices and protocols. Works very very well. C7 meshed with two overly communicative devices. I'm holding out for the next Hubitat iteration. Native border router and a fully mature implementation of the most recent version of ZWaveJS.
Yes it would be great to see a native border router in the Hubitat. As for the ZWaveJS played around with it on another platform. Seemed to work fine but I was only testing with two devices.
In the 
