I can’t figure out why it’s not working. I double and triple checked the CheckWx key in the .ini file and I still have an error. Perhaps something is wrong on my CheckWx account. I’m using KBGM METAR which is the closest to my residence. I’m perplexed at this point.
can you show part of the checkwx api key ?? It’s a long row of numbers and letters, not a name
Yup that’s what I have in the file. 
I think I counted 26 letters and numbers in the key.
If you open a terminal on your Raspberry Pi and copy the following command in and then press enter, what do you see?
curl 'https://api.checkwx.com/metar/lat/42.32122/lon/-75.02988' -H 'X-API-Key: YOUR_API_KEY'
Replace YOUR_API_KEY with your API key, and make sure you retain the last apostrophe. I see the following output:
{"results":1,"data":["KMSV 251856Z AUTO 24006KT 10SM FEW065 BKN090 OVC110 24/11 A3002 RMK AO2 SLP161 T02390106"]}
{“statusCode”:401,“error”:“Unauthorized”,“message”:“invalid x-api-key in request header”}
your key seems invalid. Think you need to check on the checkwx site your api key and see if it is activated.
I believe that it is. I requested one and that’s what I have entered in the .ini file.
That’s weird. Definitely something wrong with the API key you are using. There are also 26 letters/numbers in my API key so it sounds like you are using the right thing. I’m not sure what to suggest. You could trying registering again after deleting your account, or email the CheckWX support?
I’ll just keep digging. I already tried deleting my CheckWx account, registering again and changed the API key with the same result. Is the .ini file the only place I’d have to change that?
Yep the .ini file is the only place. It’s late here but I’ll have another look tomorrow. It could be a server issue with new API keys, so I’ll try registering a dummy account tomorrow and see what happens
Key is in correctly. Station ID is 21829
No worries, thank you. Appreciate everything you do for this console.
I wonder if you are having the same problem that I am and there actually is a problem with the CheckWx site and their API.
@bmcgrady384 and @brian.vargo, I have just registered for a test account on CheckWX and I can confirm that there seems to be an issue their end with newly registered API keys. I have tried twice and both times the API key did not work. I have used the Contact page on their website to report the error, but you might want to do the same.
Alright thanks. I knew something was up. I also contacted them via their website as you suggested yesterday.
I also found another free weather API service that could replace DarkSky. ClimaCell seems to have one. I don’t know what DarkSky provided because I never used it, but is this something similar that can be incorporated into the console instead?
Peter…Thoughts on the ClimaCell API from my above post? Any idea how I would integrate that into the Raspberry pi WFconsole if it works? I have neither the forecast nor the Sager now.
Hello Peter, I’m Reggie (rnix.1) and I’m interested in building the PiConsole but with a 10" display, not the 7" because I’m old, (happy to be my age) but can’t see. Is it possible to build this console with a 10" display without any or a lot of code changes?
Cheers,
Reggie
My plan at the moment is to use the forecast provided by WeatherFlow (the same one that is used in the Tempest app) to replace the DarkSky forecast. WF are still putting the finishing touches to the public API, but once that is finalised I will push out an update.
If you want to go ahead an incorporate the Clima Cell API regardless, have a look in the file lib/forecast.py to see the details of how the DarkSky/UK MetOffice forecasts are downloaded from their APIs and then parsed for display on the console. You would need to write some similar functions to achieve the same for the Clima Cell API.
2 Likes
Hi Reggie, thanks for checking out the console! The console will ‘work’ quite happily on a 10 inch screen - the only issue you may have will be due to using a different resolution. The console is designed to work with a fixed resolution of 800 x 480, and any deviations from this will cause stretching/squashing of the graphics. An easy work around would be to set the 10 inch screen resolution to 800 x 480 as well. It might degrade the quality of the screen close up, but from a distance it should look fine.
Here’s an example of a user running an old version of the console on an old laptop LCD panel: Announcements & Updates - #199
I set the lightning panel as secondary number 1, but when strikes occur, its toggling the bottom left one which i ha e as sunrise and moon…