I'm using Octoprint in a unique fashion, I suppose. I turn my printer on/off with a smart switch so that it's not always running. When I want to use Octoprint, regardless of how long after I've turned on the printer or whether an app (i.e. Cura) checks whether the printer is connected, Octoprint is always disconnected and requires I hit the 'Connect' button.
It'd be nice to be able to configure the retry logic to be a bit more forgiving towards printers that are powered off before they need to be used. I think a 5-10m retry would handle this case pretty well without overcomplicating things.
A smarter way to do it could be to listen for specific edges where a user is likely desiring a retry. If I load the web interface after it's been idle for a while, or if I launch Cura which uses the API to check the printer status, these are clear indicators that a retry couldn't hurt. In the cases that I'm doing that, the printer is on and would succeed, but I have to go manually hit 'Connect' before anything can proceed.
I'm not sure how to make a plugin, or if there's a plugin that already does something like this, but figured the folks here could comment on the idea. Thanks!
Edit: Digging around it looks like I can disable the max consecutive timeout while idle and accomplish the simpler solution, though an intention-based approach could still be better.