mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #778] [Bug Report] Tried to print a sliced plate, the queue says it has been moved to the printing #518
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#518
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maziggy on GitHub (Mar 21, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/778
Originally assigned to: @maziggy on GitHub.
Tried to print a sliced plate, the queue says it has been moved to the printing state. But the printer never starts printing. Earlier print fine, the second one today doesnt wat to start. I already resliced and re-uploaded the sliced 3mf like usually, but no joy somehow.
Reporter Contact
Email: rubenkremer@gmail.com
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@RubenKremer commented on GitHub (Mar 21, 2026):
Changed it from a specific A1 to Any A1 and that seems to have worked. Now the print has commenced.
@maziggy commented on GitHub (Mar 22, 2026):
Root cause: When a queue item targets a specific printer and the scheduler detects it's disconnected, it enters a reconnect loop. Each attempt creates a fresh MQTT client that tries to subscribe to the printer's request topic. Your A1's MQTT broker rejects that subscription by disconnecting, which caused a ~170 second cycle of connect → subscribe → disconnect → repeat. By the time the connection stabilized, it was fragile enough that the print command was silently lost.
Switching to "Any A1" bypassed this entirely because that code path only uses already-connected printers — no reconnect loop, no request topic re-subscription.
Fix: We now cache request topic support per printer serial number, so new client instances immediately skip the subscription instead of rediscovering the rejection each time. This eliminates the thrash loop entirely.
Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@RubenKremer commented on GitHub (Mar 22, 2026):
Glad to have found a real potential bug instead of human error 😉 ... I'll try the daily version and report back if it occurs again!