PiCockpit on Raspberry Pi OS Bullseye
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)"Note:
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.
Note 2:
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.
Note 3:
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:
https://download.pi3g.com/temp/picockpit-client_2.2.0_armhf.deb
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.
Historic information
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.
Update 15.11.2021:
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.
Update 30.11.2021
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.
Get Module not Found Error
The following NEW packages will be installed:
picockpit-client
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/10.7 MB of archives.
After this operation, 47.4 MB of additional disk space will be used.
Selecting previously unselected package picockpit-client.
(Reading database … 99751 files and directories currently installed.)
Preparing to unpack …/picockpit-client_2.1.13_armhf.deb …
Unpacking picockpit-client (2.1.13) …
Setting up picockpit-client (2.1.13) …
Successfully updated /usr/share/picockpit-client/bin/python3
picockpit-client.service is a disabled or a static unit not running, not starting it.
Traceback (most recent call last):
File “/usr/bin/picockpit-client”, line 5, in
from picockpit_client.picockpit_client import main
ModuleNotFoundError: No module named ‘picockpit_client’
Thank you for the feedback, we will investigate it!
Thank you for the feedback – we have now published a separate package for Bullseye, which you need to download manually currently. I’ve updated this page with a guide on how to do it. Please let me know if it works for you.
sudo picockpit-client connect –yes
Traceback (most recent call last):
File “/usr/bin/picockpit-client”, line 5, in
from picockpit_client.picockpit_client import main
ModuleNotFoundError: No module named ‘picockpit_client’
Thank you for the feedback – we have now published a separate package for Bullseye, which you need to download manually currently. I’ve updated this page with a guide on how to do it. Please let me know if it works for you.
Hallo,
bei mir geht es leider nicht mit dem aktuellen Fix.
Hit:1 http://repository.picockpit.com/raspbian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists… Done
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
picockpit-client is already the newest version (2.2.0).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Traceback (most recent call last):
File “/usr/bin/picockpit-client”, line 5, in
from picockpit_client.picockpit_client import main
ModuleNotFoundError: No module named ‘picockpit_client’
Hi Ben,
ich habe gerade es für den normalen Installationsprozess mit unserem one-liner sowohl für Buster als auch Bullseye ermöglicht. Kannst Du bitte gemäß der Anleitung hier installieren?
https://picockpit.com/raspberry-pi/installation-of-picockpit/
Nachtrag:
bitte führe vorher
sudo apt-get purge picockpit-client
aus, um das falsche Paket von Deinem System zu entfernen – das Paket das Du nutzt ist für Buster, nicht Bullseye
Leider ist Python nicht 100 % aufwärtskompatibel … daher mussten wir zwei verschiedene Pakete für Bullseye und Buster bauen.
Dein System ist Bullseye, daher brauchst Du das Paket aus unserer Bullseye Repository. Da dieses die gleiche Versionsnummer wie das von Dir bereits installierte Paket hat musst du es erst komplett von Deinem System entfernen.
Entschuldige bitte die Umstände.
Hallo,
bin Pi Neuling, und habe ein Rb Pi 4 Modul B 8GB (Rev. 1.5 (d03115)), und bekomme keinen Zugriff auf PiCockpit bzw. habe keine Möglichkeit den API Key einzugeben. Was mache ich falsch?
bash -c “$(curl -k -s https://picockpit.com/setup.sh)”
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2789 100 2789 0 0 32430 0 –:–:– –:–:– –:–:– 32430
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
OK:1 http://security.debian.org/debian-security bullseye-security InRelease
OK:2 http://deb.debian.org/debian bullseye InRelease
OK:3 http://archive.raspberrypi.org/debian bullseye InRelease
OK:4 http://deb.debian.org/debian bullseye-updates InRelease
OK:5 http://repository.picockpit.com/raspbian bullseye InRelease
Ign:6 http://repository.picockpit.com/raspbian stretch InRelease
Ign:7 http://repository.picockpit.com/raspbian Bullseye InRelease
Fehl:8 http://repository.picockpit.com/raspbian stretch Release
404 Not Found [IP: 88.99.237.140 80]
Fehl:9 http://repository.picockpit.com/raspbian Bullseye Release
404 Not Found [IP: 88.99.237.140 80]
Paketlisten werden gelesen… Fertig
E: Das Depot »http://repository.picockpit.com/raspbian stretch Release« enthält keine Release-Datei.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
E: Das Depot »http://repository.picockpit.com/raspbian Bullseye Release« enthält keine Release-Datei.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
N: Das Laden der konfigurierten Datei »main/binary-arm64/Packages« wird übersprungen, da das Depot »http://repository.picockpit.com/raspbian bullseye InRelease« die Architektur »arm64« nicht unterstützt.
W: Ziel Packages (main/binary-arm64/Packages) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:4
W: Ziel Packages (main/binary-armhf/Packages) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:4
W: Ziel Packages (main/binary-all/Packages) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:4
W: Ziel Translations (main/i18n/Translation-de_DE) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:4
W: Ziel Translations (main/i18n/Translation-de) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:4
W: Ziel Translations (main/i18n/Translation-de_DE.UTF-8) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:4
W: Ziel Translations (main/i18n/Translation-en) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:4
W: Ziel Packages (main/binary-arm64/Packages) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:5
W: Ziel Packages (main/binary-armhf/Packages) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:5
W: Ziel Packages (main/binary-all/Packages) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:5
W: Ziel Translations (main/i18n/Translation-de_DE) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:5
W: Ziel Translations (main/i18n/Translation-de) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:5
W: Ziel Translations (main/i18n/Translation-de_DE.UTF-8) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:5
W: Ziel Translations (main/i18n/Translation-en) ist mehrfach konfiguriert in /etc/apt/sources.list.d/picockpit.list:3 und /etc/apt/sources.list.d/picockpit.list:5
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Die folgenden NEUEN Pakete werden installiert:
picockpit-client:armhf
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen noch 0 B von 10,5 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 46,5 MB Plattenplatz zusätzlich benutzt.
Vormals nicht ausgewähltes Paket picockpit-client:armhf wird gewählt.
(Lese Datenbank … 92889 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von …/picockpit-client_2.2.0_armhf.deb …
Entpacken von picockpit-client:armhf (2.2.0) …
picockpit-client:armhf (2.2.0) wird eingerichtet …
Successfully updated /usr/share/picockpit-client/bin/python3.9
picockpit-client.service is a disabled or a static unit, not starting it.
Traceback (most recent call last):
File “/usr/bin/picockpit-client”, line 6, in
from picockpit_client.picockpit_client import main
File “/usr/share/picockpit-client/lib/python3.9/site-packages/picockpit_client/picockpit_client.py”, line 4, in
from picockpit_client.daemon_mode import DaemonMode
File “/usr/share/picockpit-client/lib/python3.9/site-packages/picockpit_client/daemon_mode.py”, line 13, in
from com_picockpit import plugincontroller as ComPicockpitPlugincontroller
File “/usr/share/picockpit-client/lib/python3.9/site-packages/com_picockpit/plugincontroller.py”, line 1, in
import com_picockpit.core.core as ComPicockpitCore
File “/usr/share/picockpit-client/lib/python3.9/site-packages/com_picockpit/core/core.py”, line 4, in
import netifaces
ModuleNotFoundError: No module named ‘netifaces’