Weather Binding throws many forecast not available errors

Add-ons Bindings
#1

All-

I am using the weather binding with OpenWeatherMap. The system seems to be working fine, but in my Openhab.log file, there are a huge number of errors that read:

[ERROR] [b.w.i.gfx.WeatherTokenResolver:78 ] - Weather forecast day 2 not available, only 0 available
java.lang.RuntimeException: Weather forecast day 2 not available, only 0 available.

at org.openhab.binding.weather.internal.gfx.WeatherTokenResolver.replaceForecast(WeatherTokenResolver.java:111) ~[bundlefile:na]
at org.openhab.binding.weather.internal.gfx.WeatherTokenResolver.resolveToken(WeatherTokenResolver.java:68) ~[bundlefile:na]
at org.openhab.binding.weather.internal.gfx.TokenReplacingReader.read(TokenReplacingReader.java:74) [bundlefile:na]
at org.openhab.binding.weather.internal.gfx.TokenReplacingReader.read(TokenReplacingReader.java:100) [bundlefile:na]
at org.openhab.binding.weather.internal.gfx.TokenReplacingReader.read(TokenReplacingReader.java:90) [bundlefile:na]
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1364) [org.apache.commons.io_2.0.1.v201105210651.jar:2.0.1]
at org.apache.commons.io.IOUtils.copy(IOUtils.java:1340) [org.apache.commons.io_2.0.1.v201105210651.jar:2.0.1]
at org.apache.commons.io.IOUtils.copy(IOUtils.java:1393) [org.apache.commons.io_2.0.1.v201105210651.jar:2.0.1]
at org.openhab.binding.weather.internal.gfx.WeatherServlet.doGet(WeatherServlet.java:129) [bundlefile:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) [javax.servlet_3.0.0.v201112011016.jar:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) [javax.servlet_3.0.0.v201112011016.jar:na]
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) [org.eclipse.equinox.http.servlet_1.1.300.v201$
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-18$
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-1841.jar$
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) [javax.servlet_3.0.0.v201112011016.jar:na]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598) [org.eclipse.jetty.servlet_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:486) [org.eclipse.jetty.servlet_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522]

etc. Does anyone have any ideas? I am refreshing every 10 minutes, but these errors periodically occur and are logged every few seconds. The logfile is getting big.

Many thanks,

-Mark

#2

Same here…

Sometimes it seems to work and all data will be displayed, but mostly it fills up my logfile with the above mentioned errors.

I´m using OpenHAB v1.8.2.

Thanks
Simon

#3

Could you replace your weather JAR with this one and tell me if the log spam decreases to single-line WARN messages instead of full ERROR messages with stack traces? Would this change be worth submitting a pull request?

#4

Thanks for your help. - I´ve replaced the JAR and it seems to reduce the spam as you had assumed

2016-04-03 19:50:01.932 [WARN ] [b.w.i.gfx.WeatherTokenResolver] - Weather forecast day 0 not available, only 0 available
2016-04-03 19:50:01.934 [WARN ] [b.w.i.gfx.WeatherTokenResolver] - Weather forecast day 1 not available, only 0 available
2016-04-03 19:50:01.936 [WARN ] [b.w.i.gfx.WeatherTokenResolver] - Weather forecast day 2 not available, only 0 available

…but still 90% downtime of the weather-webview. I´ll give OpenWeatherMap a try…

#5

All-

I am also running Openhab 1.8.2. I noticed that if I reduce the update frequency to every 60 minutes (as opposed to every 10 minutes as in the default configuration) these errors disappear. That said, I just replaced the JAR with the recommended 1.9 SNAPSHOT - will let you know if there are further issues.

Many thanks,

-Mark

1 Like