-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Just somewhere to track initial implementation of the OctoPrint project...
- Pi to test with
- Base OctoPrint installation, functional, including webcam streaming
- Puppetize initial configuration
- Initial / base set of plugins
- User authentication - anonymous view-only, username/password for admins, email only (no/any password) for regular users. Want to be able to track who prints what. Only Admins can change settings, update, etc.
- One asterisk with using email addresses as "usernames" is that we can't (easily/reliably) notify people via Slack about print status
- Slack plugin to get webcam snapshots and cancel prints
- TRAINING and DOCS both for OctoPrint itself and for Cura. Ideally, just find some good YouTube tutorials for the latter.
- Tracking of print cancel reasons
Stretch Goals:
- Secure webcam streaming (how to secure this? re-streaming server? nginx proxy? https://octoeverywhere.com/ or similar?)
- Red button on printer (GPIO) to cancel
- Green button on printer (GPIO; flashing LED) to start print
- RGBW LEDs on printer frame or near camera - white while printing (for webcam), green when ready, red on error
- Easy and clear way for admins to "oops" a printer
- OctoFarm or some other dashboard for all of the printers?
- detection of obstructions on the bed, i.e. https://plugins.octoprint.org/plugins/bedready/
- Is there any local print failure detection? Or should we just try something like Spaghetti Detective?
- Central statistics on print success/failure, user stats, filament stats, etc.
- Slicing via https://github.com/OctoPrint/OctoPrint-CuraEngineLegacy (need to install CuraEngine)?
For the GPIO stuff (buttons, LEDs) there are some plugins for that, but for things like controlling lights it might be better to use event hooks to a separate daemon.
Metadata
Metadata
Assignees
Labels
No labels