Great post with fantastic insights. Thanks.
For zwave can you take the stick and move it to the new hub and keep the zwave info? Assuming the old and new hubs both have zwave sticks.
Yes.
If you have the external ZStick. US ZWave frequency hub buyers don't get an external stick. But if you do, yes, it can be moved, making it even easier than Zigbee. 
1 Like
US C3/C4 hub customers can move their combination Zigbee/Z-Wave usb stick to a new hub, making the process very simple. Even going from a C3/C4 to a C5 with an OTG cable, I believe.
So, in theory, one could buy a C5 and immediately add a HUSBZB-1 USB Stick to essentially give them a 'movable' Zigbee/Z-Wave radio. Basically, the USB Radio stick from a C3/C4 using the C5 Hub for CPU, Memory, and Network.
5 Likes
Yes, also quite true.
Which is probably why Hubitat keeps the Feature Request to add migration tools a ways down the list. 
So we can use an OTG cable for our C5's?? That is cool. Maybe that is something HE should include with the packaging.
I believe they do when shipping the hub to countries that require an external z-wave usb radio.
3 Likes
I think if I had know this was possible when I first started, I would have used an external Zwave stick. That would have given me the opportunity to back up the stick, move to a new hub if necessary etc.
1 Like
My C5 is my controller hub right now so all good. Just ordered an otg cable to mess around with.
Thought I would post this here. My hub slows down about once a month. It happened again yesterday and support basically narrowed it down to the Chromecast beta app and asked me to disable it.
I did for the time being but I'm going to be lost without it!
I would just schedule a reboot every couple weeks. You can have Rule Machine do it for you.
Yeah I probably should. I'll run without the Chromecast app for a bit just to test and help support out by seeing if that fixes my hub slowdowns.
I'm using the Rootn Tootn Rebootn app - my main and second floor C4 hubs have lately been rebooting nightly for some reason. My C5 controller hub (with no zigbee/zwave active) has been running fine.
I like that it reboots when it "senses" hub issues.. that way it happens when needed. I guess the only drawback would be if it did so during a critical rule/trigger time. I do send an alert during each hub (re)start to let me know the hubs have rebooted.
1 Like
FWiTW I had significant hub slowdown consistently, I think it was due to a bad zwave radio as documented here Inovelli Red Series. I reset the radio and removed all zwave device as the zwave radio won't pair anything now. So long story short, the hub is faster now and has not exhibited the slowdown.
3 Likes
As a follow up there is no question, zwave went bad on the hub, the new hub is working properly and not slowing down.
8 Likes
Back into hub slowdown mode even with z-wave working properly. Going to try the 2 hub solution.
What's your current number/config of devices?
~120 devices split between iris motion sensors, iris smart plugs, sengled contact sensors, 2 hue hubs (only import groups), 1 Lutron hub, 5 Pico remotes, 5 AVRs, 2 harmony hubs, 3 hue motion sensors, 8 Alexa devices, 6 Inovelli red dimmers.
Takes 24 hours to slow down substantially and then becomes unusable by 36 hours. Reboot and hub is fast again. Sure feels like java GC to me.
So how about just schedule a daily automatic reboot for now? Eventually they’ll get to the bottom of the issue, but for now this seems like a reasonable solution that will address most users that are experiencing slowdowns over time.
4 Likes
I have read that is not recommended. Seems the dual hub is the preferred solution.
