Ive tried do some research and changed both the idle time out timer to 10 min and tried using a new cable connecting the Octopi to the printer.
Have you tried running in safe mode?
I have tried runnning in safe mod and problem still exists
Did running in safe mode solve the problem?
Additional information about your setup
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
My setup is and ender 3 pro with a skr mini board along with an octopi loaded on a raspberry pi 3b+ rev 1.3 running the latest version of octoprint.
Attached is a screen shot of what the serial log says unable to attach file because file is to big.
Last few lines of serial log:
2022-09-28 09:11:46,391 - Send: M105
2022-09-28 09:11:47,950 - Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2022-09-28 09:11:51,393 - Send: M105
2022-09-28 09:11:53,960 - No response from printer after 3 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2022-09-28 09:12:29,343 - Changing monitoring state from "Operational" to "Offline after error"
2022-09-28 09:12:29,367 - Connection closed, closing down monitor octoprint-systeminfo-20220928183816.zip (569.0 KB)
Please, turn off the debug mode.
The octoprint.log has 82614 lines with and 3863 lines without debug infos.
It takes space, calculation time and loads the CPU. Please only turn on when asked by a dev.
Same is for the Info level.
The matter is: The printer denies communication with OctoPrint at a certain point.
When the printer produces a HALT, usually something serious could be happened.
Under what circumstances of the printer does that issue occur?