Update 7.1.2022 (final fix)
I have now released two separate packages on our normal repository for both bullseye and buster.
Our install script should automatically choose which repository you can use.
In order to install picockpit-client on both Raspberry Pi OS Bullseye and Raspberry Pi OS Buster please simply run the following command on your Pi:
bash -c "$(curl -k -s https://picockpit.com/setup.sh)"
The bullseye version currently is LOWER than the buster version (2.2.3 for bullseye vs. 2.2.4 for buster). Bullseye will also currently report 2.2.0 in the package name and for apt-get purposes.
There is a minor change in the BME688 driver which should not impact bullseye users.
The two Raspberry Pi OS revisions need to have different version numbers for the repository to work properly, therefore we are currently leaving things as they are.
Please let us know in the comments if you are experiencing issues.
During the installation you will see (on bullseye):
### Checking for the latest available client version with the API …
### Your client version is: 2.2.3
### The latest available version is: 2.1.11
### The minimum recommended version is: 2.1.11
### If you would like to upgrade, run the following on your command line:
Note that the version mismatch of 2.2.3 and 2.1.11 is due to the API information not having been updated yet – I wanted to push this out as soon as possible, and will fix this in the coming days.
I have removed the manual .deb download possibility (as per the workaround on the 23.12.2021), to avoid users being stuck on that version. If you have already installed the package in this way, please run our install script again to set up the correct package sources on your system.
Update 23.12.2021 (temporary workaround)
We have released the package as a download for Raspberry Pi OS Bullseye, for the time being (another fix needs to be put in place for it to be properly released to the repository).
The package for Bullseye is hosted here:
The download has been removed on the 7th of January, as we have now fixed the package repository, and full support for Buster and Bullseye is available directly.
You can install it by following the following commands:
sudo su # the below will remove picockpit-client from your Pi if it is installed apt-get purge picockpit-client cd /tmp wget https://download.pi3g.com/temp/picockpit-client_2.2.0_armhf.deb apt-get install ./picockpit-client_2.2.0_armhf.deb # finally run the picockpit-client to connect it to PiCockpit.com # have your API key ready picockpit-client connect --yes
Please let us know if there’s problems with this procedure. We apologize for the inconvenience – hopefully in a couple of weeks we will have the install process return to be fully automated.
Raspberry Pi OS Bullseye was released a couple of days back.
I’ve had a bug report from a user who says the PiCockpit installer fails on Bullseye.
The error which occurs is currently this:
ModuleNotFoundError: No module named 'picockpit_client'
30.11.2021 Note: the bugfix given below does NOT work, we’re working on another solution, see below.
I’ve released a hotpatch into the installer script ( https://picockpit.com/setup.sh ) which should hopefully take care of that. If you want to run the installation manually, please run the following command first:
sudo ln -s /usr/bin/python3 /usr/bin/python3.7
This will create a symlink for python3.7 to your actual python3 binary. As Python is downward compatible, this should be safe.
Please report any other problems back to me here in the comments, and I’ll look into it. Be sure to include the error output which you see on your console.
We are working on a new picockpit-client release, and will test Raspberry Pi OS Bullseye compatibility (while retaining Buster compatibility) in it. It will also have a bugfix for BME688 IAQ being static at 25, and DigitalNose, an AI-enabled smell sensing app.
The new functionality has been implemented, but we are still preparing the package and ensuring compatibility with Bullseye at the time I write this. Hopefully we will have a release until the end of the month – in the meantime please continue to report any errors here.
We’re getting closer to a new release. Hopefully, we will be able to release it soon (probably by mid-December). We will keep you updated here.