Of course, as you know, we hove No (0) logging tools whatsoever, so we have no way of knowing what causes an overload for the hub.
However, I would assume that any decrease to the amount of automatic logging, is by definition, more efficient. How much more? your mileage will vary.
While not testable with Simple Automation, this is possible to test by creating a "simple automation" in rule machine. And then repeating that automation for 1000 executions per hr with or without logging turned on.
Yeah. That might be fun to do... If I only I had a development hub... Oh wait, I do. I might graph this out just to see what it looks like on a completely empty hub other than the text logic.
Would be fun to drive the hub into the ground for testing purposes anyway.
Much ado about nothing. There are log filters available for a reason. If you don't like the logs, don't look at them.
I can attest to the fact that I have a zillion things logging on my production hub with 250+ devices, 100+ automations, and there is no observable impact of all of the logging. Also, for most of the past few months I've had extensive Z-Wave diagnostic logs running constantly (left to the reader to guess why), and I've got 85 very active Z-Wave devices. So I probably easily have 10x the logging going on of any user, and there is no discernible performance impact. I think I'd notice...
The latest release includes the option to turn off logging in Simple Automation Rule.
Thank you for that!
I am very unscientifically testing the impact of disabling logging. My hub will slow to a crawl if I don't reboot it every night (325 devices, 35 apps + many children). I suspect logging is not the cause of the slow down, but that it adds to the others. I figure it is one less thing it will have to do...
I am looking forward to see how the hub "feels" after I disabled as much logging as I can.
Then later I will try something else to see if it also helps. Not sure what yet though!
I really, really like all that I can do with this hub, so I feel it is worth the time and effort. (Though my wife might say I spend way too much time tweaking things, adding new sensors, new rules, etc... Okay, she does say that...)
@bravenel
I just wanted to thank you for doing that (even though, as you and others wrote) it probably won't make any significant difference.
It's a real strength of the Hubitat that you listen to users!
Ha! I don't know if it will help or not, but something like this change takes so little effort, that it would be just stupid not to provide the feature if you think it might help.
I remember how with my former "smart" automation system provider, that expecting a bug to be fixed, let alone a feature added, was just a misplaced expectation. It was truly discouraging that they'd do an update and break things that had worked, and then never fix it even when spotted and reported right away. We aim not to be like that.
@bravenel as this was added for the rest of the apps could it be added to hub link?
This is just a turn ON/ OFF.
Sure. Will look into it.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.