OctoPrint-DisplayLayerProgress VS OctoPrint-PSUControl

Bonus batch install popular addons: OctoPrint/bin/pip install "https://github.com/birkbjo/OctoPrint-Themeify/archive/master.zip" "https://github.com/jneilliii/OctoPrint-BedLevelVisualizer/archive/master.zip" "https://github.com/OctoPrint/OctoPrint-Autoselect/archive/master.zip" "https://github.com/MoonshineSG/OctoPrint-Autoscroll/archive/master.zip" "https://github.com/tpmullan/OctoPrint-DetailedProgress/archive/master.zip" "https://github.com/OllisGit/OctoPrint-DisplayLayerProgress/releases/latest/download/master.zip" "https://github.com/OctoPrint/OctoPrint-DisplayProgress/archive/master.zip" "https://github.com/OctoPrint/OctoPrint-FirmwareUpdater/archive/master.zip" "https://github.com/kantlivelong/OctoPrint-GCodeSystemCommands/archive/master.zip" "https://github.com/cesarvandevelde/OctoPrint-M73Progress/archive/master.zip" "https://github.com/cp2004/OctoPrint-EEPROM-Marlin/releases/latest/download/release.zip" "https://github.com/imrahil/OctoPrint-NavbarTemp/archive/master.zip" "https://github.com/jneilliii/OctoPrint-BLTouch/archive/master.zip" "https://github.com/eyal0/OctoPrint-PrintTimeGenius/archive/master.zip" "https://github.com/Salandora/octoprint-customControl/archive/master.zip" "https://github.com/j7126/OctoPrint-Dashboard/archive/master.zip"

Script

If you use Octoprint, it has this plugin - https://github.com/OllisGit/OctoPrint-DisplayLayerProgress

I just checked and this issue has been logged against DisplayLayerProgress: https://github.com/OllisGit/OctoPrint-DisplayLayerProgress/issues/207

and hundreds of comments about it on this github issue for displayLayerProgress

Replying to my other comment about the logs: Try enabling logging as detailed on the PSU-Control github. (I enabled both 'psucontrol' and 'psucontrol-tplink' to "debug" level).

Thanks for pointing me towards plugins. Didn't realize those would have the power to cause that kind of issue. Looks like it's probably my Home Assistant PSU Control plugin. Lots of error spam from it in my logs, and I found this issue: https://github.com/kantlivelong/OctoPrint-PSUControl/issues/262

Same. I use a TP-Link KP303 strip with the PSU Control plugin on OctoPrint. It cuts power 10m after the hotend and bed cool to 50c.

A few days before going the Home Assistant route I had installed the PSU Control plugin to be able to turn it off/on. It worked, but I thought it would be easier if I managed it with Home Assistant as it gave me many more options for including several conditional checks. Not to mention if I wanted to adjust the logic it was much quicker/easier to edit Home Assistant automations than to have to edit the plugin settings each time and hope I didn't screw it up.

Also, if you're willing to play with some wire cutters you can use a plugin for OctoPrint to turn on/off your 3D printer directly from the OctoPrint web interface. (Although if you go with the docker container you'll need to pass through GPIO control for this to work by mounting /dev/gpiochip0).

EDIT: this plugin https://plugins.octoprint.org/plugins/tplinksmartplug/ based on the more generic power control plugin https://github.com/kantlivelong/OctoPrint-PSUControl

Really need more info about your configuration. With the exception of catching M80/M81(configurable) PSU Control doesn't modify outgoing GCode. Logs also help. https://github.com/kantlivelong/OctoPrint-PSUControl/wiki/Troubleshooting#how-to-provide-logs