This guide is for TM3D Troodon 2.0 customers or anyone else connected to our klipper_elements repos that experience updating errors expressed below.
A recent Moonraker or Mainsail update has changed the validity checks for connected repos. To keep your machines updated, we have them connected to our repos. We have some custom scripts that patch issues with different klipper components and the permissions on those files change periodically when updating.
The following is for reference and not required reading for this fix.
If you have a BigTreeTech Pad 7, your machine is connected to:
https://github.com/tinymachines3d/klipper_elements/tree/troodon_2.0_pad7
If you have a TM3D KlipperBox, you machine is connected to:
https://github.com/tinymachines3d/klipper_elements/tree/troodon_2.0
The Issue
Moonraker sees a file permissions mismatch as invalid or dirty now, while previously it did not.
DO NOT RUN A HARD RECOVERY!
Running a Soft Recovery then updating results in the following errors
To resolve, scroll to the next step.
The Fix
SSH into your device. If you have never done this, do not worry. It is safe and easy.
Windows users, search for CMD to open a command prompt
macOS users, search for terminal to open a command prompt
Linux Users should already be familiar with this but it is also called terminal
For Pad 7 users, the user / passwd is biqu / biqu
For KlipperBox users, the user / passwd is pi / tm3d
You will type ssh <user>@<ip-address>, press enter then type in your <passwd> when prompted then press enter.
Only a single command is needed. Copy and paste into command line and press enter.
cd ~/printer_data/config/elements/ && git stash
You should see the following result, Saved working directory...
If you run it a second time, it won't hurt anything, but it will report back no local changes to save
Type exit and press enter. Close out the terminal window.
exit
Run updates through Mainsail as per usual and all errors should be resolved. If not, contact us for assistance.
Summary
Hopefully, this "fix" and some additionally added scripts we have created will help resolve this through Mainsail UI going forward if any other related issues arise.