New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Weather variables #140
Comments
@VicoHBB you need to create an acccount at https://openweathermap.org/api, copy your API Key and paste it into the key variable, then look up for your coordinates using google or the GPS of your phone and put those in the 2 pairs of double quotes as indicated, the top one being latitude and the bottom one longitude. |
Is there any other step? I have registered and entered my data, but it still doesn't work properly :( |
@VicoHBB iirc that's all i did, sorry m8. |
I can´t get the weather widget to work correctly.
|
@dmguezjaviersnet Do you create other API key or just use the key by default? |
The key that I currently use is the default one.
Den mån 26 sep. 2022 15:57VicoHBB ***@***.***> skrev:
… @dmguezjaviersnet <https://github.com/dmguezjaviersnet> Do you create
other API key or just use the key by default?
—
Reply to this email directly, view it on GitHub
<#140 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3ILDWXW4TBJHTSB43RV7WDWAGTUNANCNFSM6AAAAAAQNAIPN4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@dmguezjaviersnet Did you install something else or just put the variables? |
Iirc all i did was to plug in the value for the variables @VicoHBB, sorrry :( |
For anyone coming to see this in the future the weather widget will no longer work as it calls OneCall 2.5 which has since been upgraded to OneCall 3.0. |
Hi everyone,I noticed that the weather widget is not working correctly, searching in the files I found that in the
user_variables.lua
file these variables are blank, (I put the code snippet below) could someone guide me on which API to use and how to put the coordinates?The text was updated successfully, but these errors were encountered: