probably something to do with low memory, if I'm guessing correctly. At least that's my #1 problem
4 Likes
This exactly.
1 Like
Often these LAN based apps and drivers heavily load the hub. Ecobee seems to be problematic if set wrong, but it isn't the only one that loads the hub quite heavily.
Many people keep or buy an older hub around just for these intensive apps, and keep everything else like their Zigbee and Z-wave on the "main" hub. I use my old C5 just for this purpose, and for my old Iris V1 devices that I want to keep around. You can probably pick up a C5 or C7 for less than $50 going by Ebay pricing.
1 Like
That is quite true - it's the reason I run some of mine on a 2nd hub.
1 Like
Ok - I disabled the app and devices, and I installed the hub info app, though I am not quite sure how to use it - if memory is what needs to be tracked, how do I track that over time? (I am sure I can go read how somewhere, but if you know, I would appreciate it!). Before this issue, I would normally go months in between rebooting the hub. Free memory is currently 342592.
I will see how long it stays up, and report back. I appreciate the help!
This app can chart the memory since the last reboot but it does not persist after rebooting.
-- [RELEASE] Hub-a-Dashery app
If you want more historical data it gets more complicated.
1 Like
The downgrade was attempted. It got complicated as HE webcore did not downgrade nicely (at least there were lots of errors in log). The downgrade will be a backup approach and weekend project if needed. (I had feared it might not be possible. I am grateful to @jtp10181 suggesting to uninstall and restore WC form a backup).
Currently exploring another track which is to not use the ecobee suite helpers and recreate them as pistons. So far so good, so I am now letting it run to see if all stays up.
Do you know if the load on a C7/C8 would be similar if its devices are shared via Hub Mesh?
I am considering splitting things between a C8 and C7; however, webcore uses all of them to operate various pistons. This can mean although the C7 is, say, running ecoBee Suite, its devices would be shared via Hub Mesh to the C8. It could mean less on the C7, and only running ecoBee.
I guess I am not sure what you are asking exactly.
If you share a device, the shared hub (pretend it is your C8) will have much less load than the hub where the device is hosted (the C7) .
It doesn't matter which model (C5, C7, C8) hub is the host, and which is the shared hub. The idea is to split up the LAN devices, and the hub which has the rules/automations. The only exception to this might be the C8 Pro, which has more memory and a faster processor, that may be able to handle everything all in one hub, up to a point. But even then I think you are better off splitting things up.
I have been having almost daily hub lockups on my main hub and once on my backup hub. Mine are C8's but I have remote C7 and another C8 that are running fine. Been behind the scenes sharing those experiences with Hubitat staff and they are looking into it as an OS issue. I have questioned certain apps and suspect one as the heaviest load, but the strange thing is that app, is on my backup hub. The devices created by the app are then shared to the main hub via HubMesh. So in theory, as talked about above, it shouldn't be causing the issue since its on another hub. That hub did lock up once though so who knows... My main hub is rebooting while we speak.
I might employ the reboot for memory as mentioned above and see if that helps. Sucks when things don't run and I have to get into the diagnostic menu every day... Especially when I'm not home.
BTW I have Ecobee running on one of the remote hubs and have never had an issue with it.
This answered it, Thank you.
- the Hub hosting the app takes the load
- the hub receiving the shared devices has less load
I was concerned effectively both hubs would be hit with the same load.
This is great news to know there is an investigation, and ecoBee is working.
Thank you
1 Like
Hey Derek,
I'm trying to copy your rule. How do I Set hubName? Can't figure that part of the actions out.
1 Like
Howdy, you don’t need to, that bit of the rule is grabbing your hub name from the hub and storing it in a local variable. First time you run the rule it’ll populate.
Ok, I was able to figure out everything else on the rule and get it plugged in, but couldn't figure that part out... I just ran the rule and my hub is rebooting... let me see what it looks like when it comes back up.
also i tried to download and import your rule, but that didn't seem to work.
1 Like
that didn't work... hub rebooted cause i ran the rule, but still don't have the first line Set hubName under actions.
Strange, I just exported the rule from RM, I wrote the rule that way because I have multiple hubs and this meant I could just write it once.
You can just modify the local variable manually if you like.
ok, I'll try that... 
1 Like
I just checked and downloading and importing my rule from GitHub does work. I’m wondering if your browser didn’t save it as a raw text file.
