[GH-ISSUE #936] [Bug Report] I cannot start prints from Bambuddy. I have tried the troubleshooting tips from

BreizhHardware commented

2026-05-07 00:12:23 +02:00

Owner

Originally created by @maziggy on GitHub (Apr 10, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/936

Originally assigned to: @maziggy on GitHub.

I cannot start prints from Bambuddy. I have tried the troubleshooting tips from the wiki, but it does not help

Reporter Contact

Email: davidfoght@gmail.com

System Information

{
  "generated_at": "2026-04-10T13:52:01.527311",
  "app": {
    "version": "0.2.3b2",
    "debug_mode": false
  },
  "system": {
    "platform": "Linux",
    "platform_release": "6.8.12-4-pve",
    "platform_version": "#1 SMP PREEMPT_DYNAMIC PMX 6.8.12-4 (2024-11-06T15:04Z)",
    "architecture": "x86_64",
    "python_version": "3.13.12"
  },
  "environment": {
    "docker": false,
    "data_dir": "/opt/bambuddy",
    "log_dir": "/opt/[user]/logs",
    "timezone": ""
  },
  "database": {
    "archives_total": 2,
    "archives_completed": 2,
    "printers_total": 1,
    "filaments_total": 0,
    "projects_total": 1,
    "smart_plugs_total": 1
  },
  "printers": [
    {
      "index": 1,
      "model": "A1 Mini",
      "nozzle_count": 1,
      "is_active": true,
      "mqtt_connected": true,
      "state": "FINISH",
      "firmware_version": "01.07.02.00",
      "wifi_signal": -34,
      "reachable": true,
      "ams_unit_count": 1,
      "ams_tray_count": 4,
      "has_vt_tray": true,
      "external_camera_configured": false,
      "plate_detection_enabled": false,
      "hms_error_count": 0,
      "developer_mode": true,
      "nozzle_rack_count": 0
    }
  ],
  "settings": {
    "advanced_auth_enabled": "false",
    "smtp_auth_enabled": "true",
    "auth_enabled": "false",
    "setup_completed": "true",
    "auto_archive": "true",
    "save_thumbnails": "true",
    "capture_finish_photo": "true",
    "default_filament_cost": "100.0",
    "currency": "DKK",
    "energy_cost_per_kwh": "0.15",
    "energy_tracking_mode": "total",
    "disable_filament_warnings": "false",
    "prefer_lowest_filament": "false",
    "check_updates": "true",
    "check_printer_firmware": "true",
    "include_beta_updates": "false",
    "notification_language": "en",
    "bed_cooled_threshold": "35.0",
    "ams_humidity_good": "40",
    "ams_humidity_fair": "60",
    "ams_temp_good": "28.0",
    "ams_temp_fair": "35.0",
    "ams_history_retention_days": "30",
    "queue_drying_enabled": "false",
    "queue_drying_block": "false",
    "ambient_drying_enabled": "false",
    "drying_presets": "",
    "per_printer_mapping_expanded": "false",
    "date_format": "eu",
    "time_format": "24h",
    "default_printer_id": "1",
    "ftp_retry_enabled": "true",
    "ftp_retry_count": "3",
    "ftp_retry_delay": "2",
    "ftp_timeout": "60",
    "mqtt_enabled": "false",
    "mqtt_broker": "",
    "mqtt_port": "1883",
    "mqtt_topic_prefix": "bambuddy",
    "mqtt_use_tls": "false",
    "ha_enabled": "true",
    "library_archive_mode": "ask",
    "library_disk_warning_gb": "5.0",
    "camera_view_mode": "window",
    "preferred_slicer": "bambu_studio",
    "prometheus_enabled": "false",
    "user_notifications_enabled": "true",
    "default_bed_levelling": "false",
    "default_flow_cali": "true",
    "default_vibration_cali": "true",
    "default_layer_inspect": "false",
    "default_timelapse": "false",
    "stagger_group_size": "2",
    "stagger_interval_minutes": "5",
    "require_plate_clear": "true",
    "dark_style": "classic",
    "queue_shortest_first": "false",
    "debug_logging_enabled": "false",
    "debug_logging_enabled_at": ""
  },
  "virtual_printers": [],
  "integrations": {
    "notification_providers": [
      {
        "type": "homeassistant",
        "enabled": false,
        "has_last_error": false
      }
    ],
    "spoolman": {
      "enabled": false,
      "reachable": false
    },
    "mqtt_relay": {
      "enabled": false,
      "connected": false,
      "broker": "",
      "port": 0,
      "topic_prefix": "bambuddy"
    },
    "homeassistant": {
      "enabled": true
    }
  },
  "database_health": {
    "backend": "sqlite",
    "journal_mode": "wal",
    "quick_check": "ok",
    "db_size_bytes": 544768,
    "wal_size_bytes": 32992
  },
  "dependencies": {
    "fastapi": "0.135.3",
    "uvicorn": "0.44.0",
    "pydantic": "2.12.5",
    "sqlalchemy": "2.0.49",
    "paho-mqtt": "2.1.0",
    "psutil": "7.2.2",
    "httpx": "0.28.1",
    "aiofiles": "25.1.0",
    "cryptography": "46.0.7",
    "opencv-python-headless": "4.13.0.92",
    "numpy": "2.4.4"
  },
  "log_file": {
    "size_bytes": 219193,
    "size_formatted": "214.1 KB"
  },
  "network": {
    "interface_count": 1,
    "interfaces": [
      {
        "name": "eth0",
        "subnet": "x.x.50.0/24"
      }
    ]
  },
  "websockets": {
    "active_connections": 2
  }
}

Logs (sanitized): bambuddy.log

Submitted via BamBuddy Bug Report

Originally created by @maziggy on GitHub (Apr 10, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/936 Originally assigned to: @maziggy on GitHub. I cannot start prints from Bambuddy. I have tried the troubleshooting tips from the wiki, but it does not help <details> <summary>Reporter Contact</summary> Email: davidfoght@gmail.com </details> <details> <summary>System Information</summary> ```json { "generated_at": "2026-04-10T13:52:01.527311", "app": { "version": "0.2.3b2", "debug_mode": false }, "system": { "platform": "Linux", "platform_release": "6.8.12-4-pve", "platform_version": "#1 SMP PREEMPT_DYNAMIC PMX 6.8.12-4 (2024-11-06T15:04Z)", "architecture": "x86_64", "python_version": "3.13.12" }, "environment": { "docker": false, "data_dir": "/opt/bambuddy", "log_dir": "/opt/[user]/logs", "timezone": "" }, "database": { "archives_total": 2, "archives_completed": 2, "printers_total": 1, "filaments_total": 0, "projects_total": 1, "smart_plugs_total": 1 }, "printers": [ { "index": 1, "model": "A1 Mini", "nozzle_count": 1, "is_active": true, "mqtt_connected": true, "state": "FINISH", "firmware_version": "01.07.02.00", "wifi_signal": -34, "reachable": true, "ams_unit_count": 1, "ams_tray_count": 4, "has_vt_tray": true, "external_camera_configured": false, "plate_detection_enabled": false, "hms_error_count": 0, "developer_mode": true, "nozzle_rack_count": 0 } ], "settings": { "advanced_auth_enabled": "false", "smtp_auth_enabled": "true", "auth_enabled": "false", "setup_completed": "true", "auto_archive": "true", "save_thumbnails": "true", "capture_finish_photo": "true", "default_filament_cost": "100.0", "currency": "DKK", "energy_cost_per_kwh": "0.15", "energy_tracking_mode": "total", "disable_filament_warnings": "false", "prefer_lowest_filament": "false", "check_updates": "true", "check_printer_firmware": "true", "include_beta_updates": "false", "notification_language": "en", "bed_cooled_threshold": "35.0", "ams_humidity_good": "40", "ams_humidity_fair": "60", "ams_temp_good": "28.0", "ams_temp_fair": "35.0", "ams_history_retention_days": "30", "queue_drying_enabled": "false", "queue_drying_block": "false", "ambient_drying_enabled": "false", "drying_presets": "", "per_printer_mapping_expanded": "false", "date_format": "eu", "time_format": "24h", "default_printer_id": "1", "ftp_retry_enabled": "true", "ftp_retry_count": "3", "ftp_retry_delay": "2", "ftp_timeout": "60", "mqtt_enabled": "false", "mqtt_broker": "", "mqtt_port": "1883", "mqtt_topic_prefix": "bambuddy", "mqtt_use_tls": "false", "ha_enabled": "true", "library_archive_mode": "ask", "library_disk_warning_gb": "5.0", "camera_view_mode": "window", "preferred_slicer": "bambu_studio", "prometheus_enabled": "false", "user_notifications_enabled": "true", "default_bed_levelling": "false", "default_flow_cali": "true", "default_vibration_cali": "true", "default_layer_inspect": "false", "default_timelapse": "false", "stagger_group_size": "2", "stagger_interval_minutes": "5", "require_plate_clear": "true", "dark_style": "classic", "queue_shortest_first": "false", "debug_logging_enabled": "false", "debug_logging_enabled_at": "" }, "virtual_printers": [], "integrations": { "notification_providers": [ { "type": "homeassistant", "enabled": false, "has_last_error": false } ], "spoolman": { "enabled": false, "reachable": false }, "mqtt_relay": { "enabled": false, "connected": false, "broker": "", "port": 0, "topic_prefix": "bambuddy" }, "homeassistant": { "enabled": true } }, "database_health": { "backend": "sqlite", "journal_mode": "wal", "quick_check": "ok", "db_size_bytes": 544768, "wal_size_bytes": 32992 }, "dependencies": { "fastapi": "0.135.3", "uvicorn": "0.44.0", "pydantic": "2.12.5", "sqlalchemy": "2.0.49", "paho-mqtt": "2.1.0", "psutil": "7.2.2", "httpx": "0.28.1", "aiofiles": "25.1.0", "cryptography": "46.0.7", "opencv-python-headless": "4.13.0.92", "numpy": "2.4.4" }, "log_file": { "size_bytes": 219193, "size_formatted": "214.1 KB" }, "network": { "interface_count": 1, "interfaces": [ { "name": "eth0", "subnet": "x.x.50.0/24" } ] }, "websockets": { "active_connections": 2 } } ``` </details> **Logs (sanitized):** [bambuddy.log](https://raw.githubusercontent.com/maziggy/bambuddy/bug-report-assets/logs/f065a7ead7a54021a68a2fe2e28ac42e.log) --- *Submitted via BamBuddy Bug Report*

BreizhHardware

2026-05-07 00:12:23 +02:00

closed this issue
added the
user-report

bug
labels

BreizhHardware commented

2026-05-07 00:12:24 +02:00

Author

Owner

@ViridityCorn commented on GitHub (Apr 10, 2026):

This is my bug report. I also tried adding a print to the queue for ASAP printing, but it never got past "Pending". I removed it from the queue and restarted the printer (as the log attached in the bugreport mentioned it), and when it turned on again, it suddenly began printing. I am going to experiment a bit more with starting prints through Bambuddy to find out if the problem is now fixed, or if it stops working again.

@ViridityCorn commented on GitHub (Apr 10, 2026): This is my bug report. I also tried adding a print to the queue for ASAP printing, but it never got past "Pending". I removed it from the queue and restarted the printer (as the log attached in the bugreport mentioned it), and when it turned on again, it suddenly began printing. I am going to experiment a bit more with starting prints through Bambuddy to find out if the problem is now fixed, or if it stops working again.

BreizhHardware commented

2026-05-07 00:12:24 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 10, 2026):

Did you pay attention to https://wiki.bambuddy.cool/features/printer-control/?h=clear#clear-plate ?

@maziggy commented on GitHub (Apr 10, 2026): Did you pay attention to https://wiki.bambuddy.cool/features/printer-control/?h=clear#clear-plate ?

BreizhHardware commented

2026-05-07 00:12:24 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 10, 2026):

No, you didn't. If you don't want it, disable it in settings.

2026-04-10 13:44:48,534 INFO [backend.app.services.print_scheduler] Queue: printer 1 not available — connected=True, state=FINISH, **plate_cleared=False**

@maziggy commented on GitHub (Apr 10, 2026): No, you didn't. If you don't want it, disable it in settings. ` 2026-04-10 13:44:48,534 INFO [backend.app.services.print_scheduler] Queue: printer 1 not available — connected=True, state=FINISH, **plate_cleared=False** `

BreizhHardware commented

2026-05-07 00:12:24 +02:00

Author

Owner

@ViridityCorn commented on GitHub (Apr 11, 2026):

Thank you for your response.
You are correct, I missed the "clear-plate" control, which I mistakenly left on.
However, even after turning it off, I am experiencing the same problems. When starting a print from Bambuddy, nothing happens until I restart my printer. Then it suddenly starts printing.

@ViridityCorn commented on GitHub (Apr 11, 2026): Thank you for your response. You are correct, I missed the "clear-plate" control, which I mistakenly left on. However, even after turning it off, I am experiencing the same problems. When starting a print from Bambuddy, nothing happens until I restart my printer. Then it suddenly starts printing.

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 12, 2026):

Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Apr 12, 2026): Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@ViridityCorn commented on GitHub (Apr 13, 2026):

