0, 0 was just a dummy variable to test if something from my other inputs (my home town coordinates) was wrong. But neither that, nor home town, nor "auto-set" was working. The 3 settings you mentioned are going to fix my problem? I'll give it a try and report back. Thanks!
@Corti I chanted the settings as suggested, but the error message is still the same: "webquery failed: Der Remoteserver hat einen Fehler zurückgegeben: (403) Unzulässig.". Are there any ports I have to open in order to allow the API to get that information from climacell?
this is how i have my settings. Check the API as Woodee suggests. The strangest thing is that I collected data and applied it to the track, that error never appeared. * it does not apply the weather because the server I am modifying it
https://docs.climacell.co/reference/api-errors There are 2 403 errors possible. Check your API key and/or subscription. Do you use the key multiple times for multiple servers? https://docs.climacell.co/reference/api-errors There are 2 403 errors possible. Check your API key, is it complete/correct? Your subscription? Do you use the key multiple times for multiple servers? have you exceeded a poll limit? BR
Very weird. I double checked my API key (just copy & paste from climacell) - didn't work. I requested a new free API key - didn't work. I am using only one server and it fails on the first request, so poll limit should not be an issue. I'm using the developer API key (free version), and on the site it is set to "active", so this should be sufficient, correct? Thanks for your help & best regards, Lukas EDIT: Is anyone willing to try my (second) API key to check if it is working? I wanna narrow down the possible errors. Thanks!
Ok guys, I figured it out. To prevent other new users of this great tool making the same mistake, here is what went wrong for me: On climacell you can get two free API's (climacell API and weather API) - by using the link in the first post of this thread, I got the wrong API. Make sure you get the "weather API" when signing up, not the climacell API key! To get the correct one: go to https://www.climacell.co/pricing/, then select "login" in the top right corner, select "weather API" and then you should be able to sign up for the correct API. Thanks again for your help, Lukas
They might have changed the address, as the link on first page pointed once to weather api. thx 4 the hint I ll correct the link
is there any way to avoid this sudden change in clouds with the settings? See the video for example: https://www.twitch.tv/videos/858585742?t=02h35m27s
You probably know about it already so apologies but did the weather load first of all? I've not seen that occur for me.
I think so.... it started about 1 1/2 hours before that last cloud change. I will try monitor throughout a race to see what happens. I just had a look at the Climacell dashboard and I don't know how long it takes to update but apparently my API made 0 calls today! Confusing. Could it be just using the "scripted" settings in game instead of the app?? I am using a player file which is not named the same as default.
The app shows success grabbing the weather data but 0 calls in the Climacell dashboard. I did a 100% race today with the app running, hoping that I was running realtime weather.
Could someone help me with this plugin, not sure what I have done wrong but its almost certainly user error! I am getting the 403 forbidden message and I cant see what I have done wrong.
First of all dont show your key See #251 some posts above, he ran into same problem and found the solution (wrong api key type)