Basic Information: Printer Model: MCU / Printerboard: klippy.log Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g.…

Except that you are trying to load a not exiting bed_mesh here: [delayed_gcode bed_mesh_init] initial_duration = .01 gcode = BED_MESH_PROFILE LOAD=default there are no additional errors in your log and also no mentioning of checkKlippyState. Try fixing this and then reboot your host to have a cle…

I just wanted to note that the latest version of Moonraker does not clear out any checkKlippyState errors even after they’re resolved and you’ve rebooted - you have to click on the “xed” out alarm symbol manually. I’m not sure if this is the optimal workflow as it can be hard to know if you’ve reso…

[image] mykepredko: I just wanted to note that the latest version of Moonraker does not clear out any checkKlippyState errors even after they’re resolved and you’ve rebooted Interesting. Never noticed this. Is there a reference? Is it just a notification or does it have a practical consequenc…

Huh. I was able to do a quick demo of this. I took a working printer.cfg and changed the pin name of an LED to somethingInvalid and then did a “Save & Restart” - the error was flagged. Next, I changed the pin back to its valid value, did a “Save & Restart” and the flag appears with the checkKlipp…

Ok, just checked myself: It is a Mainsail only thing It seems just a sticky notification that needs to be acknowledged It has no practical consequences

[image] Sineos: It has no practical consequences Well, if you’re new or not sure if you’ve fixed the problem you’ll probably end up looking for something that isn’t there. As I said, I don’t think it’s the optimal workflow - it can be lived with but it could be done better.

I agree, sometimes too much information is rather detrimental than helpful, especially if there are no real actions to take. Maybe @meteyou has some thoughts on it.

Yeah that might be because i have not been able to get a bed mesh in yet as i have been trying to fix other errors first. Like the BL Touch probe bouncing on the bed some on the second deploy please see video in my google drive too big to be an attachment 20231221_193510.mp4 - Google Drive

ohhh sry… i didn’t see this ping. I fixed this bug already. This was a wrong notification, when Klipper wasn’t running during the init process.

Init. Moonraker: checkKlippyState

General Discussion

Sineos December 21, 2023, 7:51am 4

Interesting. Never noticed this. Is there a reference? Is it just a notification or does it have a practical consequence?

Topic		Replies	Views
Moonraker does not report printer state General Discussion	3	328	April 9, 2024
Moonraker can't connect to klipper on fresh install General Discussion	9	688	April 2, 2025
Moonraker cannot connect to Klipper General Discussion	6	285	May 6, 2025
Speeder pad with legit klipper General Discussion	1	729	October 26, 2024
Moonraker can't connect to Klipper! General Discussion	8	24730	April 24, 2024

Init. Moonraker: checkKlippyState

Related topics