My Raspberry Pis running OctoPrint go to sleep after inactivity, and I need to reset the pi to get it running again. This problem is only occuring since I upgraded to 1.8.2. Before, I never had this problem. I was running 1.8.1 before. I have three units, one 3B, one Zero W, and one Zero 2 W.
Sometimes, after a lot of trying, I get to connect to them again without restarting them.
What did you already try to solve it?
I did a lot of Google searching, but haven't found anything relevant.
Have you tried running in safe mode?
Yes.
Did running in safe mode solve the problem?
No difference.
Systeminfo Bundle
You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
There is no dedicated 'sleep' function that I know of. What's the behaviour you are seeing? Does it become unreachable? Drop off the network connection?
I also have this problem after upgrading. My raspberry goes to sleep. The problem is that I cant cancel the print, everything goes off line. The only way to get out of it is to shut off my Prusa printer, kill power to the PI and then restart a completely new instance of octoprint.
There was a security issue which is why I upgraded. Whatever the update did to fix the security issue broke something. The connection is completely broken, I cant upload files also after it goes offline/standby and it gives me an error.
Only way to fix, restart printer, PI and restart the Browser to Octo
This is still the first I have heard of it 'going to sleep'. Please elaborate on what you call 'sleep', because I don't know what this is.
I think you probably have an issue with the wifi/network connection to your Raspberry Pi, especially if the print continues while OctoPrint is inaccessible. Try it with an ethernet cable to see if that stops it dropping out. Check if it is still connected to your network. Raspberry Pi's WiFi disconnecting is not a new problem and there are many many posts about this on this forum and others.
My Wifi Router 5G (Moca Extended) from Fios is about 12 feet away from the Raspberry PI. I have 1 Gigabit in the house, and I am an IT project Manager. This all started when I upgraded to the latest version (because of security concerns), as the original poster did as well.
Sleep= The cancel and pause command in browser will stop working. I cannot get back into octoprint UI even when doing a refresh with the browser refresh. I can no longer log in from another computer into the Octoprint UI at the same time as I did in the past. Obico is acting up and no longer functioning properly.
The print will start correctly. I can try to get a connection via the CONNECT button in the UI and it will not be able to connect. The print can finish sometimes, but I wont be able to print anything, I wont be able to upload anything (fails), and the only way to connect again is to power down the Raspberry Pi and the Prusa MIni printer.
Nothing network wise changed, nothing else changed. The only thing that changed was that I updated the firmware on the Octoprint because of "security issues" -- Wouldnt you agree two people from different places with the same issue is not a coincidence after updating the software?
I had this running for well over a year with no issues.
@Charlie_Powell I can provide more details on the 'sleeping'.
I turn on the Raspberry Pi. Within a minute or so, it boots up, and I can see the OctoPrint UI in my browser. Also if I scan the local network with Fing, I see the octopi instance.
I wait for let's say 30 minutes. (I never measured how much wait time I need exactly, I could do that.)
I try to load the OctoPrint UI in the browser, and it would not load. I try to look at the devices on my local network using Fing, and the Raspberry does not show up, or at least does not show up as an octopi instance. I try to ping it and it does not respond.
Sometimes if I mess with it enough, it can get it to come up again. I haven't managed to find a reliable method to do so. I noticed that once I restarted one of the raspberries, and two of them came online after that... weird.
I never had an issue with the prints interrupting, so I assume the problem is only with the WiFi / network. I shall try with wired connection to see if it is the WiFi.
Altogether I agree that this sure looks like a network / WiFi / Rapsberry issue. However, the facts that
it came up right after the upgrade to 1.8.2
it worked rock solid for many month before
it came up the same way the same time on 3 different raspberry pi models
it also happened to @MAX12345
makes me think the upgrade is a key element of the puzzle here.
And that proves to you what I was about to tell you: this has nothing to do with the OctoPrint update and everything with your local network hardware.
An update to OctoPrint is simply incapable of interfering with whether your Pi is reachable on your network or not. An update of OctoPi might, but those don't come over the air but require you to flash a new image to the card.
Actually Octoprint is closing all the ethernet ports a few minutes after a print finishes. It doesn't go to sleep it just becomes inaccessible. I did an update to Linux and the problem went away.
I just looked at my PI and realized it is NOT on WIFI. It is going to a dedicated switch with Ethernet.
Your assumption is right, it did not write to the Octoprint. But OctoPi Local itself is having problems get back into the Octoprint Raspberry Pi. What was the security issue, and how was it fixed?
Also, I noticed I wont be able to connect and then I hit refresh a few seconds later and it connects. Why is this?
So now, you have people who are on Wifi and Direct Ethernet with this issue. Nothing changed except the most recent security update. This rules out Wifi Completely.
I also want to add, when I hit print. It will print.
But the status state stays in operation
All the info under resend ratio 0/7 etc, temp, etc, print time, all go dead while it is printing.
I can also continue to watch my print from my PI camera through the control tab... (live)
It seems that you have a different issue to the original poster - they had a complete loss of connection to the server, which was a network issue and in the end not related to the 1.8.2 upgrade. It might be easier for you so start your own post, so we get the full information about your setup, along with testing it in safe mode and providing the systeminfo bundle.