Easy way to move devices from one hub to another without re-pairing all

🛎️ Get Help
1

Ok, I have a two c-7 hubs and a c-5 hub. Right now, all devices are on the c7 hub. What i would like to do is to split my devices between the hubs but share all inputs and outputs.

For example, on the c-5, install all my Zigbee bulbs and any plugs or switch adapters used for lighting. This hub for all lighting. Basically, I could turn off the z-wave radio on this hub and just use the Zigbee protocol on it. (One less radio to offer interference.)

The first c-7 hub, for all my other devices, like a temp sensors, presense sensors, door/window contact sensors, any power monitoring devices, etc.

Any and all ideas please.

I want to use the second c7 as a automatic fallback for the first c-7. Is this possible?

Oh, so far, I have stayed away from anything cloud based. (Must have local control 24/7. I want to learn more. I know Zigbee devices connect directly to hubitat so nothing extra was needed. I think z-wave is the same way so I may get some z-wave devices in the future. I am not sure if any wifi devices can connect directly to the hubitat hub.

"If"I pick up a matter device (plug or something) will it pair directly with hubitat? (After setting up plug in google) I guess I mean, to setup the wifi devices, I just use google home? Setup the device there, then get the code from google to add the wifi device to hubitat or is there more required hardware needed?

After setup, to control that matter device, would it need a internet connection to function or just my hubitat hub?

I thing I understand the API setups, but if I am reading it correctly, they all have to have an internet connection to work, even after setup. Is that correct? If that is so, I would prefer to use only directly parable devices to keep away from non-local control. Do not get me wrong, I do (at a later time) want to control my house from anywhere but that is not needed right now.

Thanks for the help everyone.
Paul

2

Unless you have a physical reason for separating the devices (like an outbuilding where the main hub's network can't reliably connect), you're probably just going to make things more complicated with no real benefit by splitting devices across multiple hubs.

I run two hubs, a C-8 Pro and a C-7, primarily because I bought the C-7 first and wanted to find a use for it when I upgraded to the C-8 Pro. I have all devices and most rules on the C-8 Pro, and cloud integrations running on the C-7. Looking at the memory and CPU use on the C-8 Pro, I probably don't need both, and I've been thinking of moving everything over to the C-8 Pro just to simplify things and have one less device running.

Zigbee and Z-Wave operate at different frequencies. I haven't heard of any issues with interference between the two networks.

It isn't possible to have the devices connected to two different Zigbee or Z-Wave controllers. If that's what you mean by fallback, then the answer is no. I think that with the Hub Protect service, you could take a backup from one C-7 and restore it onto the other C-7. So you could have a backup on hand in case the first one failed, but I'm not sure how you would set that up as an 'automatic' fallback.

There are some WiFi devices that can be controlled locally, but they are not 'connected' directly to the hub, the devices and the hub are both connected to your LAN.

For example, I have a few Sengled RGB bulbs that are WiFi, and my firewall is set up to block them from connecting to the internet. They needed internet access when I set them up with the Sengled app, but once connected to my WiFi, they work without internet using the Hubitat Sengled integration.

1 Like
3

@Alan_F
Thanks for the reply. I do not know where I saw the fallback thing, but I know I did not make it up. Lol I will look around and try to find it again.

As for the wifi devices, it is no big deal, I am doing my best to find Zigbee devices because of the ease of use with hubitat. I was just curious about the wifi devices. I had some old smart life wifi devices but I replaced them already.

A question about the integration, is it just sengeld or do all the api's actually work after setup when my Internet is down? I tried the tuta integration but it ended up not pretty so I just got rid of it.

I understand that some tuta devices are real chatty, that is the main reason why I was going to use multiple hubs. I was going to put the chatty devices into the c-5 app to keep the c-7 CPU load down, (to get rid of the lag/waiting time from button push to actual function.)

I hope that made more sense.

@kkossev
What do you think? Am I wasting my time trying to get the load down?

Just a FYI, I am in a c-7 running 2.4.0.143 and not 2.4.0.145 because when I updated, I could no longer see any new Zigbee devices to pair. I would try, start Zigbee pairing, but it just times out. So far, 143 is it for me.

My c-7 was getting laggy even though I set it up to reboot every other day. Then I tried daily reboot with no difference.

Well, thanks everyone. I have managed to get a few devices working correctly now.

I figured out (the most important part) if I look in the logs for errors and then focus on that device until the driver and parameters correct, then no more errors!

It is time consuming though, probably because I am making it that way.

Paul

1 Like
4

I just realized that when I said Sengled, I should have said Yeelight. I have both brands of bulbs, but it's the Yeelight ones that are Wi-Fi and using the built-in local integration. All of my Sengled bulbs are Zigbee.

If an integration is using a cloud API, then it won't work without Internet. As long as you stick with Zigbee or Z Wave devices, you don't have to worry about Internet.

1 Like
5

You probably have seen discussions about failover, but the fact remains there is no way to do that automatically.

@Alan_F is right. You could get up and running again quickly if you have the hub protect service, which gives you access to cloud backups (including hub radio data), and a spare already on hand.

2 Likes
6

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