I don't use RM anymore, and as I move automations over to node red, I remove the apps and any drivers from my hub.
If my hub get below 300K the response time interacting with the hub becomes noticeable. The zigbee radio doesn't always stop functioning but it has enough times.
Only thing I can suspect is some HW/SW variance between C4s and later. And at this point I just mitigate it as best I can.
And given the stability and increasing maturity I've seen with Zigbee2MQTT I don't know if I would invest in another HE hub if mine failed.
Mine is the NR dashboard too using the "chart" node. It's a bit more hastily thrown together than @aaiyar's. I just wanted a quick view but will probably tweak as I go along.
Interesting - I ditched my C4's after one died. I have not played around with Zigbee2MQTT but have been curious about it.. C4 definitely has more memory "constraints" thanks to the 64 bit jvm vs 32 bit on the C5/7's.
@wienog Did you ever list out the exact model numbers for Bryan? He is the Zwave guru for Hubitat, and can possibly fix the problem if he knows what model devices are failing here.
They also might be able to look at the internal hub logs and see if something sticks out, so if Bryan asks for your hub ID, be sure to get it to him.
I have a theory, since I don't own any expertise. I'm thinking the particular combination of different zigbee/zwave devices can have a big influence on performance, even outside of energy reporting or chatty devices.
I'd be curious to see a list of the devices you guy's have, to see how different it is to mine.
Hard to get a screenshot. But I can tell you the events that changed my hubs from being rebooted daily to almost never reboot:
Zigbee hub (C-5):
Removed custom drivers for zigbee devices
Moved all Xiaomi devices to the separate hub. I bring them in as virtual devices into Hubitat
Simplified my apps list
Zwave hub (C-5 at the time, lated migrated to a C-7):
Removed a couple custom drivers
Removed all ghost and stranded devices
Also, FWIW, I had at one point of time moved all my automations off the hub. I have since deliberately added a substantial amount back on a temporary basis to see if they were any faster if I eliminated processing elsewhere on the LAN. When I added them back, I rewrote rules to be more efficient (largely eliminating use of the *changed* trigger).
I don't see why HE can't use the 32 bit version since the base os is a linux variant???
Zigbee2MQTT is easy to setup, since your already running a linux system, IIRC. It runs on node. Plus it supports a much larger pool of Zigbee devices and if you find a device that is not supports there is a procedure for getting support added.
I could be wrong, but perhaps the base OS distribution for the C-4 is 64-bit. Whereas for the more recent models, it is 32-bit. And the JVM comes with the base OS.
I actually run a precompiled 32-bit application (i.e. a binary) in my 64-bit SBC, and setting it up was a PITA.
Yes, I moved all my Xiaomi devices (~80) to z2m in 2020. I bring them into Hubitat as virtual devices.
But I do have other zigbee devices on Hubitat; including ones that work very poorly on z2m (for eg. z2m doesn't support the SmartThings Arrival Sensor V4 very well, and doesn't support the V2 at all).
@Rxich
I'm using Node-RED for all my automations - this has eliminated the need for most HE apps.
My C5 Network hub seems to be rapidly declining in free memory but I am attributing that to custom drivers specifically the Flume driver at the moment.
I have a bunch of different devices (both old and new) including:
Zooz, SmartThings, Aeotec, GE, Bulldog, Inovelli, Ring, Homeseer for Z-Wave on my C-7. Apps include Groups and Scenes, Maker API & Homebridge
Iris, SmartThings/Samsung, Sengled, Centralite, RGBGenie and others for Zigbee on my C5 Zigbee hub. Apps include Groups and Scenes, Maker API & Homebridge
On my C5 Network hub - Lutron/Flume and some hubmesh devices shared from the other 2 hubs. Apps include Groups and Scenes, Maker API, Homebridge & Alexa.
In terms of hub performance, I have not had any of the "performance" based issues that many of you have had. In my installations for others, I have also not had any performance issues.
Like many of you, I tinker a lot with my own personal installation, and I try many things out personally, that I would never use at a client's site. I expect there to be issues with those things - that's why I try them out (usually) on a separate hub.
There are many drivers out there, and they are not all written well.
There are many incredibly usefull apps out there, that can kill you hub.
There are many ways to specify preferences that can destroy your hub.
(Just one example that we all know of is frequency of power reporting.)
However, for the overwhelming majority of people who just want something that works (and who don't need to upgrade their system every other month), Hubitat is just fine.
I do the same.. my home is my "dev" site well maybe "beta" site I do have to keep the family somewhat mollified. I have separate servers to test the latest stuff / apps etc but usually those get quickly incorporated into my home system to see how they function in the "real world". Also there is the basement which usually is "safe" from family HA angst but large enough for adequate testing.
For my clients and my sanity I absolutely try and keep things as close to a known baseline setup as possible with an emphasis on Hub resource reduction and ease of maintenance.
I frequently recommend a multi-hub configuration especially for "difficult" properties - older homes/signal unfriendly construction materials/expansive or weird layouts/large deployment of smart devices etc. Even though I know a single hub could theoretically work I've found the routing and management to be much improved..
Having read the first and last comment on this thread, I have obviously done extensive research... And the main comment I would add is that HA in general is a work in progress.... IMHO.... And a small number of (major) org's are approaching it from different angles.... some like Hubitat are approaching it from the angle of satisfying the developers who then supplement the offering to round out the experience for the general consumers here on the Community.
So for me, Hub performance atm...? The cost of a new HE hub is cheap enough when on special that you can take advantage of the savings to invest in the extra capacity, but only if you need it. I use my 3 hubs to split out my lighting, local and cloud integrations, with an additional HE hub for development / testing of devices and integrations.
And the main comment I would add is that HA in general is a work in progress.... IMHO.... And a small number of (major) org's are approaching it from different angles.... some like Hubitat are approaching it from the angle of satisfying the developers who then supplement the offering to round out the experience for the general consumers here on the Community.
