- Terribly slow startup and load times.
- no support for mobile devices just with some app.
- While it can do lots of things with plugins they tend to kill performance which might cause artifacts on the print.
- slow on updates, they ware on Python 2.x until this year.
I'm currently migrating to mainsail (https://github.com/meteyou/mainsail), which looks much better.
All in all the main maintainer, which is working full time on it, is communicating well with the community. The iteration cycle has become faster during this last year, and updates seem to be rather stable.
Regarding the performance killing plugins, never had a problem on a RPi 4. What are you using?
I've got no interest in shuffling around sd cards in order to print models, nor do I want it connected to my primary pc that gets rebooted regularly.
And in their defence, I've been running OctoPrint for about 3 years and never had an issue with it across any updates.
And there is an unofficial app: https://play.google.com/store/apps/details?id=com.kabacon.oc...
Even on a Pi 2 with a plugin heavy instance (TouchUI with custom theme, octolapse, etc) the web interface loaded acceptably fast enough.
Python 3 support was in Beta/RC for a very long time intentionally so plugin authors could update.
I spent a while wondering why octoprint wasn't responding to http requests before sshing in and seeing python using 100% CPU.
I guess if you have reason to want process pictures?
Edit: plus visualization for auto-bed leveling is amazing trying to fine tune the printer bed.
These are the plugins I love so far. I guess it depends on which printer you have but these are all amazing for my uses.
1) It isn't pleasant to be near many industrial machines. Chemical vapor/off-gassing can be a real problem, so on top of the usually loud metal-component motion systems/gantries you have loud evacuation/exhaust fans. One place to deal with webcams/remote features on many machines at once is convenient.
2) Real time notifications create less machine downtime. A thermistor failed so a machine stopped mid-print? This time can be salvaged by a notification to browser or mobile for quick repair rather than discovering the issue by returning to the machine at the supposed end-time and being greeted with a non-finished print.
I now have a Prusa Mini, which is quiet and small enough to live in a cupboard in my office. It's far more reliable and the print time estimate is so accurate that I don't need Octoprint any more. It also has a USB port instead of SD card, so walking across my office with a USB stick is a viable alternative to sending jobs directly from my desktop browser.
So I guess it depends on your printer - if it's noisy, large, unreliable or you have lots of them, Octoprint is a godsend.
It depends what you envisage by 'remotely', I don't imagine ever starting a print while not at home, but I do want to sit at my computer, slice, and send straight to the printer; without faffing about with a USB stick.
as an RRF user I hope to see those features move over one day.
It's planned. I'm unsure if I like RRF or Klipper more, so kinda keep up with both.
input shaping allows one to get rid of mechanical resonances without re-engineering the motion system on a printer. It's pretty unique to klipper -- but it's one of those features that I suspect is brilliant enough to where the other groups who develop such software will probably follow-up with their own variations.
I've spoken to a few people on klipper who are inputing the variables for compensation in directly from an attached accelerometer on the printer frame. That'd be the way i'd want to go rather than taking a pair of calipers to the ringing artifacts on the print itself.