Klipper firmware update
How to update Klipper and all G1OS components (Mainsail, Moonraker, Crowsnest, GingerConfigs) via the Update Manager in the G1OS dashboard.
When to do it
Section titled “When to do it”- After a fresh G1OS installation
- Periodically to get the latest Klipper features and stability fixes
- When support instructs you to update
Prerequisites
Section titled “Prerequisites”- Printer powered on and connected to the same network as your computer
- Access to
http://g1os.local
Step 1 — Connect to G1OS
Section titled “Step 1 — Connect to G1OS”- Open a browser and go to
http://g1os.local - The G1OS (Mainsail) dashboard appears
Step 2 — Check for updates
Section titled “Step 2 — Check for updates”- Go to the Machine section in the left sidebar
- In the Update Manager tab, click the refresh arrow (top right of the widget) to check for the latest versions
- Components showing UPDATE (orange) have a newer version available; those showing UP-TO-DATE (grey) are current
Step 3 — Start the update
Section titled “Step 3 — Start the update”- Click UPDATE ALL COMPONENTS
- A confirmation dialog appears — it may show warnings for Crowsnest and Moonraker (normal — these require manual config review in some edge cases)
- Check “I understand the risks” and click START UPDATE
- G1OS automatically downloads and installs all updates
Step 4 — Reboot and verify
Section titled “Step 4 — Reboot and verify”- Wait for the update process to complete — the printer performs a firmware restart automatically
- After the firmware restart, perform a manual reboot: click the power icon (top right) → Reboot (under Host Control)
- Once rebooted, re-open
http://g1os.localin a fresh browser tab - Open Update Manager again and verify all components show UP-TO-DATE
Final verification
Section titled “Final verification”All components in Update Manager show “UP-TO-DATE”. The dashboard loads normally and temperatures are visible.
- After major G1OS updates, also follow Migration to new Configurator if prompted by an “INITIALIZE PRINTER” button on the dashboard
- If
g1os.localdoesn’t load after reboot, wait 60 s for the Raspberry Pi to fully boot and retry