New OctoPi Release: 1.1.0

Guy Sheffer has just released OctoPi 1.1.0 - big thanks to him and also to everyone who helped test the release candidates and the nightly builds that went into this and reported back!

OctoPi 1.1.0 contains the following changes (see also its changelog):

• Raspberry Pi 5 support #823
• Beta support for Le Potato AML-S905X-CC
• Images uses Debian bookworm
• Due to bookworkm /boot/config.txt has moved to /boot/firmware/config.txt #220
• Support changing default user name on rpi-imager
• Move octoprint python virtualenv to /opt/custompios/oprint and add a symlink e62bada2
• Dropped support for wpa supplicant due to raspberrypi/bookworm-feedback#72
• New NetworkManager headless support added, its pretty basic for now since it is expected most people configure the wifi via rpi-imager. There is a new wifi.nmconnection file in the /boot/firmware folder that lets you configure wifi headless. Its more limited at the moment than the wpa supplicant version
• Remove camera ID 046d:0825. Fixes #759
• Fixed issue with webcam not working #837
• Fixed wifi blocking guysoft/CustomPiOS@e553cad7
• Network check has been fixed #840 (Thanks @david-forster10)
• Updated install-desktop 430a00eba
• Remove network monitoring (networkcheck) which only works on wpa-supplicant ea5d502b
• switch to modern OS dependencies for latest numpy versions bf506863

Please note that the mjpg-streamer included on OctoPi 1.1.0 does not support Raspberry Pi Camera v3/libcamera, and sadly camera-streamer used for the new camera stack currently refuses to compile. We are looking into that, but it might be a while until an image with the new camera stack based on OctoPi 1.1.0 will be available. It might actually even be necessary to completely switch horses there and go with a different streaming solution altogether.

You can download OctoPi 1.1.0 from the Raspberry Pi imager and of course the download page. If you are asking yourself how to update from an earlier version of OctoPi, please read on.

“How do I update?”

There is currently no way to update from earlier OctoPi versions to a new version of that image. It’s not strictly necessary though - a new image basically means that if you have to setup a new instance you’ll start at a newer version of everything bundled with the image. Anything included on the image however can also be kept up to date without having to reflash. OctoPrint will have prompted you to update itself and will continue to do so, and most of the image itself can be kept up to date like every other RaspberryPi OS image.

The 1.0.0 image still was based on Debian Bullseye however, which is already on its way towards end-of-life. It therefore would note be a bad idea to create a backup, reflash and restore to run off the new image. If you want to update, read here on how to create a backup of OctoPrint which you can apply after reflashing.

Confused about the difference between OctoPi and OctoPrint? Read this!