1
0
Fork 0
mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #149] [Feature]: Link existing Spoolman spools #90

Closed
opened 2026-05-07 00:06:00 +02:00 by BreizhHardware · 7 comments

Originally created by @Frdnspnzr on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/149

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

I keep unopened filament spools registered in Spoolman for stock overview. Bambuddy automatically creates and updates spools in Spoolman based on the AMS RFID data.

When an unopened spool is inserted into the AMS for the first time, Bambuddy always creates a new spool, because the existing stock entry in Spoolman has no tag associated with it yet. This leads to duplicate spool entries and requires manual cleanup to keep the inventory consistent.

Proposed Solution

Introduce an optional, configurable matching mechanism for newly detected AMS spools.

When enabled, Bambuddy could attempt to match a newly detected spool to an existing spool entry in Spoolman using the filament type and weight.

The matching eligibility could be implemented via an additional field in Spoolman, allowing users to explicitly designate which spools may be automatically matched when an RFID is detected for the first time.

Alternatives Considered

Pre-filling the tag field in Spoolman would solve the issue, but reading the tags of unopened and sealed spools is not exactly easy.

Feature Category

Spoolman Integration

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 @Frdnspnzr on GitHub (Jan 24, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/149 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case I keep unopened filament spools registered in Spoolman for stock overview. Bambuddy automatically creates and updates spools in Spoolman based on the AMS RFID data. When an unopened spool is inserted into the AMS for the first time, Bambuddy always creates a new spool, because the existing stock entry in Spoolman has no tag associated with it yet. This leads to duplicate spool entries and requires manual cleanup to keep the inventory consistent. ### Proposed Solution Introduce an optional, configurable matching mechanism for newly detected AMS spools. When enabled, Bambuddy could attempt to match a newly detected spool to an existing spool entry in Spoolman using the filament type and weight. The matching eligibility could be implemented via an additional field in Spoolman, allowing users to explicitly designate which spools may be automatically matched when an RFID is detected for the first time. ### Alternatives Considered Pre-filling the tag field in Spoolman would solve the issue, but reading the tags of unopened and sealed spools is not exactly easy. ### Feature Category Spoolman Integration ### 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
Author
Owner

@maziggy commented on GitHub (Jan 25, 2026):

There's another upcoming Buddy. Perhaps this is interesting for you?

https://spoolbuddy.cool

<!-- gh-comment-id:3796014621 --> @maziggy commented on GitHub (Jan 25, 2026): There's another upcoming Buddy. Perhaps this is interesting for you? https://spoolbuddy.cool
Author
Owner

@Frdnspnzr commented on GitHub (Jan 25, 2026):

I’ve seen that and it seems nice, but it still requires buying additional hardware, which I could already do today. I would prefer a software-only solution, even if it is arguably less robust, as it would still be fine for my use case.

<!-- gh-comment-id:3797232568 --> @Frdnspnzr commented on GitHub (Jan 25, 2026): I’ve seen that and it seems nice, but it still requires buying additional hardware, which I could already do today. I would prefer a software-only solution, even if it is arguably less robust, as it would still be fine for my use case.
Author
Owner

@maziggy commented on GitHub (Jan 26, 2026):

What if you have multiple unused spools with same meterial and weight (which is not unusual)?

I would prefer the following:

Add a new setting, if new spools should be added automatically or not. If disabled and a new Bambu Lab spool is inserted, check if there are any spools in inventory, that have no tag assigned. Show them and add the tag to the selected spool.

<!-- gh-comment-id:3798002562 --> @maziggy commented on GitHub (Jan 26, 2026): What if you have multiple unused spools with same meterial and weight (which is not unusual)? I would prefer the following: Add a new setting, if new spools should be added automatically or not. If disabled and a new Bambu Lab spool is inserted, check if there are any spools in inventory, that have no tag assigned. Show them and add the tag to the selected spool.
Author
Owner

@maziggy commented on GitHub (Jan 26, 2026):

This is more complex and needs deeper investigations and testing. We need to deal with Bambu Lab spools, non Bambu Lab spools and in the future with the new Spoolbuddy system. Have to tag it as "future feature" for now, but this is definitely something that is going to be implemented.

<!-- gh-comment-id:3798333977 --> @maziggy commented on GitHub (Jan 26, 2026): This is more complex and needs deeper investigations and testing. We need to deal with Bambu Lab spools, non Bambu Lab spools and in the future with the new Spoolbuddy system. Have to tag it as "future feature" for now, but this is definitely something that is going to be implemented.
Author
Owner

@piatho-1 commented on GitHub (Jan 29, 2026):

The solution i am currently use here is building on a simply concept that works for both RFID enabled spools and non-RFID spools.
I have a custom field in Spoolman that holds a tag id. The tag id is either the tag id coming from RFID or is manually maintained.

My app to manage the printer and AMS is reading the AMS and either tyring to match with Spoolman by the existing tag ID or allow me to add a custom id number myself.

If my application cannot find find a tag id to match (eg first time read in AMS) i get a notification with the read tag id to manually assign them in Spoolman. Once confirmed it will do the sync as usual.

<!-- gh-comment-id:3817818820 --> @piatho-1 commented on GitHub (Jan 29, 2026): The solution i am currently use here is building on a simply concept that works for both RFID enabled spools and non-RFID spools. I have a custom field in Spoolman that holds a tag id. The tag id is either the tag id coming from RFID or is manually maintained. My app to manage the printer and AMS is reading the AMS and either tyring to match with Spoolman by the existing tag ID or allow me to add a custom id number myself. If my application cannot find find a tag id to match (eg first time read in AMS) i get a notification with the read tag id to manually assign them in Spoolman. Once confirmed it will do the sync as usual.
Author
Owner

@bambuman commented on GitHub (Jan 31, 2026):

@Frdnspnzr, sorry if this is off-topic or feels like a bit of self-promotion.

But if you have an Android phone with NFC, you can import unopened and sealed spools into Spoolman using BambuMan.App.

It won't work through foil bags, but everything else is imported automatically into Spoolman.

I'm currently evaluation bambuddy and tag uuid goes to the same field as in bambuddy, have to test if filament usage also updates :)

<!-- gh-comment-id:3828855096 --> @bambuman commented on GitHub (Jan 31, 2026): @Frdnspnzr, sorry if this is off-topic or feels like a bit of self-promotion. But if you have an Android phone with NFC, you can import unopened and sealed spools into Spoolman using [BambuMan.App](https://github.com/bambuman/BambuMan.App). It won't work through foil bags, but everything else is imported automatically into Spoolman. I'm currently evaluation bambuddy and tag uuid goes to the same field as in bambuddy, have to test if filament usage also updates :)
Author
Owner

@maziggy commented on GitHub (Feb 2, 2026):

This is available in branch 0.1.7b. Please check and let me know.

<!-- gh-comment-id:3835078152 --> @maziggy commented on GitHub (Feb 2, 2026): This is available in branch 0.1.7b. Please check and let me know.
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-maziggy-1#90
No description provided.