It is configurable. Mine is happening around 2:15 so all is good.
1 Like
If you have the freememory logged somewhere I would use a value well above where it flattens out and may cause issues. I just realized some rules did not trigger the last few days before I noticed the (too) low freememory. It probably depends more on what is running on your hub that anything else. I now know I need to check it after I make changes to my setup.
2 Likes
140000? My hub moves very slow at under 250000, although I do have in excess of 120 devices
1 Like
I have around 180 physical devices, 25 or so virtual and my hub has run fine as low as 90k...I usually hover around 180k
And thus the crux of the issue...
If there were a single magic number at which it stops behaving, Hubitat would likely just automatically reboot the hub at that point. But there is no "1 right setting" for low memory.
That said, I very strongly wish that Hubitat could figure out a way to watchdog hub functionality and performance and do proactive reboots in-box without us having to cobble together our own fail safe rules.
In my few years with Hubitat every Hubtat hub I've had will stop working, or get so sluggish it is a moot point/distinction, at some point thus requiring a reboot. Usually I can go a month or more, sometimes not.
I still think the system should be able to do that for itself. They've made their problem my problem, and I want it to go back to being their problem. 
EDIT: Adder - I still love Hubitat! Still use it. Plan to keep using it. This isn't a HUGE problem to me or anything, just a rambling thought of what would happen in a perfect world to me.
11 Likes
I only regret, that I have but one like to give to this post.
I don't notice anyone from Hubitat on this thread. How do we get them to take notice and do something about this?
I appreciate all the suggestions, but I'm not inclined to mark anything as a solution. These are all workarounds; the solution needs to come from Hubitat.
Probably because it's been discussed to death with various solutions due to every system being different with a different config for each. It could be caused by a third party integration you're using or a non certified device (not on the compatibility list) etc.... You could put in for a support ticket at support.hubitat.com or tag the support team.
3 Likes
