Ok, so I think this is the problem. Python version 3.6 has become deprecated in favour of versions 3.7 to 3.10. Unfortunately you are running Ubuntu 18.04 which does not upgrade Python beyond v3.6 by default.
I know I originally said Ubuntu 20.04 was not compatible with the PiConsole, but this is now probably no longer true (although I haven’t had a chance to test) and I would suggest that you think about upgrading to solve your issues
Ok. Thanx. I see if I can do that. Thanx much!
Peter, Thanks again for the amazing console. I updated just fine and everything has been working fine. I haven’t run the latest update yet that fixes all the bugs, and my issue is very minor compared to all the others. My Today rainfall total differs from what shows on the Tempest page. For example, the console shows 0.56" for today and the tempest page shows 0.42". Unless they started running rain check in the middle of the day and not after midnight, I am not sure the reason for the discrepancy.
anyway, thanks again, and not a big issue at all compared to the others, just thought I would let you know.
This is exactly what is done now. RainCheck has been rebranded as NearCast rain, and it is a process that is run continually throughout the day. You can see more details here:
“NC Rain data is provided in the app throughout the day (exact times may vary depending on weather conditions).”
I need to have a think about how to handle this in the console
Ok, I’ll try and do a fresh install on my own Pi3 with Bullseye and see what happens. Do you have anything else running on the Pi at the same time?
Thanks Peter. I figured this is what had happened, must have missed the info on it.
Hi Peter, thanks for all of the amazing support for this console! I’ve been attempting to update to the latest version, but have not been successful yet. When updating, I get the common “Unable to update local package cache” error. So as suggested in this forum, I went ahead and ran “sudo apt-get update --allow-releaseinfo-change”, but then I get the following error:
I scoured this forum to see if anyone else had a similar issue, but didn’t see anything. Thoughts on how to fix this? I attempted to uninstall and reinstall wfpi console, but I’m getting the same issues upon reinstall. Thanks!
Welcome to the forums! Unfortunately this isn’t an issue with the PiConsole, but rather a problem with the software repositories your Pi is trying to use. You are almost certainly running Raspberry Pi OS (Buster), but you’ll see from the error messages that it is trying to located software repositories associated with Rasbian Wheezy, which is years outdated. Uninstalling and reinstalling the console is not going to fix this problem.
You can either Google the error “The Rasbian Wheezy repository does not have a release file” as there are probably solutions out there, or you can try reinstalling the Raspberry Pi OS from scratch
Hi, i was running the wfpiconsole on my rpi3+, everything works fine (i can start,stop, update the console). But now - when i want to stop or update the wfpiconsole i get the massage: /usr/bin/env: „bash\r“: file or directory not found
It’s possible to update/upgrade the pi by commands and use the curl command to install the newest version. But start/stop/update promt this error
[Update: Thanks to Vince, I found the answer]. I hate to ask such a noob question, but how do I find and open the wfpiconsole.ini file?
Try looking in the wfpiconsole directory under the pi user’s $HOME…
To open it you need to know how to edit a simple text file on Linux, and there are approximately a zillion and a half tutorials for how to learn that. That said, I’d suggest you try the free edx.org Linux Foundation intro to linux course.
This is odd. It looks like the install script has picked up Windows style line endings (rather than Unix style), which is causing all kinds of trouble. I don’t quite understand how it has happened to only affect one person.
There is some good information here: windows - env: bash\r: No such file or directory - Stack Overflow
Can you run these commands in a terminal (taken from the link above) and let me know if it is fixed?
sudo apt-get install -y dos2unix
dos2unix ~/wfpiconsole/wfpiconsole.sh
Thanks for the direction on this Peter. Reinstalling the OS did the trick. I’m now up and running with the updated version!
I used to see this a ‘lot’ in trying to support Windows folks who tried to use Windows editors to edit unix files, then they’d do something strange in copying the files back and forth. It’s been too many years to recall completely, but I think it had something to do with them using ftp and setting the ‘binary’ (or not binary) switch wrong.
Unix/Linux and derivatives use <LF> as the end-of-line delimiter in text files. Microsoft uses <CR><LF> for its line delimiter. Using/editing files with the other’s delimiters leaves hidden characters behind.
FTP’s default transfer mode is ASCII (text), which usually fixes the line terminators as it copies. If you change to binary transfer mode, it sends the file with no modifications…
After upgrading to the latest on both the OS and the console I am getting errors of barometer images not found. I have searched this list but haven’t found an answer. Any ideas on where to begin? This has been a stable console for many months.
[e[1;32mINFOe[0m ] [Logger ] Record log in /home/pi/.kivy/logs/kivy_22-03-23_2.txt
[e[1;32mINFOe[0m ] [Kivy ] v2.0.0
[e[1;32mINFOe[0m ] [Kivy ] Installed at "/home/pi/.local/lib/python3.7/site-packages/kivy/__init__.py"
[e[1;32mINFOe[0m ] [Python ] v3.7.3 (default, Jan 22 2021, 20:04:44)
[GCC 8.3.0]
[e[1;32mINFOe[0m ] [Python ] Interpreter at "/usr/bin/python3"
[e[1;32mINFOe[0m ] [Config ] Verifying station details
[e[1;32mINFOe[0m ] [Factory ] 186 symbols loaded
[e[1;32mINFOe[0m ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_pil (img_ffpyplayer ignored)
[e[1;32mINFOe[0m ] [Window ] Provider: egl_rpi
[e[1;32mINFOe[0m ] [GL ] Using the "OpenGL ES 2" graphics system
[e[1;32mINFOe[0m ] [GL ] Backend used <gl>
[e[1;32mINFOe[0m ] [GL ] OpenGL version <b'OpenGL ES 2.0'>
[e[1;32mINFOe[0m ] [GL ] OpenGL vendor <b'Broadcom'>
[e[1;32mINFOe[0m ] [GL ] OpenGL renderer <b'VideoCore IV HW'>
[e[1;32mINFOe[0m ] [GL ] OpenGL parsed version: 2, 0
[e[1;32mINFOe[0m ] [GL ] Shading version <b'OpenGL ES GLSL ES 1.00'>
[e[1;32mINFOe[0m ] [GL ] Texture max size <2048>
[e[1;32mINFOe[0m ] [GL ] Texture max units <8>
[e[1;32mINFOe[0m ] [Window ] virtual keyboard not allowed, single mode, not docked
[e[1;32mINFOe[0m ] [Text ] Provider: sdl2
[e[1;32mINFOe[0m ] [GL ] NPOT texture support is available
[e[1;32mINFOe[0m ] [Websocket ] 2022-03-23 08:29:10 - Opening connection
[e[1;32mINFOe[0m ] [ProbeSysfs ] device match: /dev/input/event0
[e[1;32mINFOe[0m ] [MTD ] Read event from </dev/input/event0>
[e[1;32mINFOe[0m ] [ProbeSysfs ] device match: /dev/input/event0
[e[1;32mINFOe[0m ] [HIDInput ] Read event from </dev/input/event0>
[e[1;32mINFOe[0m ] [Base ] Start application main loop
[e[1;32mINFOe[0m ] [MTD ] </dev/input/event0> range position X is 0 - 799
[e[1;32mINFOe[0m ] [HIDMotionEvent] using <raspberrypi-ts >
[e[1;32mINFOe[0m ] [MTD ] </dev/input/event0> range position Y is 0 - 479
[e[1;32mINFOe[0m ] [HIDMotionEvent] <raspberrypi-ts > range ABS X position is 0 - 799
[e[1;32mINFOe[0m ] [MTD ] </dev/input/event0> range touch major is 0 - 0
[e[1;32mINFOe[0m ] [HIDMotionEvent] <raspberrypi-ts > range ABS Y position is 0 - 479
[e[1;32mINFOe[0m ] [MTD ] </dev/input/event0> range touch minor is 0 - 0
[e[1;32mINFOe[0m ] [HIDMotionEvent] <raspberrypi-ts > range position X is 0 - 799
[e[1;32mINFOe[0m ] [MTD ] </dev/input/event0> range pressure is 0 - 255
[e[1;32mINFOe[0m ] [HIDMotionEvent] <raspberrypi-ts > range position Y is 0 - 479
[e[1;32mINFOe[0m ] [MTD ] </dev/input/event0> axes invertion: X is 0, Y is 0
[e[1;32mINFOe[0m ] [MTD ] </dev/input/event0> rotation set to 0
[e[1;32mINFOe[0m ] [Websocket ] 2022-03-23 08:29:10 - Connection open
[e[1;31mERRORe[0m ] [Image ] Not found <icons/barometer/942.0_lR.png>
[e[1;31mERRORe[0m ] [Image ] Not found <icons/barometer/942.1_lR.png>
[e[1;31mERRORe[0m ] [Image ] Not found <icons/barometer/942.2_lR.png>
[e[1;31mERRORe[0m ] [Image ] Not found <icons/barometer/942.3_lR.png>
[e[1;31mERRORe[0m ] [Image ] Not found <icons/barometer/942.5_lR.png>
[e[1;31mERRORe[0m ] [Image ] Not found <icons/barometer/942.6_lR.png>
Looks like you might be the first user of the console to ever have a sea level pressure reading lower than 950 mb, which is the limit of the barometer. There is a bug here (as in any pressure below 950 should show the icon for 950), and I will get it fixed up for the next release
Thank you! So will this cure itself when the pressure returns to a higher number?
Jason HItch
Hi Jason
Such low readings made me look your station, something isn’t ok with it. Please open a support ticket. This will need a closer look.