-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[weather1] Request: add support for the free version of forecasts for OpenWeatherMap #5309
Comments
The error you're getting is because you're using an invalid API key. There's nothing wrong with the binding. And the forecast URL certainly does have 'daily' in the path. See here. |
OK, there are indeed 2 API endpoints
The problem is that the 16 day forecast is not included in the free plan, that's the reason why I'm getting the "Unauthorized" message. So the question is if this is intended. The documentation of this addon says that forecast is possible for If this is not intended we have to figure out how to change addon to use the 5 days forecast. I see now that simply removing the "daily" from the url is not sufficient, because the result will not be divided in days, but in 3-hour blocks. What do you think? (Additional info: the API access key is correct, the call to get the current weather works fine) |
Ok. That is indeed a different thing. I've changed the title accordingly. |
The bug is still there. No forecast possible with OpenWeatherMap. |
I notice the same issue. Could this be fixed somehow? |
There's an ESH binding for OWM in development. |
Any updates on this? It would be great if it's possible to use free OpenWeatherMap-API with weather1 binding. What about a toggle for free and paid more detailed forecast? |
No, not yet (see #5344 (comment)). It cannot be implemented without reaching a decision on the following questions.
|
Please update your docu accordingly. I freshly have requested an API key and run into the same problem. Just wasted my time till I found this postings .... |
I'm another person who has wasted hours setting this up only to find this thread and experience the same issue. I'm not interested in paying for weather info for residential use. Have no choice but to switch to Yahoo (which has limited availability) as my free provider, until OpenWeatherMap and its common multi-hour forecasting feature is supported. To comment on the question related to forecasting data being in multiple segments per day, rather than one blob per day. I would suggest configuration params on top of Otherwise, your add-on looks excellent -- thanks for the hard work thus far! |
I also walked straight into this issue one hour ago. As I'm doing the first steps with openHAB i was confused by successfully getting stuff from the API while at the same time getting an invalid API key error. openHAB/userdata/logs/events.log openHAB/userdata/logs/openhab.log |
I'm expiriancing the same issues. I just upgraded to the latest available version and now these errors are showing. So for me this worked before, but not anymore. |
All, Just a short heads-up: I will not come up with a solution for this. We now have a dedicated OpenWeatherMap binding available in the ESH / OH2 distribution. I recommend you to use the new binding if you like to fetch data of the free 5 day / 3 hour forecast.
@staehler Feel free to add it to the documentation and contribute. @9037568 Shall we consider to close this issue? |
This new binding is not available in my installation openhab 2.3.0-1 (stable) |
Agreed. |
@kgooris I am afraid that is not possible. The OWN binding uses features which are not available in OH2.3. |
When will it become available in stable version? |
@kgooris In the next release version (OH 2.4). I do not know an exact release date for it yet. |
I created a version with the free api for forecast. |
Hello! |
@MrTheBarbarian : yes, that's the correct location |
|
This conversation needs to move to the community forum. |
Wrong url for weather forecast request for OpenWeatherMap. There is no "daily" in the url, see documentation https://openweathermap.org/forecast5
Expected Behavior
Working forecast for OpenWeatherMap (http://docs.openhab.org/addons/bindings/weather1/readme.html#forecast)
Current Behavior
Forecast is broken, see karaf log:
Possible Solution
See merge request #5308
Steps to Reproduce (for bugs)
log:set TRACE org.openhab.binding.weather
Your Environment
The text was updated successfully, but these errors were encountered: