Octoprint 1.11.0 broke PSUControl

[akamakamak]

I upgraded to the OctoPrint 1.11.0 and although the plugin can turn the printer on and off, the OctoPrint will not be able to connect to the printer.
Had same issues on XL and MK4S.
Reverting back to OctoPrint 1.10.3 solved the issue.

[andimae77]

Same problem here.
Configuration: connected with Dirigera PSU plugin. Switching with Native plug control app has no effects on Octoprint, Switching off/on with PSU control breaks the connection from Octoprint to Printer. Restart of Octoprint is necessary then.

serial.1.log
octoprint.log

UPDATE: Problem already discussed in Octoprint forum_
https://community.octoprint.org/t/update-to-1-11-0-serial-port-broken/63110/2
Seems the Autoconnect function "Connect when powered on" blocks somehow the connection. Switching off the autoconnect makes everything working as it should.

In case you want a workaround try Oerkel47s psu control fork (devel branch): https://github.com/oerkel47/OctoPrint-PSUControl/archive/refs/heads/devel.zip 1

[oxivanisher]

I think the latest 1.11.1 release containing a fix for OctoPrint/OctoPrint#5151 just fixed this problem. At least for me, I am now able to connect to the printer again even if the initial "connect after power up" did not work.

[akamakamak]

I think the latest 1.11.1 release containing a fix for OctoPrint/OctoPrint#5151 just fixed this problem. At least for me, I am now able to connect to the printer again even if the initial "connect after power up" did not work.

Could you please check if the Pinter Shutdown option also works?

[oxivanisher]

You mean just powering off from the web UI?
I successfully powered the printer on and off several times with a intentionally short "auto connect" value. The manual connect and power off worked every time. For me, it's now working again like before the 1.11 update.

[akamakamak]

You mean just powering off from the web UI? I successfully powered the printer on and off several times with a intentionally short "auto connect" value. The manual connect and power off worked every time. For me, it's now working again like before the 1.11 update.

I meant the Power Off Option: Automatically turn PSU OFF when idle

[oxivanisher]

You mean just powering off from the web UI? I successfully powered the printer on and off several times with a intentionally short "auto connect" value. The manual connect and power off worked every time. For me, it's now working again like before the 1.11 update.

I meant the Power Off Option: Automatically turn PSU OFF when idle

I will try, but it will take some time. Its currently printing. :)

[akamakamak]

You mean just powering off from the web UI? I successfully powered the printer on and off several times with a intentionally short "auto connect" value. The manual connect and power off worked every time. For me, it's now working again like before the 1.11 update.

I meant the Power Off Option: Automatically turn PSU OFF when idle

I will try, but it will take some time. Its currently printing. :)

Much appreciated!

[oxivanisher]

I meant the Power Off Option: Automatically turn PSU OFF when idle

I will try, but it will take some time. Its currently printing. :)

Much appreciated!

Ok, so I did some tests. Automatic power off on idle is NOT working for me.
BUT to be true, I think this stopped working long ago. I didn't even realize that I had this option set on my printer and it definitely did not automatically power off for a very long time. I would guess, that this was introduced when I switched from the 8-bit prusa mk3 with the reprap based firmware to the prusa mk4 32-bit firmware firmware-buddy. There are several issues open on octoprint and in the prusa repositories for serial connection "stuff". In general its working, but several things are not as with the old firmware. This is a ongoing thing where everyone is pointing at the other and I won't go deeper into it. Read this thread if you are interested.
But it could just be a result of this incompatibility why this is no longer working but I think this should be its own issue, since the auto connect is absolutely working for me now.

Edit: There is already an open issue for this which applies to my situation: #271

[akamakamak]

See #271 for the fix.