starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #660] [Bug]: Large print not correctly displaying #430

New issue

Closed

opened 2026-05-06 12:29:25 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

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

Owner

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

Originally assigned to: @maziggy on GitHub.

Bug Description

I've printed this model from makerworld: https://makerworld.com/en/models/1768086

It shows in the archive as completed and it know the time it took to print, it even has the green gcode tag but I cant see the gcode preview or any other statistic.

(originally written for v0.2.1.1 now in v0.2.2b2 I get the electricity measure displayed)

Expected Behavior

see statistics

Steps to Reproduce

honestly no idea. Just try to print the model.

Printer Model

Bambuddy Version

v0.2.2b2

Printer Firmware Version

01.07.00.00

Installation Method

Docker

Operating System

Docker

Relevant Logs / Support Package

Screenshots

Additional Context

No response

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 @PasDoe on GitHub (Mar 9, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/660 Originally assigned to: @maziggy on GitHub. ### Bug Description I've printed this model from makerworld: https://makerworld.com/en/models/1768086 It shows in the archive as completed and it know the time it took to print, it even has the green gcode tag but I cant see the gcode preview or any other statistic. (originally written for v0.2.1.1 now in v0.2.2b2 I get the electricity measure displayed) ### Expected Behavior see statistics ### Steps to Reproduce honestly no idea. Just try to print the model. ### Printer Model A1 ### Bambuddy Version v0.2.2b2 ### Printer Firmware Version 01.07.00.00 ### Installation Method Docker ### Operating System Docker ### Relevant Logs / Support Package ```shell ``` ### Screenshots <img width="423" height="466" alt="Image" src="https://github.com/user-attachments/assets/4a3739a2-94ff-43de-8edc-dbf187786a71" /> <img width="673" height="472" alt="Image" src="https://github.com/user-attachments/assets/b7316df4-fedb-4682-be39-8a31b93fe0f7" /> ### Additional Context _No response_ ### 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-06 12:29:25 +02:00

closed this issue
added the
Closed due to inactivity

bug
labels

BreizhHardware commented

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

Author

Owner

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

There's something wrong with your setup. Please update a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Mar 9, 2026): There's something wrong with your setup. Please update a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

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

Author

Owner

@PasDoe commented on GitHub (Mar 9, 2026):

bambuddy-support-20260309-192301.zip

Attached the support bundle.
I don't exactly know what I should capture but I've opened the archive and the 3d preview window.

PS: The countdown for the live timer starts at -60m and goes to -60m 59s, should I open another issue for this?

@PasDoe commented on GitHub (Mar 9, 2026): [bambuddy-support-20260309-192301.zip](https://github.com/user-attachments/files/25850251/bambuddy-support-20260309-192301.zip) Attached the support bundle. I don't exactly know what I should capture but I've opened the archive and the 3d preview window. PS: The countdown for the live timer starts at -60m and goes to -60m 59s, should I open another issue for this?

BreizhHardware commented

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

Author

Owner

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

I've analyzed the logs and found several things going on.

Main issue: Large file FTP timeout

The file Pikachu_2-piece_Hueforge.gcode.3mf is ~28 MB — Hueforge models tend to be massive. When a print starts, Bambuddy tries to download the 3MF from the printer via FTP to extract thumbnails, 3D model data, and gcode statistics. Your A1's FTP server can't transfer 28 MB within the 60-second timeout while it's actively printing. After the timeout, the connection drops with an SSL error and all retries fail. Bambuddy then creates a "fallback" archive with no 3MF data — which is why you see no thumbnail, no 3D preview, and "0 B" file size. The print time still shows because that comes from MQTT, not the 3MF.

I can see that when the printer was idle (March 9th), the same file downloaded successfully in about 2.5 minutes — so the file itself is fine, it's just too big to grab during printing.

Fix: I've just pushed higher FTP timeout options (180s and 300s) to branch 0.2.2b3. Pull the latest changes and go to Settings → FTP → Connection Timeout and set it to 180s or 300s. The previous max of 120s isn't enough for your 28 MB file.

Other things I noticed in the logs:

Unstable MQTT connection — Your MQTT connection drops frequently: "Connection stale" warnings (no message for 60–85 seconds) about 10 times over the log period, plus multiple disconnects with "Keep alive timeout" and "Unspecified error". Your WiFi signal ranges from -49 to -61 dBm, which is borderline. This is likely contributing to the FTP issues too — both FTP and MQTT share the same WiFi link. If possible, moving the printer closer to the router (or vice versa) would help with both problems.

@maziggy commented on GitHub (Mar 10, 2026): I've analyzed the logs and found several things going on. **Main issue: Large file FTP timeout** The file Pikachu_2-piece_Hueforge.gcode.3mf is ~28 MB — Hueforge models tend to be massive. When a print starts, Bambuddy tries to download the 3MF from the printer via FTP to extract thumbnails, 3D model data, and gcode statistics. Your A1's FTP server can't transfer 28 MB within the 60-second timeout while it's actively printing. After the timeout, the connection drops with an SSL error and all retries fail. Bambuddy then creates a "fallback" archive with no 3MF data — which is why you see no thumbnail, no 3D preview, and "0 B" file size. The print time still shows because that comes from MQTT, not the 3MF. I can see that when the printer was idle (March 9th), the same file downloaded successfully in about 2.5 minutes — so the file itself is fine, it's just too big to grab during printing. Fix: I've just pushed higher FTP timeout options (180s and 300s) to branch 0.2.2b3. Pull the latest changes and go to Settings → FTP → Connection Timeout and set it to 180s or 300s. The previous max of 120s isn't enough for your 28 MB file. **Other things I noticed in the logs:** - Unstable MQTT connection — Your MQTT connection drops frequently: "Connection stale" warnings (no message for 60–85 seconds) about 10 times over the log period, plus multiple disconnects with "Keep alive timeout" and "Unspecified error". Your WiFi signal ranges from -49 to -61 dBm, which is borderline. This is likely contributing to the FTP issues too — both FTP and MQTT share the same WiFi link. If possible, moving the printer closer to the router (or vice versa) would help with both problems.

BreizhHardware commented

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

Author

Owner

@PasDoe commented on GitHub (Mar 13, 2026):

bambuddy-support-20260313-164524.zip

I started the print again and looked at the live application log. Since I already finished printing I stopped the print after seeing "failed after 4 attempts"
If I see this right it failed after a whole 6 seconds.

sorry for clearing the log. tbh I thought the "clear" button just cleared the window and only show new entries instead of actually clearing the whole log.

Looking in the log I see two FTP connections, one with 30 and one with 300 seconds. I tried both 180s and 300s settings.

I will see if I can get the wifi closer to the printer and will try it again. Could take some time tho.

@PasDoe commented on GitHub (Mar 13, 2026): [bambuddy-support-20260313-164524.zip](https://github.com/user-attachments/files/25975385/bambuddy-support-20260313-164524.zip) I started the print again and looked at the live application log. Since I already finished printing I stopped the print after seeing "failed after 4 attempts" If I see this right it failed after a whole 6 seconds. sorry for clearing the log. tbh I thought the "clear" button just cleared the window and only show new entries instead of actually clearing the whole log. Looking in the log I see two FTP connections, one with 30 and one with 300 seconds. I tried both 180s and 300s settings. I will see if I can get the wifi closer to the printer and will try it again. Could take some time tho.

BreizhHardware commented

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

Author

Owner

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

Bambuddy cannot connect to your printer via FTPS and MQTT.

Your Docker network is not running in mode host.

@maziggy commented on GitHub (Mar 14, 2026): Bambuddy cannot connect to your printer via FTPS and MQTT. Your Docker network is not running in mode host.

BreizhHardware referenced this issue

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

[PR #430] [MERGED] feat(queue): improve mobile responsiveness for QueuePage #1038