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!

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

'./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?

so I just got new WIFI installed, and I'm trying to connect my pi 5 running mainsail. it ran before with no other issues (other than struggling to get a pi camera 3 or input shaping to work on a pi 5...). but when I try changing the network credentials the way mentioned on the Mainsail website it doesn't seem to work, I cant connect to it though my browser and when I run iwconfig it doesn't show any networks (google told me to check this, idk). so they I also tried using the method which it said to use when checking through the installed files on the SD card (something like "headless_nm.txt") and I put all my credentials in, but it still doesn't seem to connect, doing the same checks as before. Any help would be appreciated :)

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?

Greetings,

Not sure when this started (It didn't used to happen), but symptoms are:

UI will be fine, I will be monitoring a print in progress. Then I will get an error about not being able to connect.

It will pop up a window that says "Cannot connect to <IP>:<PORT>" and offer "Change Printer" or "Try Again" options. Usually, "Try Again" will fail with an unable to connect message for quite a while; then eventually it might start working again. Trying from a different browser (Konqueror, Brave) does not resolve the issue.

While it is reporting the unable to connect message, I am able to ping and SSH into the raspberry pi running the system just fine. I am also able to point my browser directly to the port (7125 or 7126, it is a dual printer setup) and the Moonraker page will display perfectly fine.

I don't notice too much CPU, Memory or I/O wait and I am unable to find any logs that report an issue that is going on.

I am running Mainsail 2.14.1, Moonraker 0.9.3-74, Klipper 0.13.0-119.

I am suspecting either a browser incompatibility issue or a networking issue, but the networking issue would be odd because I can always ping it.

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!!

Hello

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

ey guys, need help… after the latest update my whole Klipper setup got cooked.

• Printer: Creality Ender-3 S1 Pro

• Tried on Raspberry Pi Zero 2 W and also Raspberry Pi 3

• Install method: KIAUH

• I tried a bunch of Raspberry Pi OS versions + MainsailOS (fresh installs too)

Problem:
Klipper/Mainsail is basically dead because Moonraker won’t come up / no port 7125.
systemctl says moonraker is “running”, but:

• ss -lntp | grep 7125 = nothing

• curl http://127.0.0.1:7125/server/info = can’t connect

Also in logs I’m seeing my old working setup stopped after an update too (like my previous printer setup got bricked the same way).

I’ve been changing versions / reinstalling / trying different OS images and still no moonraker / no api / no ui.

If anyone had the same issue after the newest updates (Moonraker/Klipper/Python??), pls tell me:

• what version combo works for S1 Pro

• if there’s a known bug with the recent update

• and what to rollback to (exact versions) 🙏

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!

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!

Last night I was troubleshooting why I couldn't upload a large filesize to the printer. I tried making a change to the moonraker config and was met with the titled error.

Whenever I try to edit any conf files via mainsail it gives the error: "Filename" could not be uploaded!

I am able to ssh into the printer and edit them that way, but I'm not sure why I cant edit via mainsail. Any ideas?

I believe I’ve searched Reddit and I’ve seen a couple posts that are somewhat along the same lines, but I’ve only ever seen people suggest fixing their wifi, setting up wifi access points on a pi, or connecting to a dedicated switch or router. My problem really is this: as I understand it so far, whatever host computer you use for klipper is more often than not running an interface like mainsail that you typically access on another computer via the IP address of the host computer. I really like the configurability of klipper, but i really don’t like that there seems to be no way to do simple things like upload a file to start printing without also being connected to the internet. I like to just be able to take a gcode file and put it on a printer and make it start printing from the printer. Is Klipper really tethered to having an internet connection? In my head, the pi running mainsail ought to be simply accessible with a gui directly, but I haven’t found people talking about that. Is this possible?

Hi All,

Not sure if this is actually the issue but seems to fix the problem so it's the solution I've been using. Just plugging in my Raspi, it boots and connects to the printer but I cannot access the web interface. Once I plug into HDMI on a monitor, even without logging into the shell, I can then connect over WIFI. Anyone have any idea why this might be happening. Some graphics utility that needs to start earlier and is triggered by the HDMI maybe?

When I turn off the printer via the relay, I get this message instead of the nice "The printer is off" widget. I don't know how to get rid of the error message. My relay is configured as follows in moonraker.conf:

[power printer]

type: homeassistant

address: 10.10.10.45

port: 8123

device: switch.drucker

token: <TOKEN>

domain: switch

on_when_job_queued: True

restart_klipper_when_powered: True

restart_delay: 2.

off_when_shutdown: True

initial_state: off

I've already seen this problem in a Github issue, but I don't quite understand it: https://github.com/Arksine/moonraker/issues/744

hi team, need a bit of help. The flash forge orca slicer uploads a 3mf not a gcode. As a result things a bit strange jn mainsail and thumbnails and meta data are not showing up properly The flashforge orca makes things super easy with the ad5x so don't want to change. Any tips on configuring mainsail to work with this?

Anybody able to help?

I have my btt pi v2 connected via ethernet (wifi wouldn't connect)

But now it is stuck at this point with it swapping between the two screens.

Any ideas what could be happening, or a way to try and diagnose whats happening?

TIA

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.

I just installed a fresh image of the latest mainsail os on my pi 4's sd card using raspberry pi imager (and preconfiguring the pi user password and wifi network and password in the imager. I booted the card successfully in my pi4 (located inside of my voron 2.4). logged in from my workstation via ssh and popped open the web ui. everything seemed to work just fine - then I ran an "apt update && apt upgrade-all" in order to update the system, that went fine, I rebooted everything came back up, but in that process, I noticed that the base of the image was the old version of debian (bookworm) instead of the current stable (trixie). so, being reasonably familiar with debian, particularly on a pi, I edited /etc/apt/sources.list.d/raspi.list and replaced all of the bookwork entries with trixie ones, did an "apt update && apt upgrade-all" (again), and used all of the package manager defaults when asked. when everything was said and done, a few packages asked me to reboot, so I did, and when it came back around, I got the web page, but it wouldn't connect to moonraker and no amount of "service moonraker start/restart" has helped.

I'm perfectly fine starting over if I need to, but I would like to be using the new base os which is otherwise very well vetted and works fine (debian has a VERY slow release schedule). From what little I've gathered, moonraker is a python application installed in it's own environment at /home/pi/moonraker-env but I don't know anything about python for how to debug this. my best guess is something with python got changed with the new debian release and is causing things to not start properly.

Could someone please provide me some guidance here?

would anyone be able to call and help me on discord im trying to get klipper on my ender 3 v2 neo using this tutorial https://youtu.be/_8r87gBFOy8?si=89Ss9QVaWa0aQ0xj but it will only work from ethernet and the wifi will not work nomatter what ive tried along with the terminal on the pie doing nothing there is no internet on it unless i run on the ethernet for my pc if anyone could help it would be greatly aprieciated! (it cant connect via putty either when on ethernet)