RatOS expects stowable probe to be deployed before print
I've built a V-Core 3.1 with a Klicky stowable probe and I'm consistently getting "expected probe state to be deployed but is stowed (1)" error at the beginning of every print job, except for the very first one right after turning the printer on. First print jobs start and finish as expected and without any troubles, but when I start another job, it goes something like this:
11:57 Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)11:57 probe: TRIGGERED11:57 Stowing probe11:57 Probe batch mode disabled11:57 RatOS | TEMPERATURE_WAIT: Temperature for toolhead T0 reached.11:56 RatOS: please wait...11:56 RatOS | TEMPERATURE_WAIT: Waiting for sensor: extruder, MINIMUM: 150, MAXIMUM: 15511:56 RatOS: Waiting for extruder to be preheated...11:56 RatOS: Heating bed...11:56 RatOS: Pre-heating extruder...11:56 RatOS: All requested axes already homed, skipping..11:56 Probe batch mode enabled11:56 File selected
11:57 Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)11:57 probe: TRIGGERED11:57 Stowing probe11:57 Probe batch mode disabled11:57 RatOS | TEMPERATURE_WAIT: Temperature for toolhead T0 reached.11:56 RatOS: please wait...11:56 RatOS | TEMPERATURE_WAIT: Waiting for sensor: extruder, MINIMUM: 150, MAXIMUM: 15511:56 RatOS: Waiting for extruder to be preheated...11:56 RatOS: Heating bed...11:56 RatOS: Pre-heating extruder...11:56 RatOS: All requested axes already homed, skipping..11:56 Probe batch mode enabled11:56 File selected
This is fixable by simply restarting Klipper or by, well, manually picking up the probe and attaching it to the printer's toolhead. My guess is that I'm getting this behaviour because of this setting I added to the printer.cfg:
variable_end_print_motors_off: False
variable_end_print_motors_off: False
Maybe this variable breaks some macro when set to "false". Because when I set it to "true" the error above doesn't show up.