[GH-ISSUE #790] [Bug]: Constant deluge of "State is FINISH but completion NOT triggered" in logs #524

New issue

Closed

opened 2026-05-07 00:11:17 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:11:17 +02:00

Owner

Originally created by @jimmy-brightz on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/790

Originally assigned to: @maziggy on GitHub.

Bug Description

I just updated from v0.2.2 to v0.2.2.1. In my log I'm now seeing a constant stream of [backend.app.services.bambu_mqtt] [PRINTER_SERIAL] State is FINISH but completion NOT triggered: prev=FINISH, was_running=False, already_triggered=False, has_callback=True every 10ms or so. It seems to be generating for every printer in the farm with a finished job. Is this a sign of a problem on my end?

Expected Behavior

Somewhat fewer lines in the log with debug logging is disabled

Steps to Reproduce

Start the Bambuddy Docker instance
Wait a few seconds for the background services to start up

Printer Model

H2D

Bambuddy Version

0.2.2.1

Printer Firmware Version

01.02.00.00

Installation Method

Docker

Operating System

Linux (Other)

Relevant Logs / Support Package

bambuddy-support-20260323-130031.zip

Screenshots

No response

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @jimmy-brightz on GitHub (Mar 23, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/790 Originally assigned to: @maziggy on GitHub. ### Bug Description I just updated from v0.2.2 to v0.2.2.1. In my log I'm now seeing a constant stream of `[backend.app.services.bambu_mqtt] [PRINTER_SERIAL] State is FINISH but completion NOT triggered: prev=FINISH, was_running=False, already_triggered=False, has_callback=True` every 10ms or so. It seems to be generating for every printer in the farm with a finished job. Is this a sign of a problem on my end? ### Expected Behavior Somewhat fewer lines in the log with debug logging is disabled ### Steps to Reproduce 1. Start the Bambuddy Docker instance 2. Wait a few seconds for the background services to start up ### Printer Model H2D ### Bambuddy Version 0.2.2.1 ### Printer Firmware Version 01.02.00.00 ### Installation Method Docker ### Operating System Linux (Other) ### Relevant Logs / Support Package [bambuddy-support-20260323-130031.zip](https://github.com/user-attachments/files/26181660/bambuddy-support-20260323-130031.zip) ### Screenshots _No response_ ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:11:17 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:11:18 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 23, 2026):

Yes, you're right. That's an old debug log. Forgot to remove it again.

Available/Fixed in branch dev and available with the next release or daily build.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Mar 23, 2026): Yes, you're right. That's an old debug log. Forgot to remove it again. Available/Fixed in branch dev and available with the next release or daily build. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!