using GCODE for shutdown in .gcode files fails about octoprint-tasmota HOT 4 CLOSED

I have the impression, the command simply does not "reach" the plugin when played through the GCODE printing stream. Perhaps because it is distorted?

As you can see, what goes into the printer is slightly different according to the GCODE window (send GCODE vs. text in GCODE file), maybe it is not filtered out?

from octoprint-tasmota.

try increasing your gcode off delay. I think what you are running into is a race condition where the plugin is processing the off command but the printer is still in a printing state and not finished yet. set that value to like 15-30 seconds and see if that plays nicely.

from octoprint-tasmota.

That did the trick. I also found that my raspberry Pi needed substantial more time to fully come to a stop. The octopi server looses the connection rapidly, but the shutdown takes longer. I found these delays working for my setup.

(Pi powered from the PSU of the printer with a 5V / 5A stepdown convertor, and Tasmota relay in the mains cable to the printer)

from octoprint-tasmota.

Thanx for your help and your lovely plugin!

from octoprint-tasmota.