Moonraker issues after swapping new pi and backup restored

[SamppaD]

Hi. I need some help here. Im in process of replacing all electronics on my Voron. Decided to swap also new pi with nwme ssd ,reinstall mainsail os and before that was done i backup my config files and moonraker files. Followed the maisail installation guide. Well installation went fine but after rebooting the Voron got multiple errors from Moonraker regarding update manager. I restored  all config files  and search the internet for solution but no luck. Can anyone help? Here is summary of the errors i get:

 Moonraker warning
[update_manager]: Failed to load extension mobileraker: Invalid path for option `path` in section [update_manager mobileraker]: Path `/home/pi/mobileraker_companion` does not exist

Unparsed config option 'origin: https://github.com/Clon1998/mobileraker_companion.git' detected in section [update_manager mobileraker]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Unparsed config option 'primary_branch: main' detected in section [update_manager mobileraker]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Unparsed config option 'managed_services: mobileraker' detected in section [update_manager mobileraker]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Unparsed config option 'virtualenv: ~/mobileraker-env' detected in section [update_manager mobileraker]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Unparsed config option 'requirements: scripts/mobileraker-requirements.txt' detected in section [update_manager mobileraker]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Unparsed config option 'install_script: scripts/install.sh' detected in section [update_manager mobileraker]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.
 

[SamppaD]

I removed moonraker files and reinstall it but errors are still present. Mobileraker error got fixed but got moonraker issues. Here is the moonraker log.

 

 

moonraker log.log

Edited December 6, 2025 by SamppaD
Update

[SamppaD]

Fixed most of the issues with moonraker and mobileraker by removing all the moonraker and mobileraker files and re-installing it with Kiuah. Only one left is this one

 Moonraker warning
Unparsed config section [timelapse] detected...

 

[mvdveer]

3 hours ago, SamppaD said:

Fixed most of the issues with moonraker and mobileraker by removing all the moonraker and mobileraker files and re-installing it with Kiuah. Only one left is this one

 Moonraker warning
Unparsed config section [timelapse] detected...

Comment out / Delete  all old sections of [Timelapse] in moonraker.conf.  Re-install timelapse,  and hopefully errors will go. Moonraker is fine, it just does not recognise certain configurations - Mobileraker and Timelapse in this instance

[NikosSprocket]

Remove from the moonraker.cfg any sections having a header:

[mobileraker]

[timelapse]

[SamppaD]

Hi. Thats exactly what i had to do,last night got it to work. Finally Voron got new electronics all motors,mainboard,steppers drivers,new pi with nwme ssd,power supply. I just swap all the shit so to speak. One thing i just didn't manage to get working is Octopus 723 550 mhz board. I had to put spare 429 in my voron. 
Made the changes to config file based on BTT github recommendations,resulting in power on to hotend after reboot,no output to HE1 SSR control. And by the way this 550Mz advertised board is not what was advertised. Klipper reports 520Mhz for cpu speed. Contacted BTT but i dont think i would get any help from them,as they are always saying we will get back to you but they never do. It looks like btt provided information is not correct.

I was thinking to add a script to report when my chamber fume filter needs replacement and found some air filter.cfg online but there is recommendation that 

[save_variables]` must be present in your configuration in order for this to work. for example:
# [save_variables]
# filename: ~/klipper_config/saved_variables.cfg

Where this file is supposed to be,I couldn't find it?

Edited December 7, 2025 by SamppaD

[mvdveer]

8 hours ago, SamppaD said:

[save_variables]` must be present in your configuration in order for this to work. for example:
# [save_variables]

It is a file the script uses to reference the variable in the script. This file normally resides in the same folder as all the other configuration files. See if you can find a "variables.cfg" file where you downloaded the script from, then add that to a file called saved_variables.cfg and add to you zipper.cfg file

[mvdveer]

Found this on GitHub. Can possible be adapted to monitor fumes rather than runtime or interval.

Klipper_Filter_monitor

Here is another that has variables defined:

Klipper_Filter_Timer

[NikosSprocket]

That's great!

The file does not exist; must be created.

Login to your Voron via ssh and type the command:

touch ~/printer_data/config/variables.cfg

That will create an empty file at the proper position. The one you stated is a very old Klipper setup.

Then in your printer.cfg you can enter:

[save_variables]
filename: ~/printer_data/config/variables.cfg

 

Edited December 7, 2025 by NikosSprocket

[NikosSprocket]

FYI

Since Klipper version 12 and after, all the CFG files officially are located at ~/printer_data/config/ when they used to be at ~/klipper_config/.

If your Klipper is version 13.x I highly recommend moving all your CFG files from ~/klipper_config/ and re-configure printer.cfg to reflect that.

Eventually you want to have an empty ~/klipper_config/  directory and for final step remove it by executing "rm -d test". If the directory is NOT empty, it will aboard the delete command and give you an error 

[SamppaD]

16 hours ago, NikosSprocket said:

FYI

Since Klipper version 12 and after, all the CFG files officially are located at ~/printer_data/config/ when they used to be at ~/klipper_config/.

If your Klipper is version 13.x I highly recommend moving all your CFG files from ~/klipper_config/ and re-configure printer.cfg to reflect that.

Eventually you want to have an empty ~/klipper_config/  directory and for final step remove it by executing "rm -d test". If the directory is NOT empty, it will aboard the delete command and give you an error 

Hi. Thanks for the tip. Already running klipper 13 ,and all .cfg files are already at ~/printer_data/config/  so Im good there.

Thanks Nikos 

Edited December 8, 2025 by SamppaD

[SamppaD]

18 hours ago, mvdveer said:

Found this on GitHub. Can possible be adapted to monitor fumes rather than runtime or interval.

Klipper_Filter_monitor

Here is another that has variables defined:

Klipper_Filter_Timer

Thanks i got this one to work without issues Klipper_Filter_Timer . Thanks to everyone for helping 

[SamppaD]

On 12/8/2025 at 1:28 AM, NikosSprocket said:

FYI

Since Klipper version 12 and after, all the CFG files officially are located at ~/printer_data/config/ when they used to be at ~/klipper_config/.

If your Klipper is version 13.x I highly recommend moving all your CFG files from ~/klipper_config/ and re-configure printer.cfg to reflect that.

Eventually you want to have an empty ~/klipper_config/  directory and for final step remove it by executing "rm -d test". If the directory is NOT empty, it will aboard the delete command and give you an error 

Hi. Nikos I was looking at the old ~/klipper_config/ location and there is only examples of .cfg files in that folder. Can this be deleted directly and then use rm -d test to remove the directory?

[SamppaD]

Hi to everyone. After testing Klipper filter timer I tried to install Klipper filter monitor  as it seems like a better option including update manager but unfortunately getting internal error from klipper after install. Checked the github site and found some solution that had the same error code,basically installer didn't write correct file location for the plugin..so i run the following in ssh
cd ~/printer_data
mkdir plugins
cd plugins/
mkdir filter_monitor  but this didn't work,internal error is still reported after reboot
For now installed Klipper_Filter_Timer and this works fine. Does anyone know how to get filter monitor working..