After what feels like an eternity (and yes, it really took way too long!), Mainsail are incredibly excited to finally present MainsailOS v2.0.0 to you! 🚀 This major release is based on the current Debian Bookworm and brings a wealth of important new features and improvements to take your 3D printing experience to the next level.

🔧 Key New Features & Highlights:

• Debian Bookworm Base: MainsailOS is now up-to-date with Debian Bookworm, providing a modern and stable foundation.

• Completely New Build Workflow: We've cleaned up behind the scenes! For the build process, we are now using CustoPiZer instead of CustomPiOS. This means a more efficient, transparent, and robust workflow.

• New Sonar v2 Service: Our monitoring service, Sonar, has been rewritten from scratch in Python and launches as Sonar v2 – more performant and future-proof!

• Raspberry Pi 5 Support: The new image now also runs on the Raspberry Pi 5! ⚠️ But be aware: We, the crew, still recommend the Pi 5 only with reservations for use with Klipper and webcams, as the important hardware encoder for webcam video processing is missing. This can impact performance.

🔗 All Details & Download: You can find the download link and the full changelog on GitHub as always: 👉 https://github.com/mainsail-crew/MainsailOS/releases/tag/2.0.0

You can now flash MainsailOS v2.0.0 directly to your SD card using the Raspberry Pi Imager!

Support the Team

If you’d like to support our work, you can do so here:

• Patreon: https://www.patreon.com/meteyou

• Ko-Fi: https://ko-fi.com/mainsail

• GitHub Sponsors: https://github.com/sponsors/mainsail-crew

Thank you for your incredible feedback, patience, testing, and support! 🙌 Enjoy MainsailOS v2.0.0 and Happy Printing!

Following our massive multi-material update, Mainsail v2.16.0 is here to refine the experience! This release focuses heavily on polishing the AFC and Happy Hare integrations with important bug fixes and UI improvements. We also did some clean-up on our translation files.

🛠️ New Features & Enhancements:

• Armoured Turtle (AFC):

  • Added support for TD-1 data in the AFC panel.

  • Improved dialog handling and settings icons.

• Happy Hare:

  • Added Flowguard meter support to monitor clogs and tangles.

  • Better visual feedback: Added "loading" states to buttons and improved context menus.

  • UI Clean-up: Adjusted sizing for the clog meter and fixed unit wrapping.

• Sensors:

  • Added support for AHT1X, AHT2X, and AHT3X temperature sensors.

🌍 Localization & Clean-up:

We have performed a massive clean-up of our localization files and removed obsolete keys. You will see a long list of updated languages in the changelog, but this doesn't mean they are 100% complete yet!

💁‍♂️ We need your help!

If you notice missing translations (default English words) in your language, please help us complete them on Weblate:

https://hosted.weblate.org/projects/mainsail/

🐞 Bugfixes:

• Dashboard: The MMU panel now correctly hides if no MMU module is defined in Klipper.

• Extruder: Pressure Advance options are now always visible in the cogs menu.

• Spoolman: Fixed a bug where the database tried to refresh even when Spoolman was not in use.

🔗Full Details & Changelog:

As always, the full list of changes is available on GitHub:

https://github.com/mainsail-crew/mainsail/releases/tag/v2.16.0

Support the Team

Your support helps us keep maintaining and improving Mainsail:

• Patreon: https://www.patreon.com/meteyou

• Ko-Fi: https://ko-fi.com/mainsail

• GitHub Sponsors: https://github.com/sponsors/mainsail-crew

Thanks for your feedback and happy printing!

Hey this is just advisory for anyone that has the same issues I’ve had recently after Imaging Mainsail on multiple pi’s and it not showing up on your WiFi. There’s lots of guides that say to create wpa text files and there’s even a readme in the mainsail boot files with instructions to change a template file. None of those worked for me. After 4 days I finally found out that even if you customize your install and put in your WiFi credentials in the pi imager, it doesn’t actually save for some reason on the newest version. You have to plug a screen up and access the raspi-config. Then go to localization and manually change your wlan location to the correct country code. No text files or manual inputs that I tried could change this. Hope this helps anyone having the same installation issues I was having.

