[GH-ISSUE #645] [Bug Report] [0500-C010] Warning MicroSD Card read/write exception: please reinsert or replac

BreizhHardware commented

2026-05-06 12:29:18 +02:00

Owner

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

Originally assigned to: @maziggy on GitHub.

[0500-C010]
Warning
MicroSD Card read/write exception: please reinsert or replace the MicroSD Card.

Hi Guys

Ich bekomme ständig den Fehler von oben.
Es ist so das ich jetzt sämtliche sd karten durch habe und eine neue bestellt habe sehr gute sundisk aber leide keine Änderung.
Ich weis nicht mehr weiter ich Drucke Eine Datei und bei der nächsten geht es nicht mehr ?

Reporter Contact

Email: lanfi89@googlemail.com

System Information

{
  "generated_at": "2026-03-07T03:30:16.070198",
  "app": {
    "version": "0.2.2b1",
    "debug_mode": false
  },
  "system": {
    "platform": "Linux",
    "platform_release": "6.1.126-Unraid",
    "platform_version": "#1 SMP PREEMPT_DYNAMIC Sun Jan 19 15:51:34 PST 2025",
    "architecture": "x86_64",
    "python_version": "3.13.12"
  },
  "environment": {
    "docker": true,
    "data_dir": "/app/data",
    "log_dir": "/app/logs",
    "timezone": "America/Toronto"
  },
  "database": {
    "archives_total": 19,
    "archives_completed": 10,
    "printers_total": 1,
    "filaments_total": 0,
    "projects_total": 3,
    "smart_plugs_total": 1
  },
  "printers": [
    {
      "index": 1,
      "model": "P1S",
      "nozzle_count": 1,
      "is_active": true,
      "mqtt_connected": true,
      "state": "IDLE",
      "firmware_version": "01.09.01.00",
      "wifi_signal": -70,
      "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": null,
      "nozzle_rack_count": 0
    }
  ],
  "settings": {
    "auth_enabled": "false",
    "setup_completed": "true",
    "auto_archive": "true",
    "save_thumbnails": "true",
    "capture_finish_photo": "true",
    "default_filament_cost": "20.0",
    "currency": "EUR",
    "energy_cost_per_kwh": "0.4",
    "energy_tracking_mode": "total",
    "check_updates": "true",
    "notification_language": "de",
    "ams_humidity_good": "40",
    "ams_humidity_fair": "60",
    "ams_temp_good": "28.0",
    "ams_temp_fair": "35.0",
    "ams_history_retention_days": "30",
    "per_printer_mapping_expanded": "false",
    "date_format": "system",
    "time_format": "system",
    "default_printer_id": "1",
    "telemetry_enabled": "true",
    "ftp_retry_enabled": "true",
    "ftp_retry_count": "3",
    "ftp_retry_delay": "5",
    "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": "embedded",
    "dark_accent": "blue",
    "dark_style": "vibrant",
    "virtual_printer_enabled": "false",
    "virtual_printer_mode": "immediate",
    "virtual_printer_model": "C12",
    "check_printer_firmware": "true",
    "ftp_timeout": "60",
    "prometheus_enabled": "false",
    "virtual_printer_remote_interface_ip": "",
    "bed_cooled_threshold": "35.0",
    "preferred_slicer": "bambu_studio",
    "include_beta_updates": "false"
  },
  "docker": {
    "container_memory_limit_bytes": null,
    "container_memory_limit_formatted": null,
    "network_mode_hint": "host"
  },
  "virtual_printers": [
    {
      "index": 1,
      "enabled": false,
      "mode": "immediate",
      "model": "C12",
      "model_name": "P1S",
      "has_target_printer": true,
      "has_bind_ip": true,
      "running": false,
      "pending_files": 0
    }
  ],
  "integrations": {
    "notification_providers": [
      {
        "type": "telegram",
        "enabled": true,
        "has_last_error": true
      }
    ],
    "spoolman": {
      "enabled": false,
      "reachable": false
    },
    "mqtt_relay": {
      "enabled": false,
      "connected": false,
      "broker": "",
      "port": 0,
      "topic_prefix": "bambuddy"
    },
    "homeassistant": {
      "enabled": true
    }
  },
  "database_health": {
    "journal_mode": "wal",
    "quick_check": "ok",
    "db_size_bytes": 499712,
    "wal_size_bytes": 4128272
  },
  "dependencies": {
    "fastapi": "0.135.1",
    "uvicorn": "0.41.0",
    "pydantic": "2.12.5",
    "sqlalchemy": "2.0.48",
    "paho-mqtt": "2.1.0",
    "psutil": "7.2.2",
    "httpx": "0.28.1",
    "aiofiles": "25.1.0",
    "cryptography": "46.0.5",
    "opencv-python-headless": "4.13.0.92",
    "numpy": "2.4.2"
  },
  "log_file": {
    "size_bytes": 4084418,
    "size_formatted": "3.9 MB"
  },
  "network": {
    "interface_count": 1,
    "interfaces": [
      {
        "name": "br0",
        "subnet": "x.x.178.0/24"
      }
    ]
  },
  "websockets": {
    "active_connections": 1
  }
}

Logs (sanitized): bambuddy.log

Submitted via BamBuddy Bug Report

Originally created by @maziggy on GitHub (Mar 7, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/645 Originally assigned to: @maziggy on GitHub. [0500-C010] Warning MicroSD Card read/write exception: please reinsert or replace the MicroSD Card. Hi Guys Ich bekomme ständig den Fehler von oben. Es ist so das ich jetzt sämtliche sd karten durch habe und eine neue bestellt habe sehr gute sundisk aber leide keine Änderung. Ich weis nicht mehr weiter ich Drucke Eine Datei und bei der nächsten geht es nicht mehr ? <details> <summary>Reporter Contact</summary> Email: lanfi89@googlemail.com </details> <details> <summary>System Information</summary> ```json { "generated_at": "2026-03-07T03:30:16.070198", "app": { "version": "0.2.2b1", "debug_mode": false }, "system": { "platform": "Linux", "platform_release": "6.1.126-Unraid", "platform_version": "#1 SMP PREEMPT_DYNAMIC Sun Jan 19 15:51:34 PST 2025", "architecture": "x86_64", "python_version": "3.13.12" }, "environment": { "docker": true, "data_dir": "/app/data", "log_dir": "/app/logs", "timezone": "America/Toronto" }, "database": { "archives_total": 19, "archives_completed": 10, "printers_total": 1, "filaments_total": 0, "projects_total": 3, "smart_plugs_total": 1 }, "printers": [ { "index": 1, "model": "P1S", "nozzle_count": 1, "is_active": true, "mqtt_connected": true, "state": "IDLE", "firmware_version": "01.09.01.00", "wifi_signal": -70, "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": null, "nozzle_rack_count": 0 } ], "settings": { "auth_enabled": "false", "setup_completed": "true", "auto_archive": "true", "save_thumbnails": "true", "capture_finish_photo": "true", "default_filament_cost": "20.0", "currency": "EUR", "energy_cost_per_kwh": "0.4", "energy_tracking_mode": "total", "check_updates": "true", "notification_language": "de", "ams_humidity_good": "40", "ams_humidity_fair": "60", "ams_temp_good": "28.0", "ams_temp_fair": "35.0", "ams_history_retention_days": "30", "per_printer_mapping_expanded": "false", "date_format": "system", "time_format": "system", "default_printer_id": "1", "telemetry_enabled": "true", "ftp_retry_enabled": "true", "ftp_retry_count": "3", "ftp_retry_delay": "5", "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": "embedded", "dark_accent": "blue", "dark_style": "vibrant", "virtual_printer_enabled": "false", "virtual_printer_mode": "immediate", "virtual_printer_model": "C12", "check_printer_firmware": "true", "ftp_timeout": "60", "prometheus_enabled": "false", "virtual_printer_remote_interface_ip": "", "bed_cooled_threshold": "35.0", "preferred_slicer": "bambu_studio", "include_beta_updates": "false" }, "docker": { "container_memory_limit_bytes": null, "container_memory_limit_formatted": null, "network_mode_hint": "host" }, "virtual_printers": [ { "index": 1, "enabled": false, "mode": "immediate", "model": "C12", "model_name": "P1S", "has_target_printer": true, "has_bind_ip": true, "running": false, "pending_files": 0 } ], "integrations": { "notification_providers": [ { "type": "telegram", "enabled": true, "has_last_error": true } ], "spoolman": { "enabled": false, "reachable": false }, "mqtt_relay": { "enabled": false, "connected": false, "broker": "", "port": 0, "topic_prefix": "bambuddy" }, "homeassistant": { "enabled": true } }, "database_health": { "journal_mode": "wal", "quick_check": "ok", "db_size_bytes": 499712, "wal_size_bytes": 4128272 }, "dependencies": { "fastapi": "0.135.1", "uvicorn": "0.41.0", "pydantic": "2.12.5", "sqlalchemy": "2.0.48", "paho-mqtt": "2.1.0", "psutil": "7.2.2", "httpx": "0.28.1", "aiofiles": "25.1.0", "cryptography": "46.0.5", "opencv-python-headless": "4.13.0.92", "numpy": "2.4.2" }, "log_file": { "size_bytes": 4084418, "size_formatted": "3.9 MB" }, "network": { "interface_count": 1, "interfaces": [ { "name": "br0", "subnet": "x.x.178.0/24" } ] }, "websockets": { "active_connections": 1 } } ``` </details> **Logs (sanitized):** [bambuddy.log](https://raw.githubusercontent.com/maziggy/bambuddy/bug-report-assets/logs/64e48245b44f47938d1393015a1cfe6a.log) --- *Submitted via BamBuddy Bug Report*

BreizhHardware

2026-05-06 12:29:18 +02:00

closed this issue
added the
user-report

bug
labels

BreizhHardware commented

2026-05-06 12:29:19 +02:00

Author

Owner

@Bademeister89 commented on GitHub (Mar 7, 2026):

Hi,

I have the same problem.
I start a print normally, the file uploads, but nothing happens. After a while I get the following error:

[0500-C010]
Warning
MicroSD Card read/write exception: please reinsert or replace the MicroSD Card.

Even reinserting it doesn’t work. Strangely, when I restart Bambuddy, everything works normally again.
My system is running on Unraid.

I have also tried several SD cards, but none of them worked.

@Bademeister89 commented on GitHub (Mar 7, 2026): Hi, I have the same problem. I start a print normally, the file uploads, but nothing happens. After a while I get the following error: [0500-C010] Warning MicroSD Card read/write exception: please reinsert or replace the MicroSD Card. Even reinserting it doesn’t work. Strangely, when I restart Bambuddy, everything works normally again. My system is running on Unraid. I have also tried several SD cards, but none of them worked.

BreizhHardware commented

2026-05-06 12:29:19 +02:00

Author

Owner

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

Not yet sure where this comes from. Added a "best guess fix" to branch 0.2.2b3. Please try again and let me now.

If the error persists, please create a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Mar 7, 2026): Not yet sure where this comes from. Added a "best guess fix" to branch 0.2.2b3. Please try again and let me now. If the error persists, please create a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

2026-05-06 12:29:19 +02:00

Author

Owner

@SebSeifert commented on GitHub (Mar 8, 2026):

Looks promising. Had the Same Problem. Side effects were also Prints Not starting, cancel These Prints from Webinterface Had No effect.

Now it works for me in v0.2.3b1

@SebSeifert commented on GitHub (Mar 8, 2026): Looks promising. Had the Same Problem. Side effects were also Prints Not starting, cancel These Prints from Webinterface Had No effect. Now it works for me in v0.2.3b1

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

@Percy2Live commented on GitHub (Mar 8, 2026):

I experienced the same issue. In my case it was the SD-card, though. After ~2300h of printing (and multiple times of that the printer being online) the original card seemed to have failed. Now using a good quality SD card as replacement and I have not seen this issue anymore.

@Percy2Live commented on GitHub (Mar 8, 2026): I experienced the same issue. In my case it was the SD-card, though. After ~2300h of printing (and multiple times of that the printer being online) the original card seemed to have failed. Now using a good quality SD card as replacement and I have not seen this issue anymore.

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

@Bademeister89 commented on GitHub (Mar 8, 2026):

After updating to version v0.2.2b2, the problem has not occurred again!

Really great work, guys!
I'm looking forward to the future and have fully integrated Bambuddy into my setup.

@Bademeister89 commented on GitHub (Mar 8, 2026): After updating to version v0.2.2b2, the problem has not occurred again! Really great work, guys! I'm looking forward to the future and have fully integrated Bambuddy into my setup.

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

@curiousmuch commented on GitHub (Mar 10, 2026):

I've also not had the issue since *b2.

@curiousmuch commented on GitHub (Mar 10, 2026): I've also not had the issue since *b2.

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

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

@maziggy commented on GitHub (Mar 10, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

I recently keep getting these errors again. I think it was never fully fixed for me, it just takes longer until it happens. I already exchanged the SD card, but this didn't help. Once I get these errors, restarting the printer or bambuddy does not really help. Only formatting the SD-card (which is not even half full) helps. Also bambuddy takes very long to send this message:

This is the support package

bambuddy-support-20260412-192552.zip

Anybody else having this issue?

@Percy2Live commented on GitHub (Apr 12, 2026): I recently keep getting these errors again. I think it was never fully fixed for me, it just takes longer until it happens. I already exchanged the SD card, but this didn't help. Once I get these errors, restarting the printer or bambuddy does not really help. Only formatting the SD-card (which is not even half full) helps. Also bambuddy takes very long to send this message: <img width="483" height="374" alt="Image" src="https://github.com/user-attachments/assets/33de4bf5-407a-488b-85dc-4605a9116f7e" /> This is the support package [bambuddy-support-20260412-192552.zip](https://github.com/user-attachments/files/26661086/bambuddy-support-20260412-192552.zip) Anybody else having this issue?

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

Do you upgraded printer's firmware recently?

@maziggy commented on GitHub (Apr 12, 2026): Do you upgraded printer's firmware recently?

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

Not that I remember - the latest one is not available for local users as it's being discussed in another thread here.
Do you think the reason could be a missing certificate? Shall I redo the certificate deployment?

@Percy2Live commented on GitHub (Apr 12, 2026): Not that I remember - the latest one is not available for local users as it's being discussed in another thread here. Do you think the reason could be a missing certificate? Shall I redo the certificate deployment?

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

I have exactly the same problem!
The printer firmware has not been updated yet — version 01.09.01.00.

@Bademeister89 commented on GitHub (Apr 13, 2026): I have exactly the same problem! The printer firmware has not been updated yet — version 01.09.01.00.

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

Please update to latest beta 0.2.3b3. There are some related fixes which may fix your issue.

@maziggy commented on GitHub (Apr 13, 2026): Please update to latest beta 0.2.3b3. There are some related fixes which may fix your issue.

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

The problem still persists despite updating to version 0.2.3.b4.
The printer firmware is now also up to date (01.10.00.00).
The error is again:
[0500-C010]
Warning
MicroSD Card read/write exception: please reinsert or replace the MicroSD Card.
Thank you very much — I really hope we can solve this. I love this project.

@Bademeister89 commented on GitHub (Apr 14, 2026): The problem still persists despite updating to version 0.2.3.b4. The printer firmware is now also up to date (01.10.00.00). The error is again: [0500-C010] Warning MicroSD Card read/write exception: please reinsert or replace the MicroSD Card. Thank you very much — I really hope we can solve this. I love this project.

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

Printer?

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

BreizhHardware commented

2026-05-06 12:29:20 +02:00

Author

Owner

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

P1s

@Bademeister89 commented on GitHub (Apr 14, 2026): P1s

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

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

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

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

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

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

bambuddy-support-20260415-182357.zip

@Bademeister89 commented on GitHub (Apr 15, 2026): [bambuddy-support-20260415-182357.zip](https://github.com/user-attachments/files/26756373/bambuddy-support-20260415-182357.zip)

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

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

Thanks for the b4 log — it narrows this down cleanly.

What the log actually shows:

FTP upload completes successfully every time (STOR 226 OK, full 2.5 MB delivered)
The 0500_C010 error is emitted by the printer, about 2 minutes after the file has been uploaded and Bambuddy sends the print command. The printer can't read the file it just accepted from its own SD card
Wi-Fi signal logs at -65 dBm and upload speeds are unusually slow (41 KB/s for a 2.5 MB file, 60s per upload) — normal P1S throughput is 100–300 KB/s

This matches what @Percy2Live described: formatting the SD card fixes it for a while, replacing the card doesn't. That pattern is filesystem-level corruption, not a hardware fault and not something Bambuddy can cause — we only upload the file and send the print command; the read/write exception happens entirely inside the printer firmware.

Two things worth trying before anything else:

Format the SD card fresh again (FAT32), since that's the known workaround.
Reduce packet loss on the way to the printer. -65 dBm is borderline; at those levels FTP completes (because TLS retries) but writes can stall.

As a cross-check: can you try uploading the same .3mf directly from BambuStudio (LAN/cloud, not via Bambuddy) and start it from there? If 0500_C010 shows up with that too, it confirms the issue is printer-side and independent of Bambuddy.

Once the card is freshly formatted and the network is more stable, please run for a few days and report back.

@maziggy commented on GitHub (Apr 16, 2026): Thanks for the b4 log — it narrows this down cleanly. What the log actually shows: - FTP upload completes successfully every time (STOR 226 OK, full 2.5 MB delivered) - The 0500_C010 error is emitted by the printer, about 2 minutes after the file has been uploaded and Bambuddy sends the print command. The printer can't read the file it just accepted from its own SD card - Wi-Fi signal logs at -65 dBm and upload speeds are unusually slow (41 KB/s for a 2.5 MB file, 60s per upload) — normal P1S throughput is 100–300 KB/s This matches what @Percy2Live described: formatting the SD card fixes it for a while, replacing the card doesn't. That pattern is filesystem-level corruption, not a hardware fault and not something Bambuddy can cause — we only upload the file and send the print command; the read/write exception happens entirely inside the printer firmware. Two things worth trying before anything else: 1. Format the SD card fresh again (FAT32), since that's the known workaround. 2. Reduce packet loss on the way to the printer. -65 dBm is borderline; at those levels FTP completes (because TLS retries) but writes can stall. As a cross-check: can you try uploading the same .3mf directly from BambuStudio (LAN/cloud, not via Bambuddy) and start it from there? If 0500_C010 shows up with that too, it confirms the issue is printer-side and independent of Bambuddy. Once the card is freshly formatted and the network is more stable, please run for a few days and report back.

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

@Percy2Live commented on GitHub (Apr 16, 2026):

My connection is at -57 dBm right now, but in general there is no issue when connecting to the printer.

Formatting the SD card helps temporarily, but the issue occurs again. So this is not a permanent fix. Is there anything that can be done on bambuddys side to improve this behavior? With direct connections via bambu studio no issues occur

@Percy2Live commented on GitHub (Apr 16, 2026): My connection is at -57 dBm right now, but in general there is no issue when connecting to the printer. Formatting the SD card helps temporarily, but the issue occurs again. So this is not a permanent fix. Is there anything that can be done on bambuddys side to improve this behavior? With direct connections via bambu studio no issues occur

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

@Bademeister89 commented on GitHub (Apr 16, 2026):

There is a larger issue on the side of P1S printers and Fritz!Box routers.
My Fritz!Box is about 2 meters away from the printer, and I’m getting a very poor signal (see above).

I did some searching and found the following:
https://forum.bambulab.com/t/wlan-problem-uber-fritz-repeater/20417/23

I have now placed my printer directly next to the router and am getting a signal of -50 dBm — still not great, but better. For now, the process is working for me.
I will continue testing!

The SD card read and write error still occurred once sporadically despite formatting.

@Bademeister89 commented on GitHub (Apr 16, 2026): There is a larger issue on the side of P1S printers and Fritz!Box routers. My Fritz!Box is about 2 meters away from the printer, and I’m getting a very poor signal (see above). I did some searching and found the following: https://forum.bambulab.com/t/wlan-problem-uber-fritz-repeater/20417/23 I have now placed my printer directly next to the router and am getting a signal of -50 dBm — still not great, but better. For now, the process is working for me. I will continue testing! The SD card read and write error still occurred once sporadically despite formatting.

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

@Percy2Live commented on GitHub (Apr 16, 2026):

In my case the access point is a unifi ac ap pro, no Fritz!Box

I don't think it's an AVM specific problem

I already formatted the SD card 6 or 7 times - even changed the whole card to a high quality one. It always works for a while until the issue reoccurrs again

@Percy2Live commented on GitHub (Apr 16, 2026): In my case the access point is a unifi ac ap pro, no Fritz!Box I don't think it's an AVM specific problem I already formatted the SD card 6 or 7 times - even changed the whole card to a high quality one. It always works for a while until the issue reoccurrs again

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

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

I’ve got another current log here.

Wi-Fi connection improved.
SD card new and formatted.

Print from the queue doesn’t start at all?
Before the log, there were repeated SD card errors.

bambuddy-support-20260417-120433.zip

@Bademeister89 commented on GitHub (Apr 17, 2026): I’ve got another current log here. Wi-Fi connection improved. SD card new and formatted. Print from the queue doesn’t start at all? Before the log, there were repeated SD card errors. [bambuddy-support-20260417-120433.zip](https://github.com/user-attachments/files/26819063/bambuddy-support-20260417-120433.zip)

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

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

I think I found a bug in the current daily release. It somehow disabled the "print plate cleared" button in the settings (= enabled the switch in settings). So if I start a print, I can see in the logs it waits for the print bed to be cleared (which never happens because the button is disabled). After an extended amount of time I then get the micro SD card error. After enabling the print bed cleared button again in the options (= disabling the switch as shown in the picture), it appeared on the main page again, I was able to press it and the queued print finally started without issues.

@Bademeister89 can you check this?

In the debug logs I could see the printer was basically stuck with this message:

10:21:28,192
[backend.app.services.print_scheduler]
Queue: printer 1 not available — connected=True, state=IDLE, awaiting_plate_clear=True

Now it works, although I keep getting these messages (which may explain why my SD card is always running full quite quickly):

11:02:38,473
[backend.app.services.bambu_ftp]
FTP connected successfully to 192.168.101.211 (model=P1S, prot_c=False)
11:02:38,486
[backend.app.services.bambu_ftp]
Failed to delete /Wandhalterung.gcode: 550
11:02:38,507
[backend.app.main]
SD card cleanup failed after 3 attempts for /Wandhalterung.gcode (file may linger on SD card)

Can the others check whether this is the same for them?

@Percy2Live commented on GitHub (Apr 17, 2026): I think I found a bug in the current daily release. It somehow disabled the "print plate cleared" button in the settings (= enabled the switch in settings). So if I start a print, I can see in the logs it waits for the print bed to be cleared (which never happens because the button is disabled). After an extended amount of time I then get the micro SD card error. After enabling the print bed cleared button again in the options (= disabling the switch as shown in the picture), it appeared on the main page again, I was able to press it and the queued print finally started without issues. @Bademeister89 can you check this? <img width="627" height="526" alt="Image" src="https://github.com/user-attachments/assets/87b53b74-f590-4857-a295-49e1ea0f29f4" /> In the debug logs I could see the printer was basically stuck with this message: ``` 10:21:28,192 [backend.app.services.print_scheduler] Queue: printer 1 not available — connected=True, state=IDLE, awaiting_plate_clear=True ``` Now it works, although I keep getting these messages (which may explain why my SD card is always running full quite quickly): ``` 11:02:38,473 [backend.app.services.bambu_ftp] FTP connected successfully to 192.168.101.211 (model=P1S, prot_c=False) 11:02:38,486 [backend.app.services.bambu_ftp] Failed to delete /Wandhalterung.gcode: 550 11:02:38,507 [backend.app.main] SD card cleanup failed after 3 attempts for /Wandhalterung.gcode (file may linger on SD card) ``` Can the others check whether this is the same for them?

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

@Bademeister89 commented on GitHub (Apr 18, 2026):

“I have another log file here…
The problem still seems to persist! I made the changes.
Especially with larger files — I’ve printed a few small files since then, and those all worked without any issues.
But with the current file, I’m only having problems and can’t get it to work at all.”

bambuddy-support-20260418-170056.zip

@Bademeister89 commented on GitHub (Apr 18, 2026): “I have another log file here… The problem still seems to persist! I made the changes. Especially with larger files — I’ve printed a few small files since then, and those all worked without any issues. But with the current file, I’m only having problems and can’t get it to work at all.” [bambuddy-support-20260418-170056.zip](https://github.com/user-attachments/files/26856607/bambuddy-support-20260418-170056.zip)

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

@Percy2Live commented on GitHub (Apr 18, 2026):

@maziggy can you reopen this issue? I think something is still not right here

@Percy2Live commented on GitHub (Apr 18, 2026): @maziggy can you reopen this issue? I think something is still not right here

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

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

You're right, there is a lot of right here. Never saw such an curious install!!!

First of all the most interesting one.

"installation_id": "[REDACTED]",

This is something Bambuddy had in one of it's first versions, but it was removed months ago. Where the hell is this coming from? I have absolutely no clue.

Also you logs are flooded with errors like these:

2026-04-17 16:53:45,248 ERROR [sqlalchemy.pool.impl.AsyncAdaptedQueuePool] Exception terminating connection <AdaptedConnection <aiosqlite.core.Connection object at 0x154c38b70d50>>

2026-04-17 16:54:02,770 ERROR [sqlalchemy.pool.impl.AsyncAdaptedQueuePool] The garbage collector is trying to clean up non-checked-in connection <AdaptedConnection <aiosqlite.core.Connection object at 0x154c38b70d50>>, which will be terminated. Please ensure that SQLAlchemy pooled connections are returned to the pool explicitly, either by calling close() or by using appropriate context managers to manage their lifecycle.

asyncio.exceptions.CancelledError: Cancelled via cancel scope 154bfbd97f50 by <Task cancelling name='starlette.middleware.base.BaseHTTPMiddleware.call..call_next..coro' coro=<BaseHTTPMiddleware.call..call_next..coro() running at /usr/local/lib/python3.13/site-packages/starlette/middleware/base.py:144> cb=[TaskGroup._spawn..task_done() at /usr/local/lib/python3.13/site-packages/anyio/_backends/_asyncio.py:821]>

2026-04-17 16:55:24,819 WARNING [backend.app.main] AMS history recording failed: (sqlite3.OperationalError) database is locked

2026-04-17 17:00:44,438 WARNING [backend.app.services.bambu_mqtt] SERIAL Connection stale - no message for 80.3s, forcing reconnect

2026-04-17 19:30:46,903 ERROR [asyncio] Task was destroyed but it is pending!

2026-04-18 12:43:29,092 INFO [backend.app.services.bambu_mqtt] SERIAL Disconnect callback after stale reconnect (expected), rc=Unspecified error
2026-04-18 12:43:58,619 WARNING [backend.app.services.bambu_mqtt] SERIAL Connection stale - no message for 124.6s, forcing reconnect

2026-04-18 14:29:59,547 ERROR [backend.app.services.bambu_ftp] FTP connection lost during upload: [Errno 104] Connection reset by peer

Also this

2026-04-18 15:17:43,161 WARNING [backend.app.services.bambu_ftp] FTP connection failed to [IP]: [Errno 113] No route to host (type: OSError)
raise OSError(err, f'Connect call failed {address}')

is an OS error. Looks like your machine is loosing network connectivity.

I guess you know what you have to do ;)

@maziggy commented on GitHub (Apr 18, 2026): You're right, there is a lot of right here. Never saw such an curious install!!! First of all the most interesting one. > "installation_id": "[REDACTED]", This is something Bambuddy had in one of it's first versions, but it was removed months ago. Where the hell is this coming from? I have absolutely no clue. Also you logs are flooded with errors like these: > 2026-04-17 16:53:45,248 ERROR [sqlalchemy.pool.impl.AsyncAdaptedQueuePool] Exception terminating connection <AdaptedConnection <aiosqlite.core.Connection object at 0x154c38b70d50>> > 2026-04-17 16:54:02,770 ERROR [sqlalchemy.pool.impl.AsyncAdaptedQueuePool] The garbage collector is trying to clean up non-checked-in connection <AdaptedConnection <aiosqlite.core.Connection object at 0x154c38b70d50>>, which will be terminated. Please ensure that SQLAlchemy pooled connections are returned to the pool explicitly, either by calling ``close()`` or by using appropriate context managers to manage their lifecycle. > asyncio.exceptions.CancelledError: Cancelled via cancel scope 154bfbd97f50 by <Task cancelling name='starlette.middleware.base.BaseHTTPMiddleware.__call__.<locals>.call_next.<locals>.coro' coro=<BaseHTTPMiddleware.__call__.<locals>.call_next.<locals>.coro() running at /usr/local/lib/python3.13/site-packages/starlette/middleware/base.py:144> cb=[TaskGroup._spawn.<locals>.task_done() at /usr/local/lib/python3.13/site-packages/anyio/_backends/_asyncio.py:821]> > 2026-04-17 16:55:24,819 WARNING [backend.app.main] AMS history recording failed: (sqlite3.OperationalError) database is locked > 2026-04-17 17:00:44,438 WARNING [backend.app.services.bambu_mqtt] [[SERIAL]] Connection stale - no message for 80.3s, forcing reconnect > 2026-04-17 19:30:46,903 ERROR [asyncio] Task was destroyed but it is pending! > 2026-04-18 12:43:29,092 INFO [backend.app.services.bambu_mqtt] [[SERIAL]] Disconnect callback after stale reconnect (expected), rc=Unspecified error > 2026-04-18 12:43:58,619 WARNING [backend.app.services.bambu_mqtt] [[SERIAL]] Connection stale - no message for 124.6s, forcing reconnect > 2026-04-18 14:29:59,547 ERROR [backend.app.services.bambu_ftp] FTP connection lost during upload: [Errno 104] Connection reset by peer Also this > 2026-04-18 15:17:43,161 WARNING [backend.app.services.bambu_ftp] FTP connection failed to [IP]: [Errno 113] No route to host (type: OSError) raise OSError(err, f'Connect call failed {address}') is an OS error. Looks like your machine is loosing network connectivity. I guess you know what you have to do ;)

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

@Bademeister89 commented on GitHub (Apr 18, 2026):

I have Bambuddy running on my Unraid server, and it’s working perfectly!?!?!
However, the problems are getting worse. I managed to start a print, but it stopped after about 3 minutes… print failed… (see attached another logfile).

I will set up the Bambuddy installation again on another server and test it.

Thanks guys,

bambuddy-support-20260418-191554.zip

@Bademeister89 commented on GitHub (Apr 18, 2026): I have Bambuddy running on my Unraid server, and it’s working perfectly!?!?! However, the problems are getting worse. I managed to start a print, but it stopped after about 3 minutes… print failed… (see attached another logfile). I will set up the Bambuddy installation again on another server and test it. Thanks guys, [bambuddy-support-20260418-191554.zip](https://github.com/user-attachments/files/26858165/bambuddy-support-20260418-191554.zip)

BreizhHardware commented

2026-05-06 12:29:21 +02:00

Author

Owner

@akash191095 commented on GitHub (Apr 23, 2026):

Can this issue be due to system memory limitation?
I am facing same issues and also noticed weird behaviour where a print was auto restarted after finishing.

I had no issues like this when I was using orca slicer directly, but the system running bambuddy has the ram almost full due to other applications like the obico server.

Will try to increase the ram of the system and see if any improvement.

Bambuddy is awesome so thanks for all the hard work of all contributors and @maziggy and I hope to contribute more in the future.

@akash191095 commented on GitHub (Apr 23, 2026): Can this issue be due to system memory limitation? I am facing same issues and also noticed weird behaviour where a print was auto restarted after finishing. I had no issues like this when I was using orca slicer directly, but the system running bambuddy has the ram almost full due to other applications like the obico server. Will try to increase the ram of the system and see if any improvement. Bambuddy is awesome so thanks for all the hard work of all contributors and @maziggy and I hope to contribute more in the future.

BreizhHardware commented

2026-05-06 12:29:22 +02:00

Author

Owner

@akash191095 commented on GitHub (Apr 24, 2026):

Seems to be working fine now, steps I took:

moved it to a system with plenty of ram
fixed folder permission by running sudo chown -R 1000:1000 ./bambuddy/ and reinstalling using docker compose down -v (will delete all data)
Deleting the docker image and redownloading it
making sure I can run docker run hello-world without sudo
turned off clear plate feature

@akash191095 commented on GitHub (Apr 24, 2026): Seems to be working fine now, steps I took: - moved it to a system with plenty of ram - fixed folder permission by running `sudo chown -R 1000:1000 ./bambuddy/` and reinstalling using `docker compose down -v` (will delete all data) - Deleting the docker image and redownloading it - making sure I can run `docker run hello-world` without sudo - turned off clear plate feature

BreizhHardware referenced this issue

2026-05-06 12:34:44 +02:00

[PR #509] [CLOSED] Feature/422 #1057

BreizhHardware referenced this issue

2026-05-06 12:34:54 +02:00

[PR #588] [CLOSED] Feature/plate automation #1075

BreizhHardware referenced this issue

2026-05-06 12:35:21 +02:00

[PR #1029] [MERGED] v0.2.3 final #1149