mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #364] [Bug]: beta-test report #227
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
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#227
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 @cimdDev on GitHub (Feb 13, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/364
Originally assigned to: @maziggy on GitHub.
Bug Description
First of all. nice work!
here are my test results so far:
1.1 - 1.5
Work as expected
2.1 - 2.11
Work as expected.
UX Feedback on 2.1:
If you accidentally click outside the card, the card closes and the entered content is lost. It would be better if the card stayed open or preserved the input to avoid losing work.
3.1 - 4.2
Work as expected overall, but I noticed one detail regarding AMS + Bambu RFID handling:
When the AMS reads a Bambu Lab RFID spool, it sends color and material type presumably also the SN. Bambu Studio/the printer shows the spool as full because the remaining percentage has not yet been measured.
Bambuddy correctly:
However, at this stage the spool is displayed like a manually assigned/non-RFID spool.
After the printer measures the spool, Bambuddy then shows it as a “native BL spool”.
This behavior is not wrong, but the status change might be slightly confusing at first glance.
An other behaviorI noticed with Non-Bambu (non-RFID) spool:
When a non-Bambu spool is inserted into the AMS:
On the printer / Bambu Studio, the slot is shown as empty and after inserting the spool as non-empty, but without details (question mark).
In Bambuddy, the slot is still shown as empty unless a profile has already been assigned prior.
On an non empty slot a profile can be configured and then the spool can be assigned manually.
Suggestion:
It may be clearer to display the slot as non-empty but without profile/spool assignment, similar to how Bambu Studio indicates an unknown spool. This would better reflect the physical state of the slot and avoid the impression that it is empty.
Currently, a spool must exist before it can be assigned.
Maybe it would be helpful to be able to create a new spool directly from the assign card and then assigning it after creation.
That’s what I have tested so far.
It already works well and looks very promising.
I will continue testing and add further results to this report later.
Expected Behavior
Beta Test on X1E and H2D Pro
Steps to Reproduce
BETA_TEST_PLAN.md
Printer Model
X1E
Bambuddy Version
0.2.0b3
Printer Firmware Version
1.02.02.00
Installation Method
docker pull
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
[nice-to-have feature]: Material cost and inventory capital
Filament cost tracking would be a very useful addition to the overall concept of Bambuddy
Suggestion:
Checklist
@maziggy commented on GitHub (Feb 14, 2026):
Very nice and helpful! Thanks!!!
@maziggy commented on GitHub (Feb 15, 2026):
Major refactoring of AMS slot assignments, spool inventory and filament usage tracking.
I'll push a new beta image today and let you know.
@cimdDev commented on GitHub (Feb 15, 2026):
minor UI glitch found in 0.2.0b4 when adding a new spool (Edge browser)
When using Edge at 80% zoom, the scrollbar appears and disappears depending on where you hover over in the Form, making it very difficult or impossible to select a color.
https://github.com/user-attachments/assets/daae80f8-9ac6-4b64-a335-3c007f6cf8d8
I could not replicate this in Chrome.
I have not tested this in Firefox or other browser
@maziggy commented on GitHub (Feb 16, 2026):
I'm using Firefox and it works.
Fixed in branch 0.2.0b. Will be included in next beta image.
@cimdDev commented on GitHub (Feb 16, 2026):
I’m currently testing 7. Usage Tracking — Non‑BL Spools (3MF Estimates).
I’m unable to capture any "3MF fallback available" entries in the logs, and the filament usage doesn’t seem to update either.
It might be related to the queue not finding the correct archive ID, even though the print starts without any problem.
I uploaded the file to the file manager and queued it from there, so an archive ID should exist.
X1E PLA cube.gcode.3mf -> X1E 001
H2D ABS cube.gcode.3mf -> H2D Pro 002
bambuddy-support-20260216-110948.zip
@maziggy commented on GitHub (Feb 16, 2026):
Think I've found the issue. Please pull branch 0.2.0b and try again. Thanks!
@cimdDev commented on GitHub (Feb 16, 2026):
Still have the missing ID
The filament usage did update for non‑BL spools on my X1E, but I started the print whit "Print" not “Queue ASAP” . I’m not sure if that difference affects the behavior of print start.
For my H2D I get no usage update regardless. will continue testing and collecting logs
@maziggy commented on GitHub (Feb 16, 2026):
Wait wait....
@maziggy commented on GitHub (Feb 16, 2026):
Archive #Null is fixed in branch 0.2.0b.
Waiting for feedback regarding filament usage.
@cimdDev commented on GitHub (Feb 16, 2026):
I think the archive #null is a frontend issue in the printer card:
in the queue view it is resolved:
yes, it is internal tracking and yes, I have assigned the slot to a config and spool
One more detail that might matter for the H2D Pro: this is happening on the second AMS unit, (left nozzle), that unit is an AMS HT.
will try with slots in the first AMS. unfortunately both H2D are productive rn. will have to wait a bit for further testing
@maziggy commented on GitHub (Feb 16, 2026):
Print was finished or aborted?
@cimdDev commented on GitHub (Feb 16, 2026):
On H2D the two test print finished successfully. On X1E I tried both successful and canceled prints.
The Green filament in H2D is still listed as never used, even though prints were completed
I'm not sure if it matters but in the archive the prints are taged as "Source" but are .gcode.3mf files
some have the file hash and some the file name as title..?
@maziggy commented on GitHub (Feb 16, 2026):
Found multiple bugs. Please pull branch 0.2.0b and try again. Thanks.
But I cannot reproduce the hash name.
@cimdDev commented on GitHub (Feb 16, 2026):
Filament Usage on X1E seem to work as intended. Beta test plan: 6.1-7.3
on the H2Ds there are some issues. I did not print in black PLA today, this is the only spool that was synched to inventory: on an RFID read from the printer maybe? all the other spools are unused.
Regarding hash name, I plan to reset the database tomorrow and test again on a fresh install of 0.2.0b, to rule out inconsistencies from previous data. Let me know if you believe this step is unnecessary, or if you prefer testing with the current DB state before resetting.
@maziggy commented on GitHub (Feb 16, 2026):
This is working on the normal H2D. So most likely it's another "pro models do it different" foo. So annoying.
Anyway....I need debug logs to see the MQTT stream.
@cimdDev commented on GitHub (Feb 16, 2026):
I can do clean test runs on H2D tomorrow afternoon.
I recorded the logs from the last 180min.
but I only get the last 30min in the support package:
bambuddy-support-20260216-155750.zip
@maziggy commented on GitHub (Feb 16, 2026):
Not that easy. Will post something regarding the issue on Discord shortly.
@maziggy commented on GitHub (Feb 16, 2026):
False alarm....just had the right idea :)
@maziggy commented on GitHub (Feb 17, 2026):
Found a model independant solution :) Please pull branch 0.2.0b and try again.
@cimdDev commented on GitHub (Feb 17, 2026):
Short update: I get material usage synced with the H2D Pro with both BL and non‑BL Spools. I'm running 0.2.1b.
I’ll test this further and report here if I encounter any anomalies. thx!
@maziggy commented on GitHub (Feb 19, 2026):
Please try again with latest beta release 0.2.1b.