For the past few days I’ve noticed many errors in my logs when using the Weather binding to query Yahoo. The errors are
2017-05-17 05:23:34.047 [WARN ] [ther.internal.parser.CommonIdHandler] - CommonId not found: CommonIdHandler[provider=YAHOO,id=<null>,icon=<null>]
2017-05-17 05:23:34.062 [WARN ] [eather.internal.bus.WeatherPublisher] - Weather forecast day 0 not available for locationId 'home', only 0 available
2017-05-17 05:23:34.067 [WARN ] [eather.internal.bus.WeatherPublisher] - Weather forecast day 0 not available for locationId 'home', only 0 available
Taking a look at Yahoo’s documentation it has examples of how to query the API, which return a not authenticated error
Nope. Mine works - mostly. Meaning sometimes the OH query fails (with CommonId not found) and sometimes it doesn’t. Sometimes it is fine for days. A couple of month ago it failed practically every time, then with no OH changes resumed working well. I think its just a response time issue at the Yahoo end.
People quite often get fed up with Yahoo and use alternate weather providers for this reason. A recent discussion
Thinking about it mine isn’t totally broken, just broken for a large proportion of the time. Last time I looked around Yahoo was the most accurate, but I’ll take a look and see if any of the other providers have improved in the last few months.
Thanks for the reply
I’m querying Yahoo every hour, and checking my logs it fails 10 times per day on average (worst was 12 times, best 6 times). Using the litlle “workaround” (see post 8 in linked thread) I put in place I’ve decided to stay with yahoo - just too much hassle changing to another provider imho…