Closed creas002 closed 4 years ago
Thanks for your kind words! It looks like you are getting this error because the CheckWX API key in your .ini file is not correct. When I try and use it to retrieve the closest METAR to your station location I get the error:
{"statusCode":401,"error":"Unauthorized","message":"invalid x-api-key in request header"}
.
Can you login to your CheckWX account again (https://www.checkwxapi.com/auth/login) and double check that you have copied the API key correctly into the .ini file? The current key in your .ini file is two characters shorter than mine, so you might have missed a bit. If you have copied it correctly, can you try deleting the existing API key and generating a new one, or deleting your account entirely (under the "Profile" tab) and starting again? Hopefully one of these will get you up and running with a working API key. If nothing works let me know and we can troubleshoot further.
Wow, that was it. Originally I wrote the API key down and manually typed it in. There was 2 repeating characters that I missed. I enabled ssh demon last night so making the change from SecureCRT was quick and painless. I really struggled with determining the cause of the error. I read where you were reading about Sager and discussing with Weather34 - Brian, but I never understood how you actually pulled it off. I did not see any signs of an error in the wfpiconsole.log. Wonder when it first initializes if if could log PASS/FAIL for testing the API key works.
Thank you sir for your prompt reply and helping me sort this. I like giving a best effort before reaching out for help, but I was totally lost as to what was happening.
UPDATE: If I had half a brain, I would have looked at sager.py and would have realized it was using CheckWX. Hindsight is 20/20.
Thanks again for all your work on WeatherFlow_PiConsole. I could not be happier.
Kind Regards Richard 73 de AI4Y
Great! Glad to hear you are up and running. That's a good idea to check whether the API key is valid. I should be able to do that easily during the initial generation of the config file so I will look into it.
Hi Pete Not sure if I can respond directly to you via email, but I was not sure how to convey something without opening a new issue. My previous problem was operator and not a real issue. Thank you for your help on that and closing it out.
I wanted to share with you that I was able to get WFPi Console running on my Windows 10 PC using Python 3.8. I followed the instructions in Github and step #3 on https://kivy.org/doc/stable/installation/installation-windows.html kept failing. It fails I believe because Phyton 3.8 does not support kivy=1.11.1
So rather that running step #3 --> python -m pip install kivy==1.11.1 I installed kivy using --> pip install kivy[base]
kivy installed fine and the wfpiconsole fired right up and has run for 15+ hours without issue.
I understand these instructions referenced are managed by kivy.org , but I wanted to let you know what worked for me.
Kind Regards Richard
On Fri, Aug 21, 2020 at 6:01 AM peted-davis notifications@github.com wrote:
Closed #19 https://github.com/peted-davis/WeatherFlow_PiConsole/issues/19.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/peted-davis/WeatherFlow_PiConsole/issues/19#event-3678908237, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQVTS6KIFXMLJCTOK7WRPYLSBZAWZANCNFSM4QFO2QGA .
I'm a new Tempest owner and recently setup wfpiconsole . Very nicely done Peter! Thank you for all your work to make this excellent console.
I'm getting the following panel error on my Pi 4b --> Sager Forecast ERROR: Missing METAR information.
I seem to have all functionality working as expected except for this problem and I've been looking at it for a while. Hoping you can tell me how to debug this error. I'm attaching ini and log files, which I don't notice any issue with.
wfpiconsole.zip