mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #616] [Bug]: Printer stuck in IDLE and plate not cleared #399
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#399
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 @Dendrowen on GitHub (Mar 5, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/616
Originally assigned to: @maziggy on GitHub.
Bug Description
The printer is in IDLE and there is no 'clear plate' button. An API call to clear the plate results in an error indicating the state is not FINISH or FAILED.
Expected Behavior
The next print to be picked up
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
0.2.2b1
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
Additional Context
No response
Checklist
@Dendrowen commented on GitHub (Mar 5, 2026):
bambuddy-support-20260305-084557.zip
@Dendrowen commented on GitHub (Mar 5, 2026):
I have now started a print directly from bambu studio to see if that resolves the issue for now. The state in bambuddy has changed to "RUNNING"
@maziggy commented on GitHub (Mar 5, 2026):
Are you sure developer mode is enabled on your printers?
@Dendrowen commented on GitHub (Mar 5, 2026):
Yes, very sure. It has worked up until now. The printer has finished my 0.2mm high cube and I can now clear the plate again. The next print has already started from bambuddy.
It's still an issue of course, but this is a way to fix the problem for now.
@maziggy commented on GitHub (Mar 5, 2026):
I've analyzed your logs and here's what I found:
What happened:
Why the queue stalled:
The most likely explanation is that your Big Dragon Split print was still running on the P1S during most of the log window. The scheduler correctly skips items when the printer is busy. The log ends at 08:45:55 (when you enabled debug logging), and your printer status shows IDLE at 08:45:57. The print may have finished just before you captured the support package, and the scheduler hadn't had a chance to run its next 30-second check yet.
However, we don't have enough visibility to be 100% sure — the scheduler had no logging for why it skips items. I've just added diagnostic logging that will show exactly why items aren't starting (printer state, connection status, manual_start flag, etc.). This will be in the next build.
Could you help confirm:
Also noted: The greenlet_spawn error from #612 is confirmed in your logs (5 occurrences). This happens on each MQTT reconnect during RFID auto-assign. We're tracking that separately.
Next steps: Please pull the latest 0.2.2b2 — it will include the scheduler diagnostics. If the issue happens again, the logs will tell us exactly what's going on.
@Dendrowen commented on GitHub (Mar 5, 2026):
I'll install 0.2.2b2 for now an let you know when it happens again.
@Dendrowen commented on GitHub (Mar 5, 2026):
I can't install 0.2.2b2 because there is no released docker file yet. (I guess?)
@maziggy commented on GitHub (Mar 5, 2026):
cd to your bambuddy folder and do a
git pull && git checkout 0.2.2b2 && git pull && docker compose down && docker compose up --build -d