[BUG]M702 (Filament unload) sometimes triggers M600 (filament change)

[Its-my-right]

Printer type - MK3s
Printer firmware version- 3.9.2

MMU Upgrade - No

SD card or USB/Octoprint
Octoprint

Describe the bug
When I use M702 via octoprint (well, via a button mapped on octodash), sometimes it behaves well (unload and that's it), and sometimes, after the unload, the head is parking like for a filament change, and then the printer asks to insert the new filament

To Reproduce
Use M702 via octoprint. Sometimes it behaves as described

Expected behavior
M702 should only unload filament everytime, and never ask to load new filament as if a filament change was requested

[JohnnyDeer]

Hi @Its-my-right, I can confirm that there is something wrong, thank you for reporting.

[gudnimg]

Not sure if this was present in 3.12 and before, but this should definitely not be an issue in 3.13 anymore as filament runout is blocked.

I think we should consider closing this issue once 3.13 is out.

[Prusa-Support]

It seems safe to close this issue as resolved.

If the issue persists via Octoprint (probably not tested), now the user can send M406/M405 codes to disable/enable the filament sensor before/after the M702 filament unload code (PR #1447).

Michele Moramarco
Prusa Research