Openweathermap 401 error

It was working, so something changed on their side recently.
I’ll take a look, thank you for the hint.

Can you give a try by adding limit=5 to the line? So we are in free user limit ranges.

OK, I’ll see with the lib owner if we have a workaround for this.
I can see that we are not using the last version. Maybe is already handled in the last version.

Seems an issue on the API.
Do you have the same issue as this one?

Yes, it’s the same issue. But again, I don’t think this must be considered like a bug because the API response with a free account fits the price chart on the openweathermap website.
16 days/daily forecast API = http://api.openweathermap.org/data/2.5/forecast/daily = owm.daily_forecast(…) = requires a paid subscription.
(But, I might be misunderstanding)
Anyway, I’d be happy if there’s a way to make this work with a free account

ok. I don’t see any workaround to get the «tomorrow» weather with the lib.
I’m not sure this is handled so far.

According to what I’ve seen in the API, there is a solution to get some detailed forecast information for the next 5 days.

Using the «5 days/3 hour forecast API», available with a free account, you can get the 5 next days forcast by 3 hours periods. With good python skills (which I don’t have), it might be possible to regroup all these data day by day and compute the results : day X pressure = average pressure for that day, day X min temperature = min temperature for that day, day X precipitations = sum of precipitations for that day, etc.
Though, it seems to represent a rather huge effort for a result that would probably not be fully satisfying.

For now I’ve just commented the «tommorow» part of the neuron to make the «today» weather work.
Thanks for the feedback on this issue !

Yes, I know that it’s possible to request on the api directly. The fact is taht we are using a lib to facilitate this step.
And the idea is to stick on this lib. My question was, is the lib aware of this potential change? Do we have another call that can do the trick?
I’ll check this when I have time.

Thanks for pointing out the issue.

Current weather and forecast ok.
Neuron updated.

Same problem with V2 update of this neuron :

pyowm.exceptions.api_response_error.UnauthorizedError: Your API subscription level does not allow to perform this operation
Reason: Invalid API Key provided

I’m still using a free API key. Am I missing something ?

Show us your synapse. (Cut some letters of your key)

- name: "weather-summary"
  signals:
      - order: "quel temps fait il"
  neurons:
      - openweathermap:
          api_key: "25xxxxxxxxxxxxxxxxxxxxxxbaa"
          lang: "fr"
          temp_unit: "celsius"
          location : "paris"
          country: "FR"
          say_template:
              - "Actuellement à {{ location }} : {{ current['weather_status'] }} avec une température de {{ current['temp'] }} degrés."

looks good.
weird, no typo in the api key? a space or something?

I can confirm the issue.
Exception in kalliope debug log on pastebin: https://pastebin.com/5T6iZevb

I’m using up to date pyown version 2.6.1 from pip:
pip install pyowm Requirement already satisfied: pyowm in /usr/local/lib/python3.6/dist-packages (2.6.1)

My synapse:

   - name: "getthe-weather"
     signals:
       - order: "Wie wird das Wetter"
       - order: "Wie ist das Wetter"
       - order: "Wie ist das Wetter heute"
     neurons:
       - openweathermap:
           api_key: "e9ecxxxxxxxxxxxxxxxxxxxxxxxxe2d6"
           lang: "de"
           temp_unit: "celsius"
           location: "Berlin"
           country: "DE"
           say_template:
           - "Heute wird das Wetter {{ weather_today }} bei einer Temperatur von {{ temp_today_temp }} Grad."

So weird, we don’t have the issue with @corus. Maybe because we have an old API key.

@Sispheor this is what I’ve been thinking about. Anyway, this neuron does not work for «recent» openweathermap users. Maybe you can confirm that by generating a new key / creating a new account.
I’ll switch to my previous «disappointing-current-weather-data-only» version for the moment.

You are using pyowm version 2.6.1?
We’ve updated it to 2.9.0. Can you give a try?
pip install --upgrade pyown

I’m using pyown 2.9.0 and I have the issue.
Run your code with a recent free API key and you’ll probably reproduce this issue.

I’m using pyown 2.9.0 and I have the issue.

I can confirm this. Uptdating to pyowm 2.9.0 didnt’t do the trick.

I looked into it and I can confirm it seems related to our «old» keys. With a new key, I have the same problem.

With the function three_hours_forecast() I’m able to get a forecast of 5 days for every 3 hours and also weather_at_place() is working which is for the current weather conditions.

So we have to rebuild the neuron again, to make sure everyone gets the weather. I will try to make a PR till the end of the weekend.

I took a look to the update.
I just feel uncomfortable with the fact that it looks like a trick to keep having for free something that is now reserved to paid user.
@LaMonF what do you think?

I took a look to the update.
I just feel uncomfortable with the fact that it looks like a trick to keep having for free something that is now reserved to paid user.
@LaMonF what do you think?

What exactly to you mean? I checked the pricing for the OWM API and I think, things should be OK there. Take a look at the pricing. 5 days forecast and current day weather should work.

We need to define clearly what we want to return. As the 5 days forecast is only for a 3 hour range.
How do we propose this as neuron input? The user provide the range of hours he wants?
We provide a dict of range and then the user take the one he wants in his template? We calculate the average from all range we got?

First of all I think about a switch. The user can set in the brain, if he pays for OWM or not.As default I would say, people use the free version. Using this switch we can say, that we provide the forecast the user asks for(paying users) or only the 5days/3hours forecast(free users).

Talking about what we provide for 5days/3hours forecast: How does OWM calculates the dayli forecast? I don’t know, someone who pays for OWM could find out, by comparing 5days/3 hours and dayli forecast. If they only use the max_temperature value for saying what temperature is gonna be, that should be an easy one.

But: I think it would be a nice feature to hand over the time period manually. I could imagine asking kalliope, what the weather will be in the morning. In my case this would mean: If it will be sunny/nice I’ll set my alarm 30 minutes earlier to go by bicycle to work. If it will be rainy, I’ll take the subway.

New version here ready for testing.

Update pushed in master branch. We’re good I think this time

Great ! I’ll give it a try asap.

Hi ! Thanks for the update on the openweathermap neuron, I have installed and tested it yesterday and it works.
However I’d like to tell you about a few things, but I don’t know if it should be considered as bugs or improvements. May we discuss it here or do I have to open a new issue ?

Come on the gitter chat to discuss about it and then we can open an issue if needed.