-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial printTimeLeft update takes forever on long prints #105
Comments
I have the same issue. You can use Example
Which contains quite a lot of info as well as the printTimeLeft.
|
So you're using this additional plugin to generate those events as the corresponding Gcode commands are fed to the printer, then using OctoPrint-MQTT to send the events to clients? |
When I start a long (8hr) print, I see a couple of octoPrint/progress/printing messages and one octoPrint/event/PrintStarted message on MQTT. In the former messages, printTimeLeft is either 0 or null. I don't see a valid printTimeLeft field on MQTT until the progress bar hits 1%, which takes several minutes on a long print job. It would be nice if this field got populated and sent out over MQTT as soon as it is known to OctoPrint, so that anything that wants to display the estimated time (e.g. dashboards) could be updated sooner.
The text was updated successfully, but these errors were encountered: