Info logs - How do I turn them off?

I have a simple automation which turns on a light (and turns it off after 3 minutes), when motion is detected.
Here is the logs for this:


Is there any way of turning off the logs for this app?

go into the each device and turn off the tick buttons for logging. I generally turn them all off in each device. Keeps my logs quiet for errors.

This is a log from the app. The flags are all turned off for the involved devices.

You can't turn that logging off currently.

That's what I thought!

Well, if the "infamous" resource leak has anything to do with the size or nature of the log, don't you think it would be a good idea if we were given the option of turning this entry to log off?

You would have to ask Hubitat that... :man_shrugging:

I imaging logging is ON by default in the Simple Automations app, as it is supposed to be simple as possible without a bunch of options to clutter everything up.

Personally I don't think the 20 or so events you posted over what looks like ~2 days is of any concern from a loading standpoint.

1 Like

Are you in favor of turning off the logs via a selectable option in the simple automation app?

It's difficult to know what is hammering the log, sometimes....

I have no strong feelings one way or the other.

I only use a few rules in Simple Automations, and they generate maybe 5-10 events/day for me. So it is nothing I'm really concerned about.

Would converting this into a RM4.0 rule make sense if logging is a concern? I think you can control what is logged there...

In general, I don't want Hubitat to do logging for me, unless I explicitly turn it on.
Unfortunately, it appears the simple automation does so by default.

It would be nice to be able to deactivate this logging. My simple rules never seem to have issues, yet they are constantly filling the logs. It might be only a few lines per simple rule, but once you have 25-30 of these simple rules logging, it does get cluttered.

I guess someone just needs to make a feature request to @bravenel then, and see if that makes sense to him. There is a danger of adding more and more togglable options to a "simple" app, as soon it is no longer "simple", but maybe this one will make the bar (?).

@bravenel Bruce:
The request here for your consideration, is to add an option in Simple Automation to turn on/off the logging that is by default on for that particular simple automation.
The benefit of this option is that it may reduce the logging that goes on, and would therefore increase the efficiency of the hub.

1 Like

Is that really true?

1 Like

I mean I guess it would have to be - technically. Whether it is a measurable or meaningful difference is another story.

Yeah - that's what I meant .....

It would be appalling if write operations to a log file measurably reduced hub function, so I cannot believe that happens.

1 Like

It's measurable if you are using Simple Automations extensively, (instead of Node Red, Rule Machine, or other approaches).
Many, many Simple Automations is the recommended direction, is it not?

In what way (I'm coming to this thread very late, so I might have missed it). But how has this decrease in efficiency due to writing to the logs been measured?

2 Likes

Sure you can measure how many events there are, but you can't really measure the impact the logging causes.

Let's say you have a BUNCH of Simple Automation rules, and get 100 events/hour. OK... So? Is that a meaningful impact on hub load? I would guess not, but I don't know.

Let's say your rules are really chatty and you get a 1000 events/hour. Ok... Is that too many / impact hub loading? I don't know...

That said I have no issue/problem if they make the logging optional/configurable. I like less things in my log too - I'm just not convinced that actually impacts hub performance.

2 Likes

Also want to add - I also have no issue if logging is made configurable.

Although I would be shocked if turning info logging off for Simple Automation rules impacted hub function in any measurable way.

BTW, I can see how turning debug logging on for a chatty (frequently used) z-wave device can impact efficiency ....

1 Like