[Bug] Time paused at print end due to retraction failure isn't being counted as usage hours but printer does
AdrianGarside opened this issue · comments
Describe the bug
Printer counts this as usage hours. The integration currently does not as time to completion dropped to 0 minutes so we stop updating the end time.
To Reproduce
.
Expected Behaviour
.
What device are you using?
P1S
Diagnostic Output
.
Log Extracts
No response
Other Information
No response
2024-01-23 11:23:47.133 DEBUG (Thread-6 (mqtt_listen_thread)) [custom_components.bambu_lab.pybambu] END TIME2: 2024-01-23 11:23:00
2024-01-23 11:27:09.210 DEBUG (Thread-6 (mqtt_listen_thread)) [custom_components.bambu_lab.pybambu] GCODE_STATE: RUNNING -> PAUSE
2024-01-23 19:01:03.038 DEBUG (Thread-6 (mqtt_listen_thread)) [custom_components.bambu_lab.pybambu] NEW USAGE HOURS: 11.62
2024-01-23 19:01:03.040 DEBUG (Thread-6 (mqtt_listen_thread)) [custom_components.bambu_lab] OVERWRITING USAGE_HOURS WITH : 298.62
But the new printer reported usage hours is 307 hours. The integration didn't count the ~11.27am -> 7.01pm time as the we never updated the end time while paused at 0 minutes left.