That's my point I want to map the octoprint buttons to klipper macros.
The RESUME klipper command is somehow different from the resume button, and I don't know the reason that's why I want to change the resume button in octoprint to call RESUME macro.
Same goes for the start (print button). It is different than start from SD (M24). And I need the start from SD because I'm using the printer.print_stats.filament_used value in order to delay the runout pause.
OctoPrint automatically use M23/M24 commands if you are printing printer "SD card" files. When you upload files to OctoPrint are you uploading to SD card (button on right)?
@jneilliii Apologies I forgot to mention this. If use the upload to SD card in octoprint it gives an error about "can't write the SD card". But this is expected because the documentation already says:
# The path of the local directory on the host machine to look for
# g-code files. This is a read-only directory (sdcard file writes
# are not supported).
Anyhow I can see all my uploaded files (regular upload, NOT upload to SD). I can list all the files with M20, select file (M23) and print (M24).
Therefore my guess is that I want to trick octoprint to use the uploaded files as if they were uploaded to SD card.
We are at the initial point again. How to customize the print button behavior, or have a custom button, and how to capture the loaded file as a variable to use in my custom code.
I agree, and yes, moving to mainsail was in my mind since I moved to klipper. Just kept octoprint because I'm familiar with it.
Anyhow I want to confirm what options do I have in octoprint/octoklipper. A simple (on paper of course) solution for me would be creating the macro in octoklipper, but I do need to know if I can capture the octoprint loaded filename.
@jneilliii The key pramater is printer.print_stats.filament_used.
I use it to delay the filament replacement MACRO when the runout sensor triggers. If there is another way to keep track of the used filament that would make my life easier.