Jan
Jan
IIRC Klipper wrote some warnings months ago that the "default" bed mesh will no longer be loaded automatically on start up with a future release. But after a bed mesh...
For me it looks loaded. 
do you have maybe some macro "hiccup" where it somehow does a `BED_MESH_CLEAR` after a bed mesh or something?
To be creative, you could override BED_MESH_CLEAR and print an error, to test it out. but thats not a permanent solution. just locating or eliminating possibilities
since I did not use clean nozzle, it never came up on my virtual z endstop
@Frix-x could this be just avoided by checking if a bed mesh is loaded? At beginning of the processing of modules do a bed mesh clear and then check at...
@Frix-x do you want to override G28 for that? or where do you like to place "KEEP_MESH=1"?
We shouldn't program something that has moonraker update entries by itself using the configuration option "managed_services". This is referenced in the moonraker documentation [https://moonraker.readthedocs.io/en/latest/configuration/](url)
@tobi466 have you used the manual of auto z? It seems you haven't followed it correctly. What Eric says is the essence and use case of auto z
Changed the title to reflect the possible issue