Getting error when trying to install

Developers WeatherFlow PiConsole
21

Now HERE’s a Weird Anomaly for you all! Check this out. My RPi4 is still on “buster”. . . as in:

pi@piconsole:~ $ cat /etc/os-release
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODEMANE=buster
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspian.org/”
SUPPORT_URL=“http://www.raspian.org/RaspbianForums”
BUR_REPORT_URL=“Loading...”
pi@piconsole:~ $

. . .but on Friday March 3rd. . .I did the update to get the latest version that @peter put out.

My console (on Buster / Debian v10) swallowed the update JUST FINE. Had Absolutely NO Problem what-so-ever. ‘wfpiconsole’ has been running on v23.3.1 for the past 3 days. . .under the auspices of the old operating system. I guess I (or the RPi4) Lucked Out and that makes me Very Happy!

Just to make sure. . .I used Menu | Exit. . .then did ‘wfpiconsole start’ a couple of times. . .just to see what would happen. . . and it came right back up on v23.3.1 !

image
image1222×684 71.9 KB

image
image1081×581 77.5 KB

22

You are lucky!! I have been unable to find a consistent set up that worked with Pi4 and Buster. In contrast Pi4 and Bullseye works out of the box, which is why that is now the supported combination. Fingers crossed it keeps working for you!

1 Like
23

I have a Pi 4 Model B and just installed bullseye. I am trying to install but I am getting an error

pi:~ $ curl -sSL https://peted-davis.github.io/wfpiconsole | bash
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: curl - SSL CA Certificates

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

24

This is not an issue with the PiConsole. For some reason your Raspberry Pi is unable to verify the SSL certificate provided by Github. Double check that your Pi is connected to the internet and the time and date is set correctly. You can always try running the curl command without certificate checking using this command:

curl -skSL https://peted-davis.github.io/wfpiconsole | bash

This might work but will not solve the underlying problem

25

defiantly connected to the internet, date and time verified correct. when I run

curl -skSL https://peted-davis.github.io/wfpiconsole | bash

I get
bash: line 1: 410: command not found

I have never had these issues before, everything was running fine before upgrading to Bullseye.

26

ok not sure what I did other than go to the github page in the browser on my Pi. Copied the path from the website and it worked fine. not sure if just visiting the page worked or what. Up and running again. Thanks

27

I figured I’d report that I did a clean build with 32-bit Bullseye, installed PiConsole, copied over the .ini file from my previous (Buster) install, and it worked perfectly. Because I had a bunch of other software to re-install, it took around 3-4 hours total, but I think if it was just the OS and PiConsole it would have been much quicker.

This is not surprising given the work Peter’s done, but with all the “it’s not working” comments regarding the updates I wanted to pass on some good news.

1 Like
28

I’m STILL Very Lucky! Still have Linux 10 (Buster) OS on my ‘wfpiconsole’ running v23.3.1 since March 3rd. Haven’t had a Lick of trouble with it what-so-ever. . . so Why mess up a good thing by putting Linux 11 (Bullseye) on it? . . .when Buster and v23.3.1 are the Best of Friends!

2 Likes