Icalendar Openhab3 Problems

After installation of the Bindung, the Service will not be go to online.

2021-02-12 18:01:46.387 [DEBUG] [ar.internal.handler.ICalendarHandler] - The calendar is currently offline as no local copy exists. It will go online as soon as a valid valid calendar is retrieved.
2021-02-12 18:01:46.387 [DEBUG] [g.icalendar.internal.handler.PullJob] - InterruptedException message is: null
2021-02-12 18:02:34.728 [WARN ] [g.icalendar.internal.handler.PullJob] - Download of calendar was interrupted.
2021-02-12 18:02:34.728 [DEBUG] [ar.internal.handler.ICalendarHandler] - The calendar is currently offline as no local copy exists. It will go online as soon as a valid valid calendar is retrieved.
2021-02-12 18:02:34.730 [DEBUG] [g.icalendar.internal.handler.PullJob] - InterruptedException message is: null
2021-02-12 18:03:34.730 [WARN ] [g.icalendar.internal.handler.PullJob] - Download of calendar timed out (waited too long for headers).
2021-02-12 18:03:34.731 [DEBUG] [g.icalendar.internal.handler.PullJob] - TimeoutException message is: null

Download from google via browser is o.k, any idear?

1 Like

Same problem here with nextcloud (owndrive.com).

1 Like

Why do you deliver something like that? I have tested the binding with different services, small ones work.
An old way via JS:[script] is no longer supported, so no transition to the new version is possible, where was tested here before delivering this?

okay. on my rasp I’ve also installed pi-hole. After uninstall it, it worked quite perfect.

I don’t use pi-hole. Still not working.

Try to download the calendar using wget/curl on the device openhab running. There you might get more information. You could also increase the general loglevel as the framework’s http client is used.

oh no. The deinstallation of pi-hole hasn’t really helped. The problem came back.
Downloading with curl works perfect. There are no warn messages. Also -v or -i doesn’t give any hint.

I also changed the global log level to Logger level=“DEBUG” name=“org.openhab”/> and Logger
level=“ALL” name=“org.openhab.binding.icalendar”/>, but the only information is still
2021-02-27 13:17:25.791 [WARN ] [g.icalendar.internal.handler.PullJob] - Download of calendar timed out (waited too long for headers).
2021-02-27 13:17:25.794 [DEBUG] [g.icalendar.internal.handler.PullJob] - TimeoutException message is: null
Any other ideas?

If only icalendar logs - you surely did not have increased the log level properly, so there must be an error in your configuration. OpenHAB logs really much in DEBUG!

Please post your logging config completely. Alternatively, you could set the log level via openhab-cli.

