[GH-ISSUE #538] [Feature]: Check if there's any Spool with not NFCTag associated of the same brand/color/type #347

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

Originally created by @wreuel on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/538

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

I buy 10 spools from Bambu. I receive them and keep them in storage. I also add all the details (colors, etc.) to the Filament/Inventory.

Later, when I take one of those spools and insert it into the AMS, the system creates a new entry on the Filament/Inventory for that spool.

Proposed Solution

When a spool is inserted into the AMS, if the Inventory already contains an entry with the same brand, color, and material type that does not yet have a tag associated, the system should prompt the user to link the inserted spool to that existing entry instead of creating a new one.

This would prevent duplicate inventory entries and improve inventory consistency.

Alternatives Considered

No response

Feature Category

Other

Priority

Would improve my workflow

Mockups or Examples

No response

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @wreuel on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/538 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case I buy 10 spools from Bambu. I receive them and keep them in storage. I also add all the details (colors, etc.) to the Filament/Inventory. Later, when I take one of those spools and insert it into the AMS, the system creates a new entry on the Filament/Inventory for that spool. ### Proposed Solution When a spool is inserted into the AMS, if the Inventory already contains an entry with the same brand, color, and material type that does not yet have a tag associated, the system should prompt the user to link the inserted spool to that existing entry instead of creating a new one. This would prevent duplicate inventory entries and improve inventory consistency. ### Alternatives Considered _No response_ ### Feature Category Other ### Priority Would improve my workflow ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-06 12:28:29 +02:00
Author
Owner

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

Is it for the internal inventory or Spoolman?

<!-- gh-comment-id:4046863387 --> @maziggy commented on GitHub (Mar 12, 2026): Is it for the internal inventory or Spoolman?
Author
Owner

@wreuel commented on GitHub (Mar 12, 2026):

I did thinking about the internal inventory

<!-- gh-comment-id:4046885962 --> @wreuel commented on GitHub (Mar 12, 2026): I did thinking about the internal inventory
Author
Owner

@wreuel commented on GitHub (Mar 15, 2026):

Even this one that is practically ready? Has all the necessary tests and so on? That don't make sense at all @maziggy

<!-- gh-comment-id:4062735859 --> @wreuel commented on GitHub (Mar 15, 2026): Even this one that is practically ready? Has all the necessary tests and so on? That don't make sense at all @maziggy
Author
Owner

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

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.


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

<!-- gh-comment-id:4116284936 --> @maziggy commented on GitHub (Mar 24, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/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#347
No description provided.