Howto disable the sunrise plugin event-loggings

---

Hi all,
does someone know a possibility to disable the event-logging of the datetime and especially the sunrise plugins?
I might be a bit too sensitive, but I have the feeling, that they ‘spam’ a bit the logfile 😉
Regards Pedder

What do you mean in detail? I have them installed too but don’t see any spam.

Are your plugins set to debug?

Hi @SaxnPaule,
thanks for your quick reply 👍
When I open e. g. the homeduino plugin, I find an option to disable debugging, but this isn’t the case in the two mentioned ones.
So by their permant updating of all variables, which for sure in general makes sense for time-devices, they produce tonnes of events which, in my eyes, are needless to document.

Okay, you mean events not log entries.

As far es I understand, these events are used for the graph visualizations. Every change of a variable is kept as event. It’s no plugin thing. It’s a pimatic core feature. @mwittig please correct me if I’m wrong.

Yes correct, sorry for being unprecisely.
I just recognised that, as I wondered about the nearly 70tsd events after 24h running a fresh Pimatic …

At least you could reduce the events of the datetime plugin, depending on your use case.

Just use a refresh interval that is small enough to fit your requirements but as big as possible.

I’m with you and I already reduced that from 5sec. default to 10sec. 😊 and will reduce it more, …
… but the sunrise plugin produces much more events with it‘s hugh amount of variables and there I don‘t have that option.
I might be to critical on that, but I thought, let‘s give it a try by asking…

@saxnpaule said in Howto disable the sunrise plugin event-loggings:

As far es I understand, these events are used for the graph visualizations. Every change of a variable is kept as event. It’s no plugin thing. It’s a pimatic core feature. @mwittig please correct me if I’m wrong.

Correct. Events are also used to trigger the evaluation of rules. The Javascript runtime has been optimized to deal with high volumes of events, but still this might create a bottleneck, for example, if events get externalized, e.g. log events. Considering this, we should review the log levels assigned to the log events in question.

OK, understood the approach, which sounds meaningfull.
I, for example, used temperature-curves from different sites of the house to develop a simple sun-protection steering of the shutters, where it is very helpful
I also understood, that you think that the question itself isn’t that bad and may spend some thoughts on it.

Thanks!