Thank you @ogiewon and all the other people who responded.
I disable HADB because I've had severe overload issues since upgrading to the C8 (an issue I've never seen on the C7.) The "offending" apps (looking at the hub logs after receiving the overload warning) are always HADB and Advanced Hue Bridge. So what I would do is to disable HADB before a restart if I remember, or otherwise disable the app as soon as the hub overload warning appears.
It is clear that I made the problem worse by disabling the app, causing a vicious circle of more devices being added (which I believe in itself is a process requiring extra system resources) and the more HA devices there are, the heavier the load on the hub.
I also got the impression. Almost as if, while the HE hub is rebooting, updates from the HA hub pile up, waiting for the HE hub to become available. The developers would obviously be able to tell if this is even a possibility.
The app is reporting the overload. (To be precise, the log shows the app as being the app using the most system recourses. Sometimes it is the HADB app; other times, it is the Advanced Hue Integration app. But these two apps always use substantially more resources than all other apps when the hub complains about excessive loads.)
OK, makes sense. If you ignore that warning and let the hub just go about its business, does it eventually go away?
I know it seems annoying, but really anything that uses any amount of processing or other hub resources at startup is going to stand out relative to the rest of the system. It may trip that warning, but it is just a coarse check and anything processing heavy at startup will get flagged.
It sounds like the HADB app or the Hue app may be doing that, but if both "quiet down" after some runtime and the system isn't burdened on an ongoing basis, then it is mostly innocuous. Whereas disabling HADB and having to clean up devices later is less innocuous.
The hub load remained an issue for the first few weeks after I migrated to the C8. I had terrible Z-wave issues for weeks, and Bobby diagnosed the severe hub load as the culprit. I, therefore, had to disable all apps and, one by one over a period of more than 2 weeks, re-enabled the apps to troubleshoot the issue.
I eventually managed to stabilize things to a large extent, as long as I didn't reboot the hub. I dread a hub reboot, but in a moment of weakness, I updated the hub firmware today and the severe overload warnings returned. I'm obviously over-sensitive to the overload issue after having the issues for many weeks.
I wouldn't say you're over-sensitive -- it sounds like you have had legitimate issues related to the severe hub load.
In that case, I'd encourage you to look for things on the HA side that you could potentially remove, similarly to what @Ken_Fraleigh mentioned. Can you tell which devices are creating the most events on the websocket connection from HA to HE?
No, the Hue bridge is only linked to the HE hub. I have considered moving the Hue lights to HA because of the overload issue described above, but that would complicate my automation. 99% of my automations are handled by webCoRE in HE.
I also get severe hub load right after a reboot, but it clears after a few minutes. This is the case even on my main hub that houses all my Z devices, but minimal apps. Basically nothing but Hub Mesh and a few other built ins. If it shows up but clears after the hub is up for 10 minutes or so, then I wouldn't sweat it.
What did you have to disable to help mitigate the impact of events from HA? I thought there were some that periodically updated that were causing some unneeded load. Any chance you could give pointers on what you found in case it would help @hendrec bring his hub load down?
I deleted the Sun app, Calendar, and weather app from HA and disabled my main Hue bridge. I am currently using HA for a MyQ garage door, one Hue bridge, 3 ATVs, 3 HPMinis, Litter Robot, Shark Vacuum, Roomba and Brava Jet, Cielo thermostat, a few TP-link plugs, a Yamaha receiver, Vizio TV, Sonos, and a HASS bridge for Homekit. I didn’t initially realize that the extra traffic would have to be filtered out on the HE side and had thrown caution to the wind since HA is running on Ubuntu on an i7 with 16 GB of ram and a 500GB ssd. After that revelation, I deleted everything that I wasn’t actually using. I should also mention that Hue bridge polling is disabled in CoCoHue and just using push updates from the eventstream.
This HADB integration, allows Home Assistant devices (many, not all) to be added to Hubitat, with bidirectional communications.
There is another integration that allows Hubitat devices to be added to Home Assistant with bidirectional communications.
So, you may need both integrations to achieve your goes, depending on what your requirements are.
If you'd like to use Hubitat as a Zigbee and Z-Wave controller, and then expose those devices to Home Assistant, you would use the integration that I linked above only. You would not need to use this HADB integration.
I am hoping to use HA dashboard and cameras on HA because of better hardware support but use all the devices on HE linked to HA dashboard because HA does have a much better looking dashboard if you know what I mean ...
Would this bridge or other link is what I should look into?
Thank you so much for explaining and information! ....
One last question, I also want to move my doorlock and garage door opener over to HA because I am told that it have Homekit support without the restriction and I wouldn't need to use Homebridge since HA have Homekit support.
