peted-davis / WeatherFlow_PiConsole

Raspberry Pi Python console for WeatherFlow Tempest and Smart Home Weather Stations
GNU General Public License v3.0
156 stars 20 forks source link

Numpy - error when updating to newest version of PiConsole #131

Closed DMEbner closed 10 months ago

DMEbner commented 10 months ago

Hello friends!

I have been trying to the most current version of Pi Console but I keep getting error that it can't install the numpy module. IMG_7597

Numpy is loaded on my Rasp. Pi. Can anyone give me some direction?

Cheers!

peted-davis commented 10 months ago

Sorry you have run into trouble. It looks like this happens if Numpy is already installed on the Pi. To fix the issue, please open a terminal and run the following commands:

source ~/wfpiconsole/venv/bin/activate python3 -m pip install --no-cache-dir numpy==1.26.0 deactivate

Once those three commands have run, try to update the console again with wfpiconsole update

DMEbner commented 10 months ago

Thank you for the help. It says there is no such file or directory. Should I just reinstall Pi Console on my Pi?

On Sat, Nov 4, 2023 at 5:24 AM Pete Davis @.***> wrote:

Sorry you have run into trouble. It looks like this happens if Numpy is already installed on the Pi. To fix the issue, please open a terminal and run the following commands:

source ~/wfpiconsole/venv/bin/activate python3 -m pip install --no-cache-dir numpy==1.26.0 deactivate

Once those three commands have run, try to update the console again with wfpiconsole update

— Reply to this email directly, view it on GitHub https://github.com/peted-davis/WeatherFlow_PiConsole/issues/131#issuecomment-1793405259, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2F5RKWDXFDRLUQ5V5NBIH3YCYJV7AVCNFSM6AAAAAA65GGPROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGQYDKMRVHE . You are receiving this because you authored the thread.Message ID: @.***>

peted-davis commented 10 months ago

Yes, just try reinstalling. I have just pushed an update that should fix the issue you are seeing

peted-davis commented 10 months ago

This error should now be fixed in v23.11.1