Yes, of course. Thank you.

bambuddy-support-20260413-195511.zip

Edit: Even more interestingly, it didn't even start the right print after restarting the printer. It started a previous print, I had cancelled.

@ViridityCorn commented on GitHub (Apr 13, 2026): Yes, of course. Thank you. [bambuddy-support-20260413-195511.zip](https://github.com/user-attachments/files/26683320/bambuddy-support-20260413-195511.zip) Edit: Even more interestingly, it didn't even start the right print after restarting the printer. It started a previous print, I had cancelled.

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 14, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let mme know if ti works for you now.

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

@maziggy commented on GitHub (Apr 14, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let mme know if ti works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@ViridityCorn commented on GitHub (Apr 15, 2026):

Hello. Thank you for the response.

I updated my instance, and for a single print, it seemed to be working (I could start it from Bambuddy).
However, currently, I am still unable to reprints elements from the archive. Bambuddy opens the modal, and uploads the file to the printer (I can see it on the printer), but it never starts.

I have attached a new support package. The print in question is "Clip_Mate_Filament_Clip".

I looked at the logs, and there also seems to be some problems with SD card cleanup, and there is also an explicit error regarding the printer's camera (Errno 104).

bambuddy-support-20260415-140912.zip

@ViridityCorn commented on GitHub (Apr 15, 2026): Hello. Thank you for the response. I updated my instance, and for a single print, it seemed to be working (I could start it from Bambuddy). However, currently, I am still unable to reprints elements from the archive. Bambuddy opens the modal, and uploads the file to the printer (I can see it on the printer), but it never starts. I have attached a new support package. The print in question is "Clip_Mate_Filament_Clip". I looked at the logs, and there also seems to be some problems with SD card cleanup, and there is also an explicit error regarding the printer's camera (Errno 104). [bambuddy-support-20260415-140912.zip](https://github.com/user-attachments/files/26748632/bambuddy-support-20260415-140912.zip)

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 15, 2026):

Thanks for the new bundle. I can see the reprint flow clearly now:

Bambuddy uploads Clip_Mate_Filament_Clip.3mf via FTP — succeeds (226 ack).
Sends the MQTT project_file start command.
Printer never transitions out of IDLE/FINISH within 15s. A power-cycle then starts a stale/previous print instead of the one you asked for.

The MQTT payload we send is byte-identical to the one that successfully reprinted archive 11 earlier the same day, so Bambuddy is doing its part correctly. The A1 Mini is accepting the upload but silently ignoring the start command, and it's holding onto stale state across reboots.

Strong suggestion: your A1 Mini is on firmware 01.07.02.00, which has known issues with SD card reads that line up exactly with the symptom here — the file uploads fine, but the printer can't read it back to actually start the job. Bambu just released 01.08.00.00 (2026-04-14). Please update the printer firmware and retry the reprint — I expect that to resolve it.

If the problem still reproduces on 01.08.00.00, a couple of follow-ups would help narrow it down further:

Had you cancelled or paused a print (via the printer screen or Bambu Handy) shortly before the failing reprint? The reboot starting the wrong previous print is the key clue that the printer had stale queued state.
Does a reprint work right after a clean power-cycle, but then fail after the next print completes?
Can you try the same reprint from Bambu Studio/Handy at the moment Bambuddy's reprint silently fails? If Studio also doesn't start it, it's confirmed firmware-side; if Studio works, there's something specific about our payload worth looking at.

The 550 SD-cleanup errors and the camera Errno 104 in the log are unrelated — cosmetic FTP quirks on the A1 Mini and a normal chamber-image reconnect.

@maziggy commented on GitHub (Apr 15, 2026): Thanks for the new bundle. I can see the reprint flow clearly now: 1. Bambuddy uploads Clip_Mate_Filament_Clip.3mf via FTP — succeeds (226 ack). 2. Sends the MQTT project_file start command. 3. Printer never transitions out of IDLE/FINISH within 15s. A power-cycle then starts a stale/previous print instead of the one you asked for. The MQTT payload we send is byte-identical to the one that successfully reprinted archive 11 earlier the same day, so Bambuddy is doing its part correctly. The A1 Mini is accepting the upload but silently ignoring the start command, and it's holding onto stale state across reboots. Strong suggestion: your A1 Mini is on firmware 01.07.02.00, which has known issues with SD card reads that line up exactly with the symptom here — the file uploads fine, but the printer can't read it back to actually start the job. Bambu just released 01.08.00.00 (2026-04-14). Please update the printer firmware and retry the reprint — I expect that to resolve it. If the problem still reproduces on 01.08.00.00, a couple of follow-ups would help narrow it down further: 1. Had you cancelled or paused a print (via the printer screen or Bambu Handy) shortly before the failing reprint? The reboot starting the wrong previous print is the key clue that the printer had stale queued state. 2. Does a reprint work right after a clean power-cycle, but then fail after the next print completes? 3. Can you try the same reprint from Bambu Studio/Handy at the moment Bambuddy's reprint silently fails? If Studio also doesn't start it, it's confirmed firmware-side; if Studio works, there's something specific about our payload worth looking at. The 550 SD-cleanup errors and the camera Errno 104 in the log are unrelated — cosmetic FTP quirks on the A1 Mini and a normal chamber-image reconnect.

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@ViridityCorn commented on GitHub (Apr 15, 2026):

bambuddy-support-20260415-171638.zip

Thank you for the response.

Currently, I cannot update to version 01.08.00.00, as the update itself has not yet been released (I can't find it at least). Only the changelog.

I should have specified that your previous update has solved the problem of the print lingering and starting after restarting the printer. That does not happen any more. However, now the print just never starts.

To answer your three questions:

I have not cancelled or paused a print shortly before. I have power cycled the printer to be sure.
No, it does not.
I can send the prints fine from Bambu Studio without any problems.

I have attached a new support bundle.

I first tried to start the print from Bambuddy with no luck. I then started the print from Bambu Studio which worked perfectly.

@ViridityCorn commented on GitHub (Apr 15, 2026): [bambuddy-support-20260415-171638.zip](https://github.com/user-attachments/files/26754624/bambuddy-support-20260415-171638.zip) Thank you for the response. Currently, I cannot update to version 01.08.00.00, as the update itself has not yet been released (I can't find it at least). Only the changelog. I should have specified that your previous update has solved the problem of the print lingering and starting after restarting the printer. That does not happen any more. However, now the print just never starts. To answer your three questions: 1. I have not cancelled or paused a print shortly before. I have power cycled the printer to be sure. 2. No, it does not. 3. I can send the prints fine from Bambu Studio without any problems. I have attached a new support bundle. I first tried to start the print from Bambuddy with no luck. I then started the print from Bambu Studio which worked perfectly.

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@ViridityCorn commented on GitHub (Apr 17, 2026):

@maziggy Also, can we reopen the issue? :)

@ViridityCorn commented on GitHub (Apr 17, 2026): @maziggy Also, can we reopen the issue? :)

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 17, 2026):

After analyzing the latest logs, everything points to firmware 01.07.02.00 on your A1 Mini being the root cause. The logs show a cascade of printer-side failures:

SSL connections killed mid-transfer — Bambuddy connects fine, but the printer's FTP server drops the TLS session during data transfer
Connection reset by peer (Errno 104) — the printer is actively refusing camera and FTP connections
Print commands silently ignored — Bambuddy uploads the file (226 ack confirmed), sends the MQTT start command, but the printer doesn't act on it. On your 7th attempt,
the printer finally responded — after a 55-second delay
AMS version info missing after reconnect — the printer isn't providing basic data it should
Persistent print_error (0x0500C010) that won't clear

Bambu Studio works because it establishes a completely fresh MQTT session for each action, while Bambuddy maintains a persistent connection that the printer's buggy
firmware degrades over time.

In the meantime we know that firmware version 01.07.02.00 had multiple issues. Please update to version 01.08.00.00.

@maziggy commented on GitHub (Apr 17, 2026): After analyzing the latest logs, everything points to firmware 01.07.02.00 on your A1 Mini being the root cause. The logs show a cascade of printer-side failures: - SSL connections killed mid-transfer — Bambuddy connects fine, but the printer's FTP server drops the TLS session during data transfer - Connection reset by peer (Errno 104) — the printer is actively refusing camera and FTP connections - Print commands silently ignored — Bambuddy uploads the file (226 ack confirmed), sends the MQTT start command, but the printer doesn't act on it. On your 7th attempt, the printer finally responded — after a 55-second delay - AMS version info missing after reconnect — the printer isn't providing basic data it should - Persistent print_error (0x0500C010) that won't clear Bambu Studio works because it establishes a completely fresh MQTT session for each action, while Bambuddy maintains a persistent connection that the printer's buggy firmware degrades over time. In the meantime we know that firmware version 01.07.02.00 had multiple issues. Please update to version 01.08.00.00.

BreizhHardware commented

2026-05-07 00:12:25 +02:00

Author

Owner

@ViridityCorn commented on GitHub (Apr 20, 2026):

I have done some testing, and after updating to 01.08.00.00, I am now able to print directly from Bambuddy.

Thank you so much for the help. I appreciate it a lot

@ViridityCorn commented on GitHub (Apr 20, 2026): I have done some testing, and after updating to 01.08.00.00, I am now able to print directly from Bambuddy. Thank you so much for the help. I appreciate it a lot

Rows
Columns

[GH-ISSUE #936] [Bug Report] I cannot start prints from Bambuddy. I have tried the troubleshooting tips from #646