OllisGit / OctoPrint-PrintJobHistory

OctoPrint Plugin stores all print-job informations of a print in a database
138 stars 38 forks source link

Cost Estimation aborted prints #183

Closed EvilBlood closed 2 years ago

EvilBlood commented 2 years ago

Hi,

I use PrintJobHistory in combination with Spool Manager and Cost Estimation.

I have noticed that if a Print was aborted the Duration and used Filament ist updated but the Cost Stay the same as the print would finished.

Versions: Octoprint Version 1.7.2 Cost Estimation (3.4.0) SpoolManager Plugin (1.5.0) PrintJobHistory (1.15.2)

EvilBlood commented 2 years ago

Hi, I also found the after a successful print. The Costs would not update. (based on the real print time)

AlexVercammen commented 2 years ago

In my case, sometimes the cost is not updated as well but randomly. I made sure CostEstimation was setup correctly. I am currently running a print and I will confirm my "random" statement...

OllisGit commented 2 years ago

I think I found the issue. The Cost-Plugin doesn't update the data reliable. I create a new ticket for that in the Cost-Repo: https://github.com/OllisGit/OctoPrint-CostEstimation/issues/16

OllisGit commented 2 years ago

Hi @AlexVercammen, @EvilBlood,

I release a new version https://github.com/OllisGit/OctoPrint-PrintJobHistory/releases/tag/1.17.0.dev1 in DEV channel.

This version should fix the cost-bug and also add the option to see how the costs were calculated in a technical log.

Please test and give feedback.

Thx, in advance Olli

github-actions[bot] commented 2 years ago

This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.

OllisGit commented 2 years ago

fyi: Now included in V1.17.0

github-actions[bot] commented 2 years ago

This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.

github-actions[bot] commented 2 years ago

This issue was closed, because it has been already marked for 10 days with no activity.