[GH-ISSUE #566] [Bug]: Cannot assign most of the spools in inventory to an AMS slot using UI #371

Closed
opened 2026-05-06 12:28:50 +02:00 by BreizhHardware · 3 comments

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 ...

Image

... I can only choose from those four totally unrelated spools:

Image

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:

Image

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

  • 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 @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 ... <img width="345" height="318" alt="Image" src="https://github.com/user-attachments/assets/48a69e7f-57fe-45fc-b9a4-b88547f8a944" /> ... I can only choose from those four totally unrelated spools: <img width="472" height="595" alt="Image" src="https://github.com/user-attachments/assets/344d062c-b072-4575-a039-4def60bbe041" /> 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: <img width="472" height="595" alt="Image" src="https://github.com/user-attachments/assets/fea6c97b-0573-481d-8b51-b4234495f6bf" /> 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](https://github.com/user-attachments/files/25663776/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 - [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:28:50 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@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.

<!-- gh-comment-id:3982409865 --> @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.
Author
Owner

@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!

<!-- gh-comment-id:3982665544 --> @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!
Author
Owner

@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!

<!-- gh-comment-id:3982695627 --> @maziggy commented on GitHub (Mar 2, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#371
No description provided.