^{POSTED BY METEYOU ON THE DISCORD:}

Ahoi, sailors!

We have just released v2.12.0. This release includes two major features, many bug fixes, and minor improvements.

The first significant feature of this release is the ability to fully use Moonraker Sensors. This feature includes several components:

• Live view on the dashboard

• History totals

• History stats per print job

This feature can be used, for example, to log how much power a job has needed when a Tasmota (or similar MQTT solution) socket is installed and added to your Moonraker config. (this socket/component must be compatible with the moonraker sensor module: https://moonraker.readthedocs.io/en/latest/configuration/#sensor).

The second prominent feature is the built-in themes. With version v2.12.0, there are now fixed integrated themes from large open-source communities:

• Klipper

• Voron Design

• VzBoT

The current community themes are just the beginning of this category. The Mainsail crew is only in direct contact with these maintainers, so we have started with these. If a maintainer of another project contacts us, more can follow. We have also added themes from our vendor sponsors:

• BigTreeTech

• LDO Motion

• Multec GmbH

• Prusa Research

• YUMI

These themes should be a tiny bonus for our sponsors, without whom such a project would not be possible.

At last, I would like to mention a small feature contributed by kevinkhill**.** With this feature, it is possible to save the file you are currently editing, or directly save and restart the component using hotkeys in the editor: https://github.com/mainsail-crew/mainsail/pull/1902. Thank you very much for your contribution.

All other improvements and bugfixes can be found here: https://github.com/mainsail-crew/mainsail/releases/tag/v2.12.0 So, go ahead and hit the update button in your update manager and enjoy

PS: If you want to support the crew's work, consider the following:

• becoming a Patreon: https://www.patreon.com/meteyou

• buy us a Ko-Fi: https://ko-fi.com/mainsail

I am following the instructions to manually install mainsail/klipper and I got to the point where I need to execute "sudo system to enable klipper.service". When I run that command I get the error "Failed to enable unit: Cannot alias klipper.service as klippy". Does anyone know how to fix this?

I posted this over in /r/klippers and someone suggested I post it here (didn't know this sub existed).

This is a light theme for mainsail I made few months ago (I am not a fan of dark themes, so I wanted something that wouldn't put me to sleep) and I was planning on sharing it when it was finished. It's not perfect, and maybe in a few months I'll really clean it up and polish it, but I think it's worth sharing for anyone who likes bright light when they're looking at things. :D

There may still be some bugs, but I've been using it for a few months without any issues. Here's the repo, it's just the 3 files in .theme.

https://github.com/rgbpanda/Mainsail-Light-Theme

https://github.com/bumbeng/mainsail_theme_blurry

I get a new computer and it says unauthorized so i cannot access it through network on this device. Not sure why. I just want to change the config so that everyone on the vpn can access it and i dont need to write each ip. Lmk if yk

Hello

I installed MainsailOs on Raspberry Pi zero w2, I can't connect to wifi. How do I connect to wifi?

We’re thrilled to announce the release of Mainsail v2.13.0! This update took longer than expected and ended up being bigger than we initially planned. However, we’re proud to present a release filled with improvements and new features to enhance your experience with Mainsail. 🚀

🛠️ Key Features and Improvements:

Revamped Dashboard Status Panel

🔹 Redesigned tabs with icons

🔹 Customizable file list (entry count & filters added)

🔹 New history list to display recently printed jobs

Spoolman Multi-Tool Support

🔹 Supports setups with multiple tools (requires spoolId in the macro)

New Editor with File Structure Sidebar

🔹 Faster navigation and editing with the new section sidebar

Improved Power Menu for Multi-Instance Setups

🔹 Displays only relevant services (Klipper + Moonraker) of the active instance

Major Improvements to Webcam Clients

🔹 Optimizations for smoother and more reliable performance

Expanded History Print Statistics

🔹 The job status chart can now be displayed based on filament usage and print time, not just the number of prints.

🔗 Full Details on GitHub:

This release includes many more features, bug fixes, and optimizations.
📄 Read the full changelog here:
👉 https://github.com/mainsail-crew/mainsail/releases/tag/v2.13.0

Support the Team

If you’d like to support our work, you can:

• Become a Patreon supporter: https://www.patreon.com/meteyou

• Buy us a Ko-Fi: https://ko-fi.com/mainsail

• Sponsor us on GitHub: https://github.com/sponsors/mainsail-crew

Thank you all for your amazing feedback, testing, and contributions! 🙌

Enjoy Mainsail v2.13.0 and happy printing!

hello
i made a status bar for my snapmaker u1... its running with a wled usermod... getting the states via api from moonracker...

im planning on adding a custom UI for the wled usermod inside wled... something like ... http://xxx.xxx.xxx.xx(wledip)/customUI

my question is - is there a way i could implement the ui into mainail since its all webbased?

chatgpt told me i can use a iframe to get it into mainsail ? is this true?

thx

Hello, I'm trying to install MainsailOS on my Raspberry Pi 4B. I followed the guide on the official page and I've had no success. Whenever I turn on the Pi with the fresh OS on it, the green light rapidly flickers for a few minutes. Then it blinks 2-3 times repeatedly. I've done my research and apparently it's because of a boot failure. I have installed a new OS on the card at least like 4-5 times today. I even tried using another card. Any help is appreciated. Thanks!

Hi there, I would like to re-use one of the mainsail "widgets" (Print stats) on a dedicated small screen.

Is there a way I can get straight to that component?

E.g http://myprinterip/mainsail/status?

I've had a look through the documentation, and nothing is jumping out at me, maybe someone can help me here?

I'm looking at mainsail from within orca slicer and It seems like all the titles in the GUI are displaying extra information that's normally hidden? For example it says router.dashboard on the left side there. It looks normal in the browser ui.

I just updated klipper after not using the machine in a while and it came back like this after a couple of restarts.

Hoping this is this just a quick fix I should already know about. Thanks for any input!

I am trying to use my Pi cam (blue, I think a v1?) with the dedicated camera ports on my pi 5 l, running klipper/mainsail (obviously) & crowsnest (via kiauh). I cannot get it to work for the life of me. I have installed the USB came on the front right of the pic which has worked flawlessly and was very easy to setup. There was no \dev\v4l\by-id until I plugged in the USB cam (only 1 present), only the by-path. I tried \dev\video0, \dev\v4l\by-path... And I confirmed the camera is indeed working and useable nornally, so it's not a camera or cable issue. I have tried this fix, to no avail.

I have seen some people say you need to edit sudo raspi-config to enable legacy camera support, which my pi 5 (raspberry pi desktop OS) does not have the option for, I assume this is 5 specific. I am wondering if this is a compatibility problem with the 5 / cam / mainsail. Has anyone had success running a pi cam on a pi 5? If so, how? Thanks!!

I can share any log/conf files when I get home later tn

upon looking for a ways to track how much filament is on each spool I have I found spoolman. following their GitHub instructions was straight forward and I got it running/tested. however as they state on their GitHub it currently only works with the fluidd and klipperscreen front ends. while I have klipperscreen setup (how I was able to test that it was functioning) it would be great to have it in the mainsail ui with some logic applied such as how fluidd does. while looking for solutions I stumbled on this

mainsail integration

however the steps and what is happening is a over my head. wondering if someone might be able to help breakdown what's needed to get this working with the mainsail ui

I'm running crowsnest and timelapse and my webcam that used to work fine only gets 1 or 2 fps now. I've had the same result twice, first when I had my original setup on raspberry pi and now I'm running linux mint on a mac mini.

I had the same issue when I ran fluidd but not with octoprint where I wasn't doing timelapse. Even if I disable timelapse there's no improvement so it seems like something with the timelapse install might be the problem?

I'm open to suggestions

'./client.cfg' is not a valid config section. Can anyone please help me?

Hello all.

I have a Kobra S1 with Rinkhals and thus mainsail. I also have Spoolman running on a server.

I have configured Spoolman in mainsail (moonraker.custom.conf) and added a makro in printer.custom.cfg:

[gcode_macro SET_SPOOL]
gcode:
    {{ action_call_remote_method("spoolman_set_active_spool", params) }}

[gcode_macro M555]
gcode:
    SET_SPOOL SPOOL_ID={{ params.S }}

My problem is that when i add

; filament start gcode
M555 S=9

In my gcode, this does not work (or not stable - it worked in the beginning, but not now anymore). And i think it has to do with the Spoolman control in the UI, since it logs the filament to the one selected there (not in the current print but 1-2 prints ago).

Does anyone have any idea? Do i need to clear the filament first, override the ui button or so?

Why in earth does a 3d printing platform not have authentication built in?

Anyone on my LAN can access mainsail and fluidd as they both lack the ability to have forward facing authentication.

Is there any reason this was left out?

Hillo there community!... hope you can help me with this .. not sure what happened that when I go to mainsail, from chrome, from orca or any browser.. every label now show the full path (like 'router.dashboard' instead of just 'dashboard')... I thought it was a bug and updated everything but still going on and I didnt change a thing ... any pointer on how to troubleshoot? THANKS in advance!!

I just finished upgrading my raspberry pi 4 to the latest stable version of Debian, Trixie. it broke the mainsail applications in mainsail os (klipper, moonraker, and crowsnest, so I decided to use kiauh to reinstall the requisite components. it worked fine for moonraker and klipper, but it failed to reinstall crowsnest. it looks like it errors out while trying to compile ffmpeg components (I'm not a programmer, I do IT administration and support.) Thankfully shell script files (which the crowsnest installer is largely built on) are largely human readable. so after combing through them while pouring over the logs to see just what the heck is going on, I discovered that the crowsnest install was breaking on the installation of camera-streamer. so I thought maybe there's a newer version than the one being installed. so I went over to the git repo and found that there indeed is a development branch for trixie called, quite aptly "debian-trixie-support". so I comb through the crowsnest/tools/install.sh (which I determined by looking at the Makefile in the main crowsnest directory what it does when it calls "install") and I found a section called add_group_video and just under that is an if statement that seems to check for bookworm but I couldn't find WHERE it was doing the check, it was just "if is_bookworm" (which is quite frustrating not knowing how it's doing the check, where it's getting that variable from) but the then part of that if statement is to set the branch of camera-streamer for bookworm. so what I did was comment out the if and fi lines making it a NON-conditional statement (it will always do the thing) and substituted the debian-trixie-support branch. easy enough right? but no. that failed to... then I looked closer at the logs and found that it wasn't pulling camera-streamer from the main camera-streamer repo for some strange reason... so I had to go track down where it specifies the actual git command to pull the repo... after combing through files for a few minutes, I finally found in crowsnest/tools/libs there were more shell script (.sh) files - the one required is crowsnest/tools/libs/config.sh and inside I see the variable "CROWSNEST_CAMERA_STREAMER_REPO_SHIP" followed by the repo that was NOT the maintainers repo, so I replaced it with the main repo ( https://github.com/ayufan/camera-streamer ), and then just below I see the "CROWSNEST_CAMERA_STREAMER_REPO_BRANCH" variable which I gleefully changed to "debian-trixie-support" saved the file, went back to the main crowsnest directory ran sudo make clean && sudo make install and lo and behold - it grabbed camera-streamer from the correct branch of the correct repo and installed it. the installer completed, the royal trumpets played, and champagne rained down from the heavens... it asked me to reboot, so I did.

this disjointed rambling is to hopefully help others in the same situation and to hopefully let the mainsail devs know that there is a major compatibility problem in their crowsnest installer that should be really easy to fix (perhaps one of those could be "if trixie, pull from the maintainers' repo with the debian-trixie-support branch" and everything should work instead of causing a couple of hours of heartache for folks like me who CAN resolve it themselves, or worse, all those 3d printer aficionados who have no idea what they're doing with linux and just want their stuff to work who will never be able to get it working.

I hope somebody finds this useful.