Skip to content

Octoprint Plugin to display the estimated finish time of the current print

License

Notifications You must be signed in to change notification settings

AlexVerrico/Octoprint-Display-ETA

Repository files navigation

OctoPrint-Display-Print-ETA

Display the finish time of the current print as estimated by Octoprint. The day of finish is displayed only when the current print will not finish today. You can configure if you want to display the ETA on the printer, as well as if you want to use 12HR or 24HR time. If this plugin causes your printer to report errors, try enabling the option "remove all colons"

alt text

Setup

Install via the bundled Plugin Manager or manually using this URL:

https://github.com/AlexVerrico/Octoprint-Display-ETA/archive/master.zip

Some users have reported that the ETA is extremely innacurate, please try installing Print Time Genius before opening a new issue. You must have the time zone configured on the host, otherwise you will see the time in UTC. In Debian, use the following command to set time zone:

sudo dpkg-reconfigure tzdata

then follow the wizard.

Day and time are printed according to the host locales. In Debian they are configured using

sudo dpkg-reconfigure locales

then follow the wizard.

API

The API endpoint is /api/plugin/display_eta
For general API information see the Octoprint Docs.
For GET requests, the parameters should be included as query parameters
For POST requests the parameters should be included as a JSON dictionary
The endpoint requires that the parameter "command" be sent with all requests.
The available commands are:

  • current_eta: No additional parameters, returns a JSON dictionary containing the currently stored ETA for the current print. For example, {"eta":"02:32:05 PM"}
  • update_eta: No additional parameters, recalculates the ETA then returns a JSON dictionary containing the old ETA and the new ETA for the current print. For example, {"eta":"02:28:39 PM","old_eta":"02:28:38 PM"}

Contributing

All Pull Requests MUST be made to the devel branch, otherwise they will be ignored.
Please ensure that you follow the style of the code (use spaces not tabs, etc)
Please include descriptive comments to assist others to understand your changes
For now, all code must be backwards compatible with Python 2, unless you can provide a very compelling reason to drop Python 2 support.
Please open an issue to discuss what you feature(s) you want to add / bug(s) you want to fix before working on them, as this avoids 2 people submitting a PR for the same feature/bug.