mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #566] [Bug]: Cannot assign most of the spools in inventory to an AMS slot using UI #370
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
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-maziggy-1#370
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 @peter-k-de on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/566
Originally assigned to: @maziggy on GitHub.
Bug Description
While it is perfectly possible to manually assign any (non Bambu-) spool in the internal inventory to an AMS-Slot using the API, it is not possible to do so using the UI. This is since there are only 4 (apparently random, but always the same) spools shown in the assign dialog and the search field only search within those 4).
Screenshot - Trying to assign a Spool to the Second slot, configured as "PLA Silk" using Bambuddy ...
... I can only choose from those four totally unrelated spools:
It even doesn't matter whether this AMS slot is configured (using the printer menu or bambuddy) or not at all- this doesn't change which spools you can select from - it's always those random 4 spools. Demonstration: When I configure the Slot for Generic PETG Green profile (no spools in the inventory) the same spools are shown:
It only seems to be a UI Bug - since I can assign any Spool to the slot using POST /api/v1/inventory/assignments - not only those listed in this selection list.
Expected Behavior
You should be able to assign all spools in the filament inventory to an AMS slo (or even better: Only those whose Profiles match the configuration of the slot).
Steps to Reproduce
See Above
Printer Model
H2D
Bambuddy Version
v0.2.1.1
Printer Firmware Version
01.02.10.00
Installation Method
Manual (git clone)
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
bambuddy-support-20260301-175546.zip
Screenshots
No response
Additional Context
Support Bundle recorded After the Screenshots: Only Includes Configuring Slot 2 From PETG Green as in the screenshot + Trying to find one of my SILK PLA Spools in the Assign-Dialog, which was not possible, so the log doensn't include any spool assignments.
Checklist
@maziggy commented on GitHub (Mar 2, 2026):
Let's first make sure that we have a common understanding.
The current logic is:
when assigning a non Bambu Lab spool to a spool from inventory, the modal shows all non-archived inventory spools that are not RFID-tagged and not already assigned to another slot.
@peterk83de commented on GitHub (Mar 2, 2026):
Thanks a lot for looking into this 🤩
That explains it. I can confirm that the displayed spools match the logic you described — I just wasn’t aware of that behavior.
This is likely caused by my own setup: I’m using a (rather ugly, self-made) RFID scanner script for non-Bambu spools. The script creates a new (dummy) spool via the API and writes the NFC tag’s UUID into the tag_uid field. I then edit the remaining spool details (material, profile, etc.) directly in Bambuddy.
I assumed this would be fine, since my script sets data_origin to "pk_script" and not to something like "bambu_ams".
Given your explanation, it makes perfect sense that those spools are excluded from the assignment dialog — they technically count as RFID-tagged, which matches your filtering logic.
I’ll adjust my script to store the UID in the note field instead. That should work perfectly for my use case.
Thanks again for the clarification!
@maziggy commented on GitHub (Mar 2, 2026):
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!