Hub process slowdown after TIME

gavincampbell · February 7, 2020, 6:37pm

Yup. There are a number of us on here. We just don’t make as much noise. Maybe we need a ‘1 Hub Club’ forum.

Ken_Fraleigh · February 7, 2020, 6:38pm

I created all of my Hue groups in Hue for better control with zigbee group messaging. I also switched to using CoCoHue instead of the built in app, because it lets you dim up and down Hue groups (which is very smooth) and import Hue scenes.

aaiyar · February 7, 2020, 6:38pm

I have two. One of them never needs to be rebooted. The other one starts showing slow down symptoms after ~2-3 weeks (one time it went 5 weeks). I just reboot the first hub when I reboot the second.

wayne2 · February 7, 2020, 6:38pm

To be clear, does this mean you have gone the multi-hub route with good results?

gavincampbell · February 7, 2020, 6:39pm

Oh no. Been a 1 hub guy since I started two years ago.

Ken_Fraleigh · February 7, 2020, 6:39pm

I was having the issues you are now. I added a hub and no issues since.

wayne2 · February 7, 2020, 6:41pm

I did the same, CoCo Hue. I just went and checked and I misspoke. I did the same thing. Created groups in Hue and import them with CoCoHue. Only thing I export from HE to Alexa is a handful of smart plugs. Also import some hue scenes with CoCoHue.

wayne2 · February 7, 2020, 6:42pm

Very cool. I like the way you think. I will do the same thing.

Ken_Fraleigh · February 7, 2020, 6:45pm

Check out the HubConnect thread. @csteele and @srwhite are amazingly helpful if you run into issues. There are even videos walking you through the installation that @csteele created.

wayne2 · February 7, 2020, 6:45pm

Awesome! Thanks. The community around HE is outstanding.

Ken_Fraleigh · February 7, 2020, 6:50pm

BTW, I want to thank you for your post about the Iris motion sensors on Ebay. I bought 10 from the seller you mentioned and they are all like new with new batteries and pull tabs in place. Working perfectly

wayne2 · February 7, 2020, 6:51pm

Excellent! You are certainly welcome.

csteele · February 7, 2020, 6:51pm

Multiple Hubs interconnected via HubConnect is intended to reduce specific issues. Baseline assumption is: no one should NEED more hubs.

BUT...

Many people have recognized that now that they have a wonderful Home Automation system, living without is horrifying.

They look at the Order + shipping time and they say to themselves, "I Need a Backup Hub. I can't wait a DAY for a replacement, let alone TWO days."

So.. it's not long before a hub is sitting on the shelf waiting for a really bad day to come along.

The next step, I presume, is the realization that "I'm going to have to re-pair and re-join devices if the Hub fails." and that leads to: "You know, If I split the devices between Two Hubs, only half will need to move, on that horrible day."

Now you're in HubConnect territory

wayne2 · February 7, 2020, 6:53pm

I just got a shiver up my spine with your scenarios. Next Hub will be ordered today.

I take it a backup and restore would not include the paired devices? ie you would still have to repair?

ogiewon · February 7, 2020, 6:55pm

I use two hubs, but do not use HubConnect at all (at least not yet .) I simply chose to use the second hub to handle tasks/automations that do not require the devices from the main hub. This has off-loaded a bunch of my custom code from the main hub and has greatly improved the overall performance. I do have a RM rule on my main hub make an HTTP call to the MakerAPI on the second hub to mirror my device presence, as this is used in an IFTTT routine for my Wyze Cams. I wanted to move IFTTT away from the main hub to see of it was possibly a source of hub instability. I don't believe IFTTT was a problem over a year later and the second hub is very stable!

TL/DR - HubConnect is great, but don't feel like you have to use it day one. If possible, compartmentalize what you can to a second hub in order to "Keep It Simple" and reduce complexity.

Ken_Fraleigh · February 7, 2020, 6:58pm

I believe you can restore zigbee devices to another hub, but not z-wave.

wayne2 · February 7, 2020, 7:00pm

Thank god for that. I am trying to stay Zigbee other than a small number of ZWave switches.

ogiewon · February 7, 2020, 7:02pm

You still would have to reset and re-pair every Zigbee device, however they would 'pop back into' their original device from the database restoration. And then all automations would still work without having to be edited.

Much simpler than Z-Wave.

wayne2 · February 7, 2020, 7:03pm

Yikes! But I can appreciate the benefit of popping back in place.

csteele · February 7, 2020, 7:06pm

We really need to have a "Hub Dissected" cartoon around here The hub has so many pieces and it's so tiny...

Zigbee Radio
ZWave Radio
Diagnostic Menu
Platform OS/Firmware
Built In Apps
Built In Drivers
Community Apps
Community Drivers
User Apps and Drivers

Each needs it's own Backup plan.

Some of it is downright easy. Some is painful.

An off-hub backup of the "DB" helps with 5-9
The Platform OS and Diagnostic Menu are downloaded from Hubitat on demand, thus covering 3 & 4

The problems, the pain, is in 1 and 2.

Zigbee is less painful, but you MUST walk to each device and 'click it' while the new hub is in pairing mode. Yes, the Zigbee device will 'reattach' using it's previous identity and will drop right back into all the Rules and Dashboards.

ZWave are going to need the same 'walk to and click' every device BUT they get a completely new identity and all the Rules etc will need to be touched too. I hope that Hubitat adds a "replace" feature to allow re-join to re-use the old identity. It's a part of the ZWave spec and I have used it on Staples Connect a half lifetime ago. That feature alone would bring parity to ZWave and Zigbee.