Issue with print clearing sequence being its own "print"

[whopster17]

Basically, on the older version of Continuous Print, I would have an IFTTT plugin that would send a webhook that would trigger a smart plug to turn on a fan to cool down the print bed. After 15 minutes, the fan would turn off and the bed clearing would start.

Now, on the newer versions, the bed clearing script is considered its own "print". Because of this, immediately after the bed is cleared, the fan turns on because the "gcode" finished. So for 15 minutes, the fan is on for the beginning of the print which is definitely not ideal. I tried to look for older releases but could only find so far back. Is there any other way I could workaround this?

[smartin015]

Is the plugin you're using this OctoPrint-IFTTT plugin? It looks like it just does a string match on events.

I can't override the way OctoPrint fires print completion events - that's built in. However, I could add a custom event which fires when CPQ starts the bed clearing process. In that case, all you'd have to do is change the event name in the IFTTT plugin to match the custom event, and ensure your bed clearing script appropriately waits for the proper time/temperature.

Let me know if this works for you, and I'll open a feature request.

[whopster17]

This would be absolutely perfect my friend and yes that's the IFTTT plugin I'm using. This would be so useful!

[smartin015]

Great - I opened #117, please keep an eye out there for implementation progress.