I also turn my printer off when I'm not using it and OctoPrint's auto-reconnect doesn't work most of the time. If someone isn't paying attention and tries to connect while a print is running, it causes the printer to reboot, which isn't fun. So I largely leave it disconnected. I don't have a camera though. If I were making videos of my prints I'm sure I'd rely on OctoPrint more.
On the other hand, Octolapse is a lot of fun. But I went back to just using an SD card for important prints just because I value the recovery option.
There are a lot of small papercuts, like OctoPrint using `vcgencmd` to measure CPU throttling. `vcgencmd` is part of Raspberry Pi's userland. Not a big deal (aliased to another util). I've also added WebRTC-based streaming to my build.
The recommended way to use OctoPrint is the OctoPi image, which is based on Raspbian / Raspberry Pi OS. The OctoPi image includes extras like haproxy and mjpg streamer for HTTP-based JPEG frame stream. If you end up baking a RockPi image, here's the OctoPi root file system for reference: https://github.com/guysoft/OctoPi/tree/devel/src/modules/oct...
at this point the mere thought of setting up a sbc that isnt a raspberry pi is job security and frankly im not sure why. its not like the rasberry pi 1 days
If your operation expands and you want to chat about wrangling networked printer management software, shoot me an email leigh@printnanny.ai. I want to make it dead-simple to manage 10+ printers running a menagerie of software (OctoPrint, Moonraker/Mainsail) and firmwares (Marlin/Klipper). Happy to trade notes!