CalDAV Binding spamming log while event is active

Hey,

I am completely new to openHAB and this forum, hope I don’t fail too hard for my first topic.

I use openHAB 2.5.5 Release Build on a Raspberry PI 3+ with openHABian.
I configured my Garbage Calendar as a Google Cal and somehow my log gets spammed while an event is active (my local garbage company provided events from 6am to 4pm for the day of collection).

I installed calDAV Personal and Command Binding, but doesn’t use Command at all, if it matters.

I check once a day via cron if there is an event next day and send a message via telegram bot and I have the items in a frame in my Basic UI.

My caldavio.cfg:

caldavio:Muellkalender:url=https://www.google.com/calendar/dav/.../events
caldavio:Muellkalender:username=user
caldavio:Muellkalender:password=password
caldavio:Muellkalender:reloadInterval=60
caldavio:Muellkalender:preloadTime=20160
caldavio:Muellkalender:disableCertificateVerification=true

caldavPersonal.cfg:

caldavPersonal:usedCalendars=Muellkalender

Items (same config for Event 2 and 3):

String      CalDAV_Muell_1       "1. [%s]"                          <calendar>    { caldavPersonal="calendar:Muellkalender type:EVENT eventNr:1 value:NAME" }

DateTime    CalDAV_Muell_1_Date  "Datum der Abholung [%1$td.%1$tm.%1$tY]"    <calendar>    { caldavPersonal="calendar:Muellkalender type:EVENT eventNr:1 value:START" }

My “problem”:
While an event is active it spams my openhab.log like twice every minute, starting from 6am til 4pm, here is the end:

2020-06-24 15:57:17.486 [INFO ] [nhab.io.caldav.internal.job.EventJob] - event BEGIN for: a6c47ca51c38e4c2d7ee617788ad2a32(Abfuhrtermin Biomüllabfuhr am 24.06.2020@24.06.2020/06:00-24.06.2020/16:00)

2020-06-24 15:58:09.185 [INFO ] [nhab.io.caldav.internal.job.EventJob] - event BEGIN for: ea385c8cea07573991e7bf8ccb97663b(Abfuhrtermin Restmüll am 24.06.2020@24.06.2020/06:00-24.06.2020/16:00)

2020-06-24 15:58:17.111 [INFO ] [nhab.io.caldav.internal.job.EventJob] - event BEGIN for: a6c47ca51c38e4c2d7ee617788ad2a32(Abfuhrtermin Biomüllabfuhr am 24.06.2020@24.06.2020/06:00-24.06.2020/16:00)

2020-06-24 15:59:09.112 [INFO ] [nhab.io.caldav.internal.job.EventJob] - event BEGIN for: ea385c8cea07573991e7bf8ccb97663b(Abfuhrtermin Restmüll am 24.06.2020@24.06.2020/06:00-24.06.2020/16:00)

2020-06-24 15:59:17.064 [INFO ] [nhab.io.caldav.internal.job.EventJob] - event BEGIN for: a6c47ca51c38e4c2d7ee617788ad2a32(Abfuhrtermin Biomüllabfuhr am 24.06.2020@24.06.2020/06:00-24.06.2020/16:00)

2020-06-24 16:00:00.003 [INFO ] [nhab.io.caldav.internal.job.EventJob] - event END for: a6c47ca51c38e4c2d7ee617788ad2a32(Abfuhrtermin Biomüllabfuhr am 24.06.2020@24.06.2020/06:00-24.06.2020/16:00)

2020-06-24 16:00:00.005 [INFO ] [nhab.io.caldav.internal.job.EventJob] - event END for: ea385c8cea07573991e7bf8ccb97663b(Abfuhrtermin Restmüll am 24.06.2020@24.06.2020/06:00-24.06.2020/16:00)

My question: is this normal or expected behaviour?
If not where is the culprit?

Thanks for your help!
Lukas

Normal, though an argument could be made that these should have been DEBUGs instead of INFOs.
Just raise the logging level to make them go away.

As an aside, this binding is going away with the advent of OH3 anyway, so you should look into switching to another calendar binding.

1 Like

Thanks for this information.
So CalDAV is a compatible V1-Addon correct?

The only other binding I found is iCalendar-Binding which is unfortunately lacking my needs because there are up to 3 types of garbage-collection-events per day … maybe I open an issue and try to extend it :slight_smile:

Are there any others I missed (and should I open an additional thread for this question, because it is drifting away from original topic)?

Not sure what you mean by “compatible”. But yes, CalDAV is an OH1 addon.

This is the one I was thinking of. So yeah, if you can do the work, extending it is a possible option.

Not sure what you mean by “compatible”. But yes, CalDAV is an OH1 addon.

I found the wiki/github pages about OH1 Addons after my post :slight_smile:

This is the one I was thinking of. So yeah, if you can do the work, extending it is a possible option.

Alright I’ll look into it and create an issue for it…not sure if it would be better to migrate the old addon or to extend the existing one.