starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #824] [Bug]: Print job sent via Bambuddy not executed – A1 remains in idle state #553

New issue

Closed

opened 2026-05-07 00:11:34 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

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

Owner

Originally created by @benjamdev on GitHub (Mar 26, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/824

Originally assigned to: @maziggy on GitHub.

Bug Description

When sending a print job from a locally hosted Bambuddy server to local a Bambu Lab A1 printer (Same Network), the job appears to be accepted, but the printer remains in idle state and does not start printing.

In Log File i can see the Message:

"[backend.app.services.background_dispatch]Printer Bens A1 (1) did not respond to print command within 15s (state still IDLE) — printer may need restart" -> I tried a few Restarts, it does not work

Expected Behavior

The printer should receive the print job and start printing.

Steps to Reproduce

Go To Archive, i can see all my Uploaded Files
Click on Print
Bambuddy Asks me on which Printer, Filament and Print Options - all okay I click "Print"
Files are sent to Printer succesfully with the Message "Background Dispatch successfully.
Printer does nothing except for generating the log entry ([backend.app.services.background_dispatch]Printer Bens A1 (1) did not respond to print command within 15s (state still IDLE) — printer may need restart")

Printer Model

Bambuddy Version

v0.2.2.1

Printer Firmware Version

01.07.02.00

Installation Method

Manual (git clone)

Operating System

Docker

Relevant Logs / Support Package

bambuddy-support-20260326-124745.zip

Screenshots

No response

Additional Context

Prerequisites are Okay:

Bambuddy is running
Printer is on and connected to Network (also Connected to HA and Configured a Smart Plug)
SD Card Inserted and Working
Developer Mode Active
IP Adress is known and reserved in DHCP for the Printer, Serial and Accesscode okay

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 @benjamdev on GitHub (Mar 26, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/824 Originally assigned to: @maziggy on GitHub. ### Bug Description When sending a print job from a locally hosted Bambuddy server to local a Bambu Lab A1 printer (Same Network), the job appears to be accepted, but the printer remains in idle state and does not start printing. In Log File i can see the Message: "[backend.app.services.background_dispatch]Printer Bens A1 (1) did not respond to print command within 15s (state still IDLE) — printer may need restart" -> I tried a few Restarts, it does not work ### Expected Behavior The printer should receive the print job and start printing. ### Steps to Reproduce 1. Go To Archive, i can see all my Uploaded Files 2. Click on Print 3. Bambuddy Asks me on which Printer, Filament and Print Options - all okay I click "Print" 4. Files are sent to Printer succesfully with the Message "Background Dispatch successfully. 5. Printer does nothing except for generating the log entry ([backend.app.services.background_dispatch]Printer Bens A1 (1) did not respond to print command within 15s (state still IDLE) — printer may need restart") ### Printer Model A1 ### Bambuddy Version v0.2.2.1 ### Printer Firmware Version 01.07.02.00 ### Installation Method Manual (git clone) ### Operating System Docker ### Relevant Logs / Support Package [bambuddy-support-20260326-124745.zip](https://github.com/user-attachments/files/26278566/bambuddy-support-20260326-124745.zip) ### Screenshots _No response_ ### Additional Context Prerequisites are Okay: - Bambuddy is running - Printer is on and connected to Network (also Connected to HA and Configured a Smart Plug) - SD Card Inserted and Working - Developer Mode Active - IP Adress is known and reserved in DHCP for the Printer, Serial and Accesscode okay ### 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:34 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

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

Author

Owner

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

Please try dev branch. It might solve your issue. Please let me know.

git checkout dev && git pull && sudo systemctl restart bambuddy

@maziggy commented on GitHub (Mar 26, 2026): Please try dev branch. It might solve your issue. Please let me know. git checkout dev && git pull && sudo systemctl restart bambuddy

BreizhHardware commented

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

Author

Owner

@benjamdev commented on GitHub (Mar 27, 2026):

git checkout dev && git pull && sudo systemctl restart bambuddy

Hi, seems no difference for me, Printer stays Idle:

cd /opt/bambuddy && git branch
* dev
  main

@benjamdev commented on GitHub (Mar 27, 2026): > git checkout dev && git pull && sudo systemctl restart bambuddy Hi, seems no difference for me, Printer stays Idle: ``` cd /opt/bambuddy && git branch * dev main ```

BreizhHardware commented

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

Author

Owner

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

Root cause: Your file Verteilerkasten_Pro_-90_Junktion Box PRO 90.3mf has spaces in the filename. The FTP upload to the printer works fine (spaces are OK in FTP paths), but the MQTT print command includes the filename as a URL (ftp://Verteilerkasten_Pro-_90_Junktion Box PRO 90.3mf). The firmware can't parse the URL with unencoded spaces, so it silently
ignores the command — that's why the printer stays IDLE.

Your earlier print Katzenfutterbeutel_Ausstreifer.gcode.3mf (no spaces) worked fine, which confirms this.

Fix: Spaces in the remote filename are now replaced with underscores before upload and print command.

Try reprinting the same file. It should upload as Verteilerkasten_Pro_-_90_Junktion_Box_PRO_90.3mf and the printer should start.

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 27, 2026): Root cause: Your file Verteilerkasten_Pro_-_90_Junktion Box PRO 90.3mf has spaces in the filename. The FTP upload to the printer works fine (spaces are OK in FTP paths), but the MQTT print command includes the filename as a URL (ftp://Verteilerkasten_Pro_-_90_Junktion Box PRO 90.3mf). The firmware can't parse the URL with unencoded spaces, so it silently ignores the command — that's why the printer stays IDLE. Your earlier print Katzenfutterbeutel_Ausstreifer.gcode.3mf (no spaces) worked fine, which confirms this. Fix: Spaces in the remote filename are now replaced with underscores before upload and print command. Try reprinting the same file. It should upload as Verteilerkasten_Pro_-_90_Junktion_Box_PRO_90.3mf and the printer should start. 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!