Shelly EM writes continuously on Events log

[Lorenzo]

The Shelly binding write on the event log file every change of power and voltage measured by my Shelly EM because voltage (than the measured power) continuosly fluctuates a few tenths of a volt to some volts. This means that my log files are full of power and voltage values. There’s a way to change this behavior?

Thanks

[rossko57]

Previous discussion.

Shelly Binding

ok, new DEV build fix for sensors#lastUpdate Watt updates are filtered, diff must be > 1W KW/h updates are filtered, diff must be > 0.05 kw/h (50W) Are the thresholds suitable? I want to prevent the logfile getting flooded by power updates, on the other side the threshold shouldn’t drop useful updates. Feedback welcome.

Recent changes, so the binding version you are using would be relevant.

[markus7017 (Markus Michels)]

@Lorenzo

The Shelly binding write on the event log file every change of power and voltage measured by my Shelly EM because voltage

that‘s true, but I can‘t change that. The channels get updated on each device message, there is no way to suspress logging each time, this is done by the OH framework. I already have a cache, which suspresses updates when the value has changed. I implemented a filter, which skipped minor updates with the result that LED devices with low consumption received no updages anymore. So…?

[Lorenzo]

So… only Shelly can help changing the firmware?

[markus7017 (Markus Michels)]

Nope, the OH framework does the logging

If you don‘t want an update every 15sec you could disable CoIoT for this thing. This results in updates every 60sec (if value has changed in between)

[markus7017 (Markus Michels)]

please use the regular Shelly Binding community thread so others benefit from the discussion or could make suggestions

[sloth0815 (Jonas Böhringer)]

I am having the same issue (as is everybody using Shelly switches I guess). With about 10 Shelly switches in my home the Openhab event log gets spammed with every minor power consumption change (even changes of 0.02 W are reported). Is there a way to reduce the logging (switching offColoT did not help) or even completely disable non-error logs?