Thank you for answering so fast.
I’ve just changed again my /var/lib/openhab/etc/log4j2.xml. I will quote here only the Loggers-part

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

            <!-- Root logger configuration -->
            <Root level="WARN">
                    <AppenderRef ref="LOGFILE"/>
                    <AppenderRef ref="OSGI"/>

            <!-- Karaf Shell logger -->
            <Logger level="OFF" name="org.apache.karaf.shell.support">
                    <AppenderRef ref="STDOUT"/>

            <!-- Security audit logger -->
            <Logger additivity="false" level="INFO" name="org.apache.karaf.jaas.modules.audit">
                    <AppenderRef ref="AUDIT"/>

            <!-- openHAB specific logger configuration -->
            <Logger level="DEBUG" name="org.openhab"/>

            <Logger level="ERROR" name="openhab.event.ItemStateEvent"/>
            <Logger level="ERROR" name="openhab.event.ItemAddedEvent"/>
            <Logger level="ERROR" name="openhab.event.ItemRemovedEvent"/>
            <Logger level="ERROR" name="openhab.event.ItemChannelLinkAddedEvent"/>
            <Logger level="ERROR" name="openhab.event.ItemChannelLinkRemovedEvent"/>
            <Logger level="ERROR" name="openhab.event.ThingStatusInfoEvent"/>
            <Logger level="ERROR" name="openhab.event.ThingAddedEvent"/>
            <Logger level="ERROR" name="openhab.event.ThingUpdatedEvent"/>
            <Logger level="ERROR" name="openhab.event.ThingRemovedEvent"/>
            <Logger level="ERROR" name="openhab.event.InboxUpdatedEvent"/>
            <Logger level="ERROR" name="openhab.event.RuleStatusInfoEvent"/>
            <Logger level="ERROR" name="openhab.event.RuleAddedEvent"/>
            <Logger level="ERROR" name="openhab.event.RuleRemovedEvent"/>
            <Logger level="ERROR" name="openhab.event.StartlevelEvent"/>
            <Logger level="ERROR" name="openhab.event.AddonEvent"/>

            <Logger additivity="false" level="INFO" name="openhab.event">
                    <AppenderRef ref="EVENT"/>
                    <AppenderRef ref="OSGI"/>

            <Logger level="ERROR" name="javax.jmdns"/>
            <Logger level="ERROR" name="org.jupnp"/>

            <!-- This suppresses all Maven download issues from the log when doing feature installations -->
            <!-- as we are logging errors ourselves in a nicer way anyhow. -->
            <Logger level="ERROR" name="org.ops4j.pax.url.mvn.internal.AetherBasedResolver"/>

            <!-- Filters known issues of pax-web (issue link to be added here). -->
            <!-- Can be removed once the issues are resolved in an upcoming version. -->
            <Logger level="OFF" name="org.ops4j.pax.web.pax-web-runtime"/>

            <!-- Filters known issues of lsp4j, see -->
            <!-- https://github.com/eclipse/smarthome/issues/4639 -->
            <!-- https://github.com/eclipse/smarthome/issues/4629 -->
            <!-- https://github.com/eclipse/smarthome/issues/4643 -->
            <!-- Can be removed once the issues are resolved in an upcoming version. -->
            <Logger level="OFF" name="org.eclipse.lsp4j"/>

            <!-- Filters warnings for events that could not be delivered to a disconnected client. -->
            <Logger level="ERROR" name="org.apache.cxf.jaxrs.sse.SseEventSinkImpl"/>

            <!-- Filters known issues of KarServiceImpl, see -->
            <!-- https://github.com/openhab/openhab-distro/issues/519#issuecomment-351944506 -->
            <!-- Can be removed once the issues are resolved in an upcoming version. -->
            <Logger level="ERROR" name="org.apache.karaf.kar.internal.KarServiceImpl"/>

            <!-- Filters warnings about unavailable ciphers when JCE is not installed, see -->
            <!-- https://github.com/openhab/openhab-distro/issues/999 -->
            <Logger level="ERROR" name="org.apache.karaf.shell.ssh.SshUtils"/>

            <!-- Filters known issues of javax.mail, see -->
            <!-- https://github.com/openhab/openhab-addons/issues/5530 -->
            <Logger level="ERROR" name="javax.mail"/>
            <!-- Filters disconnection warnings of the ChromeCast Java API, see -->
            <!-- https://github.com/openhab/openhab-addons/issues/3770 -->
            <Logger level="ERROR" name="su.litvak.chromecast.api.v2.Channel"/>

            <!-- Added by Karaf to prevent debug logging loops, see -->
            <!-- https://issues.apache.org/jira/browse/KARAF-5559 -->
            <Logger level="ERROR" name="org.apache.sshd"/>
            <Logger level="ALL" name="org.openhab.binding.icalendar"/>

And now a little bit greater quote from /var/log/openhab/openhab.log:

2021-02-28 09:27:25.854 [DEBUG] [io.openhabcloud.internal.CloudClient] - Sending update ‘11.0 °C’ for item ‘TermostatSchlafZiGross_Temperature’
2021-02-28 09:27:26.383 [WARN ] [g.icalendar.internal.handler.PullJob] - Download of calendar timed out (waited too long for headers).
2021-02-28 09:27:26.386 [DEBUG] [g.icalendar.internal.handler.PullJob] - TimeoutException message is: null
2021-02-28 09:27:30.081 [DEBUG] [e.automation.internal.RuleEngineImpl] - The trigger ‘0’ of rule ‘FensterZu-4’ is triggered.

Also grepping with owndrive (my provider of nextcloud), wegt, curl doesn’t find more.

After i Reinstall openhab
3 (new) the ical works fin.
Thats really Strange.
What I Changed?
Just from openjava 11 to Zulu 11. Maybe this solv the Problem.

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.