core: Invalid API Key provided
The problem
Hi,
The API key works with curl. I also generated a 2nd one, same problem.
At first, the default when setting up the integration was not onecall_daily but hourly. The very first time, I think the integration worked as sensors were created (but didn’t get data). I then realized I could not change the integration’s configuration, so deleted it and now I am faced with that problem.
What version of Home Assistant Core has the issue?
2022.11.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
openweathermap
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No, but on the openweathermap website, nothing is shown as "blocked".
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 11
- Comments: 27
I had the same problem with the message “wrong API key…”. It looks to me that the daily feature is no longer free on weatherman.org. Changing the configuration to hourly I get at least this configuration up and running again. For the daily configuration you have to have the Startup subscription on opernweathermap.org
This appears to still not be working. New HA setup and I already had an account with openweather. Attempted to use an already working API that’s currently used with a streamdeck action and that was invalid. I created a new key just for home assistant and that was also listed as invalid.
Hi, I subscribed recently to OWM and didn’t know which option to choose, got the same errors at the beginning by trying all options. On the OWM website I could find that the free API key only allows the “hourly” call, which actually is a 3h period granularity.
So selecting “hourly” works, but the other 3 options require a subscription to the OWM service as it seems.
I am therefore interested to have an option in the integration to retrieve the data on a 3h interval basis, but have a subsequent option to either process the data “as is” or aggregate it into a 24h dataset instead (calculated, so probably not as accurate as a “real” 24h dataset that you would retrieve from OWM).
My use case for example would be to know how much it would rain “tomorrow”, so I could just use the sensor “Forecast Precipitation” and I would get a 24h value instead of the 3h value I have now, which doesn’t help me much for what I want to do (deciding to water the garden or not).
I do it at the moment with NodeRed outside of the integration, by a direct query to OWM with my API key and it works, the raw data is there. But my script does not send back the calculated data to the Weather entity so I cannot use weather cards to display the aggregated data. I have to create my own parallel weather entity, so at the end I +/- have to rewrite the integration, so it’s too complex.
Edit: actually, it’s now mentioned in the integration page
Same problem here, none of the options work. Signed up for the new (?) One Call API 3.0 that should give all hourly, daily etc. in one API call and includes 1000 calls per day. Is this integration not supported in HAOS?