Problem with OpenWeatherMap

[bwl-andromeda]

Hello, dear developers, I am using Arch Linux in conjunction with the Hyprland window manager. When initializing .wegorc and after trying to configure it, the same error is displayed
401 HTTP error.
I use the standard key that is given upon registration.
Here are my settings:

# aat-frontend: Show geo coordinates (default false)
aat-coords=false

# aat-frontend: Monochrome output (default false)
aat-monochrome=false

# BACKEND to be used (default forecast.io)
backend=openweathermap

# NUMBER of days of weather forecast to be displayed (default 3)
days=3

# forecast backend: the api KEY to use (default )
forecast-api-key=

# forecast backend: print raw requests and responses (default false)
forecast-debug=false

# forecast backend: the LANGUAGE to request from forecast.io (default en)
forecast-lang=en

# FRONTEND to be used (default ascii-art-table)
frontend=ascii-art-table

# json frontend: do not indent the output (default false)
jsn-no-indent=false

# LOCATION to be queried (default 40.748,-73.985)
location=Cheboksary

# openweathermap backend: the api KEY to use (default )
owm-api-key=(default key)

# openweathermap backend: print raw requests and responses (default false)
owm-debug=true

# openweathermap backend: the LANGUAGE to request from openweathermap (default en)
owm-lang=en

# UNITSYSTEM to use for output.
# Choices are: metric, imperial, si, metric-ms (default metric)
units=metric

# worldweatheronline backend: the api KEY to use (default )
wwo-api-key=

# worldweatheronline backend: print raw requests and responses (default false)
wwo-debug=false

# worldweatheronline backend: the LANGUAGE to request from worldweatheronline (default en)
wwo-lang=en

[kordianbruck]

Looks like you didn't configure an api key?

[flaflutsch]

Hello, I also had problems with openweathermap always ending up in 401. After some investigations I figured out that I surrounded my key with quotes ("") which resulted in an invalid key. Deleting them solved the issue. Also referring the documentation, it can take some time until the key is recognized as a valid key.