I received a system update and now the WF Pi console is not receiving any data, no wind, no temp, nothing in five of the six frames. Is anyone else having this issue?
FYI… After the install was done, the update icon top right keeps showing up after I reboot the system. I tried to update again but the system states it is up to date. But the update icon returns.
Peter,
Thanks for the reply but I have removed the PI console and ordered the new console from Tempest, not that I wanted too, but it’s because of the past issues with system updates, data not matching the App and after the last update (yesterday), no data displayed. I’ve made no changes to the configuration other than installing the updates. I’m not sure if the updates are the issue with the operating system of the PI or updates with PI Console updates.
Peter,
The PI Console did work great! But for some reason the last few updates, either PI operating system or the WF PIConsole software updates, maybe some of both caused the issue, I don’t know.
Thank you for your support and for the development of the WF PiConsole, I’m going to miss some of the data it provides that the new one does not.
Cheers,
Reggie
Pete,
I thought I would try to re-build the Raspberry PI4 by installing a new OS load and a new wfpiConsole load. The Os install loaded with no issues and updated but I’m not sure if I’m doing something wrong because on the wfpiConsole install/load I get an error stating “Unable to install Kivy Python Library”. I’ve tried several times with the same results.
It is Pi OS 32-bit Debian Bookworm and as for providing the error transcript, someone will need to provide instructions on how to copy the information from the pi window into a memory stick so I can attach it to an email. I don’t know how.
If you provide ‘which’ PiOS image you are trying, perhaps we can recreate your issue. If you look at https://www.raspberrypi.com/software/operating-systems/ exactly which one are you running ? Is it the ‘Raspberry Pi OS with desktop’ dated 13 May 2025 ? Unfortunately there have been multiple releases since the first bookworm release, so I have to ask for specifics.
The Pi OS release date is 13 May 2025, 32-bit, Debian Bookworm.
According to the wfpiconsole installation guide, all I needed to do is run the script provided in the instructions. FYI… I had the wfpiconsole working but some update or change took place then it stop displaying data. I didn’t make any changes to the system to cause the issue I was having. All I am/was trying to do is start fresh with a new Pi OS load and new wfpiconsole load because of the problem. It was easy the first time getting the wfpiconsole setup but this is becoming more involved and frustrating.
Sorry you’re having no luck! @vinceskahan is right that generally I need to see the full error transcript (a photograph is fine!), but I think in this instance you might have run into the same issue that someone else had a while back. They seemed to be the only one, but maybe the error is now consistent.
Please run this command and then try installing the console again:
Pete,
Thank you for the magic command, that fixed the problem with loading the Kiyv library and all the errors that came with that. I don’t understand this software magic and never have even thou I’ve tried but very glad there are those that do.
I just reimaged a SD card and did an installation without visible issues…
pi@raspberrypi:~ $ curl -sSL https://peted-davis.github.io/wfpiconsole | bash
[✓] Root user check passed
[!] Architecture check warning (arm64)
[✓] OS check passed (Debian GNU/Linux 12 (bookworm))
[✓] Raspberry Pi check passed (Raspberry Pi 4 Model B Rev 1.1)
[!] WARNING: unsupported architecture or Raspberry Pi detected
No support is available for errors encountered while running
the PiConsole
================================
Installing WeatherFlow PiConsole
================================
[✓] Checking for updated packages
[i] 186 updated packages available. Use 'sudo apt upgrade' to install
[i] WeatherFlow PiConsole dependency checks...
[✓] Checking for git
[✓] Checking for curl
[i] Checking for rng-tools (will be installed)
[✓] Checking for build-essential
[✓] Checking for python3-dev
[✓] Checking for python3-pip
[✓] Checking for python3-setuptools
[i] Checking for libssl-dev (will be installed)
[i] Checking for libffi-dev (will be installed)
[i] Checking for libatlas-base-dev (will be installed)
[i] Checking for libopenblas-dev (will be installed)
[i] Checking for jq (will be installed)
[✓] Installing Python virtual environment
[i] Installing WeatherFlow PiConsole Python modules...
[✓] Updating Python package manager
[✓] Installing Python module websockets
[✓] Installing Python module numpy
[✓] Installing Python module pytz
[✓] Installing Python module tzlocal
[✓] Installing Python module ephem
[✓] Installing Python module packaging
[✓] Installing Python module cryptography
[✓] Installing Python module pyOpenSSL
[✓] Installing Python module certifi
[i] Kivy Python library installation check (will be installed)
[✓] Installing Kivy Python library
[✓] Updating Kivy configuration for touch screen
[✓] Installing latest version of WeatherFlow PiConsole: v25.2.1
[✓] Copying service file to autostart directory
============================================
WeatherFlow PiConsole installation complete!
Start the console with: 'wfpiconsole start'
============================================
```
I found that the installation didn’t upgrade 200+ packages to today’s version, since many upgrades have happened since the May 13 date the raspi image was created, so I did so manually….
sudo apt upgrade
sudo apt update
and reboot to make it take effect
Just as a test vs a fully patched up image, I renamed the wfpiconsole directory to move it aside and did ‘another’ wfpiconsole installation which also worked fine. So I can’t recreate any issues on a pi4 here.
I ‘do’ have zlib1g-dev installed here but not libjpeg-dev. The os I installed was “Raspberry Pi OS with desktop” dated 13 May 2025.
Thanks for doing this. Maybe there is a difference in the 32 and 64 bit images. Yours (the 64 bit) didn’t error, but the 32 bit did. Either way, I’ll just add those two packages to the dependencies in the install script