Openweathermap api key still not valid after 12 hours

Configuration
, ,
21

Same issue. At first it worked, but when I added the integrity again, it no longer worked.

Message: Invalid API Key provided

22

I’m having a similar issue. Tried signing out and setting the call type. Hopefully we get a resolution soon.

23

Changing to “hourly” in the Configuration worked for me - switched it back to “onecall-hourly” and it failed again. Changed to hourly and it worked again. No idea why that option is broken. Try it out.

24

This error seam to persist to this day.
No matter hte call type i use: Invalid Key provided

1 Like
25

I’m heaving this issue with OpenWeatherMap. When trying to install this integration, I get “Invalid API key” (on multiple API key and with all settings)

26

Logging off from Openweather on my browser worked but only for hourly.

27

Same problem. Latest version of HA. Unfortunately nothing in the thread worked for me so far.

28

‘hourly’ works for me and ‘onecall-hourly’ immediately breaks

29

Looks like I was able to get the ‘onecall-hourly’ mode to work by subscribing to the Open Call API 3.0.

I initially set up a free plan and couldn’t figure out how to get hourly data, but upon further reading, I realized that I needed to subscribe as well.

1000 calls a day are free and then you pay per 100 calls thereafter (you can set your limit to 1000 calls though)

image
image1342×1796 334 KB

They say it is an instant upgrade but it took a few minutes after I changed the mode in HA from ‘hourly’ to ‘onecall-hourly’ for things to start working.

Then I was able to get this output (instead of 3hr intervals)

image
image1308×1748 162 KB

Hope that helps

6 Likes
30

For anyone that waited 2 hours and still gets the empty dialogue, it’s because your latitude and longitude have too many digits. Try shortening to 4 decimal places and then selecting “hourly”

2 Likes
31

So I also have the issue. my api keys do work (I tested through postman). I tried both api versions and reducing longitude/lattitude to integers. Any furhter idea is welcome.

3 Likes
32

Same issue. Invalid API. Tried reducing decimals on lat and lon, and I don’t even get an option to choose hourly or anything.

33

I have the same issue. At the same server, ssh terminal, curl command with API request works good.
But I can’t add Home Assistant integration with the same API key: “Invalid API key” error.

34

I had the same issue. Tried the direct API call and it didn’t work either. After debugging it for a bit, I found out that you have to subscribe to at least one plan. In my case I subscribed to the free plan, which still requires billing details, such as, credit card details.

After doing this and waiting a few hours. The direct API call started working and I was able to add the integration to HA.

Sidenote: It doesn’t matter how many digits your coordinates are. Open Weather Map deal with it themselves.

1 Like
35

Is this the One Call API 3.0 Plan you’re talking about?

Edit: It’s now valid…you have to subscribe to 3.0 Plan, where 1000 calls/day are free, entering paypal/visa whatever…

1 Like
36

@BLotto, exactly.