-
Notifications
You must be signed in to change notification settings - Fork 182
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
Retargeting to PiOS/Python3/PyQt5 #228
Comments
Using the latest version of Raspberry Pi OS (raspberrypi 5.10.92-v8+ #1514) I'm using the python3-SerBrynden Branch. After working out the changes between the install of the Master Branch and this one, I am getting the following when I attempt to do a First Start. It is possible I missed something... I did Blank out my Keys and location in this output pi@raspberrypi:~/PiClock $ sh startup.sh -n -s |
Climacell.co changed to Tomorrow.io and their v3 API was replaced with the v4 API. I don't think the v3 API works anymore and, last I checked, the PiClock code hasn't been updated to support the v4 API. I use OpenWeatherMap.org. |
That was it.... Thanks for your Help |
So seeing 2 issues now, one is brand new. This morning a New error popped up. This causes PiClock to Crash. Its referencing "Compass" in the error. Near as I can tell its something to do with decoding the METAR. Originally I thought it had something to do with the METAR I was using not being available or missing. However I was able to pull the file up and restarting PiClock caused the same issue. I tried using a Different Airport code, utilizing the nearest international airport, thinking its format would not have the same error. However the same problem happens. the code referenced is Line 1178 and is "wd = f.wind_dir.compass()" Unfortunately my programing knowledge is limited here and cant seem to find where is defined. libpng warning: iCCP: known incorrect sRGB profile |
Tried again today, and the Crashing and alert about "Compass" have stopped. However the Image corruption continues |
I don't see why it has that error. K12N works fine for me in PiClock and PiClock3. Perhaps an upgrade... sudo pip3 install python-metar --upgrade |
I ran the command you provided with the following results: pi@raspberrypi:~ $ sudo pip3 install python-metar --upgrade I restarted PiClock and it is working. However this error seems to happen after its been running for a while. I'll let you know should it fault again. I still see the problem with the radar overlays being garbled. Its particularly visible on the second page where it looks like is random noise along with the radar overlays being mixed on both maps. it seems to get worse over time with images from the previous update being mixed together with new update |
Still getting that same crash related to "compass" It seems that it happens when a Wind direction is not included in the Metar Such as: |
Following up. 2022/03/09 19:54 |
So After some research I am able to duplicate the error. Seems to be a Bug in the python-metar code relating to the wind_dir.compass variable. If the wind is designated as something like "VRB03KT" it throws that error. Its related to the VRB (variations in wind direction greater than or equal to 30 degrees). Here is a little Test program I put together. If you change the Comment for the sample METAR you can make the error happen or not.
|
So I opened a Issue with the Python Metar Github. Seems that it is indeed an issue with that code. They aren't quite sure yet how to fix it. But there is a Work around... If you Replace the 2 occurrences of: wd = f.wind_dir.compass() with: if f.wind_dir is None: That will set the wind direction to a blank in the cases that it isn't specified or VRB. This will stop the crashing at least until a more elegant method is developed. I am still having issues with the Radar overlay. I'm not quite able to figure that out.... |
Thanks to @SerBrynden we're moving down the road to python3/PyQt5. I'm also moving to PiOS (bullseye) (PiOS starting 2021-10-30)
The upgrade path may be difficult for those on older versions of Raspbian/python2. Not sure how to handle these issues yet, to make it easy to upgrade without starting over.
The python3/PyQt5 testing branch is Python3-SerBryden
/K
The text was updated successfully, but these errors were encountered: