-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest OctoPrint update broke the "Automatically turn PSU OFF when idle" #252
Comments
I fixed mine (Octoprint 1.8.4) using my Ender 3 S1 by adding https://marlinfw.org/docs/gcode/M155.html I noticed that the |
Thank you Michael. |
thanks Michael, but even for me it does not solve the problem. I have Klipper |
I have exactly the same behaviour. |
If you are using LightsOut plugin remember to add the gcode commands used by this plugin to the ignored command list. LightsOut sends the set gcode command (to turn the lights off) every configured period of inactivity (not just once) if the PSU Control idle timeout is longer it will never see printer as idle even if the sent gcode is only "virtual" gcode for a plugin like GCODE System Commands. If it still does not trigger for you observe the Terminal to see what other gcode is sent to your printers. |
I d'ont use this LightsOut plugin |
Was there ever a resolution for this? Recently flashed the new Octopi 1.0.0 and the "Automatically turn PSU OFF when idle" does not seem to work anymore. Using a Prusa MK3S+. Octopi connected via RPi4/USB. Checked terminal; it does not seem to be sending anything to the printer. Just the printer sending temp messages. |
Can you downgrade the OctoPrint with the latest OctoPi? |
https://raw.githubusercontent.com/kantlivelong/OctoPrint-PSUControl/master/.github/ISSUE_TEMPLATE.md Also include serial logs. |
Is the add-on working for you? |
My printing environment is offline at the moment. |
Definitively, I have exactly the same behaviour. browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36 Edg/110.0.1587.69 |
https://raw.githubusercontent.com/kantlivelong/OctoPrint-PSUControl/master/.github/ISSUE_TEMPLATE.md |
I began having this issue after installing the plugin on a fresh installation of the RasPi image based install. I realized this plugin wasn't working and subscribed to this thread. Recently I realized that it started working again not having changed anything related to the plugin directly but I speculate it was after installing one or more additional plugins. I've listed all installed plugins below, I highly suspect Octolapse was the package that "fixed" the Auto Off functionality.
|
I had the Octolapse plugin installed all along. |
I have PRUSA MINI and MK3S. There were no problems with PSU Control on MINI at all. Some months ago, I discovered the same issue as these guys on my MK3S. I have tried many things (based on this topic) without success. I tried to enable debug and check logs - nothing in the logs (it needs more detailed debug logs - by the way). Today I decided to do some more debugging again, and based on this "Octolapse info", I checked my plugins and discovered that I had installed and enabled it on MINI but installed and disabled it on MK3S. I enabled Octolapse on MK3S and Woala, and it started to work. If @kantlivelong wants to do some deep debugging and testing, I'm ready to help:) |
OK, I was happy too early:( more printing and some testing = it works after a full octoprint reboot. It will stop working after the print. |
What were you doing?
What did you expect to happen?
What happened instead?
Version of OctoPrint-PSUControl
Operating System running OctoPrint
Printer model & used firmware incl. version
Link to octoprint.log with octoprnt.plugins.psucontrol set to DEBUG
The text was updated successfully, but these errors were encountered: