openweathermap custom API broken in v138
Closed this issue · 5 comments
Description
Version 138 breaks the custom API key even more than the last version. Previously I could save my key using gsettings --schemadir ~/.local/share/gnome-shell/extensions/openweather-extension@penguin-teal.github.io/schemas set org.gnome.shell.extensions.openweatherrefined custom-keys "['', '<KEY>', '', '']"
but that no longer works with the latest version.
System
Ubuntu 24.04 LTS
Settings
{"app-version":"138","git-version":"138.r0.g6367a11","gnome-version":"46.0","user-locale":"en","custom-keys":["","<REDACTED>","",""],"appid":"<REDACTED>","actual-city":"1","weather-provider":"'openweathermap'","has-run":"true","locs":[{},{}],"show-sunsetrise-in-panel":"false","frozen":"false","weatherapidotcom-key":"<REDACTED>","geolocation-appid-mapquest":"<REDACTED>","disable-forecast":"true","position-in-panel":"'center'","show-comment-in-panel":"false"}
This is not a bug.
First of all, the array should be three fields long, not four. Next, you are placing your key into the field for WeatherAPI, not OpenWeatherMap. The reason this worked before was because of a bug, which was just fixed.
Change your command to:
gsettings --schemadir ~/.local/share/gnome-shell/extensions/openweather-extension@penguin-teal.github.io/schemas set org.gnome.shell.extensions.openweatherrefined custom-keys "['<KEY>', '', '']"
That worked, but I couldn't do it via the UI.
That worked, but I couldn't do it via the UI.
Neither can I. I don't know if this is a gnome-shell/wayland thing, the extension, or something else. Other people have been able to do it via the UI without issue so it is possibly not the extension causing this.
What exactly isn't working with the UI? Is it related to #58?
The key format is:
- OpenWeatherMap
- WeatherAPI.com
- Visual Crossing
- Unused
The fourth key is there because I released the hotfix in the middle of adding Open-Meteo weather provider, so it just does nothing right now.
This entire system is getting a re-do which should be done in the near future.
The UI issue only affected certain API keys and has been fixed for the next release. Until then use the workaround described above.