Klipper Update from the Command Line

[mykepredko]

I’m creating some setup scripts for Klipper systems and one of the things I’ve run into when using a Raspberry Pi with the “MainsailOS” provided with Raspberry Pi Imager, the version of Klipper that comes with the MainsailOS image is downlevel and I have issues building a valid .bin file.

I believe that the way to check the Klipper version number is to execute an M115 gcode command which matches what I see on Mainsail:

When I look at the Klipper documentation:

https://www.klipper3d.org/FAQ.html?h=update#how-do-i-upgrade-to-the-latest-software

The SSH command line instructions for updating Klipper are:

cd ~/klipper
git pull
sudo service klipper restart

After running these commands, the Mainsail version doesn’t change BUT the version returned by M115 does indicate that the version has been updated:

If I click on UPDATE in Mainsail, the message seems to indicate that klipper is currently up to date:

and when I close the update window, the version displayed by Mainsail seems to be correct:

I feel like I’ve probably answered my own question here; the command line instructions given in the Klipper documentation correctly updates Klipper but Mainsail does not reflect the update.

Is this a correct interpretation of what’s happening here?

[mykepredko]

After putting this out there, I realized that I should:

1. Start with a virgin MainsailOS system
2. Do the git pull process to update Klipper from the command line
3. Do a reboot and see if the Klipper version status message changes
4. If the reboot doesn’t change it: do a shutdown, power cycle and see if the status message changes

Interestingly enough, the version status message doesn’t change if you reboot or shutdown and power cycle. It only changes when you click on UPDATE.

[Sineos]

Baseline

After git pull

Same as baseline

After refreshing the version cache

My interpretation

• The versions are cached in either Moonraker or the web interfaces (no clue in which one)
• The web interfaces either:
  • Run periodic checks for new versions (no setting seems to exist to control this)
  • Need to refresh the cache manually