starred/bambuddy-maziggy-1

Fork 0

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

[GH-ISSUE #729] [Feature]: Tag system for filament #484

New issue

Closed

opened 2026-05-07 00:10:42 +02:00 by BreizhHardware · 8 comments

BreizhHardware commented

2026-05-07 00:10:42 +02:00

Owner

Originally created by @hollycroftlabs on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/729

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Not sure if this is a bug or feature request as there is a "Delete Tag" button against each filmament...but in any case.

It would be great if i could tag filaments for their use. I have some that are critical and need to re order as they get low, and others not so much. A tag system would help me organise filaments further.

Proposed Solution

Ideally you would be bale to ag a certain filament type and colour eg Bambu Labs PLA Matte Ash Gray. That way whenever you add more spools they get that tag by default.

For each tag you can set lower limits when you get filament level warnings to customise the warnings for each filament type.

Alternatives Considered

Ive tried looking in the menu for each filament and there is a "Delete Tag" button but it greyed out in most cases. Where it wasnt greyed out i clicked it, but unsure what it does!

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 @hollycroftlabs on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/729 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Not sure if this is a bug or feature request as there is a "Delete Tag" button against each filmament...but in any case. It would be great if i could tag filaments for their use. I have some that are critical and need to re order as they get low, and others not so much. A tag system would help me organise filaments further. ### Proposed Solution Ideally you would be bale to ag a certain filament type and colour eg Bambu Labs PLA Matte Ash Gray. That way whenever you add more spools they get that tag by default. For each tag you can set lower limits when you get filament level warnings to customise the warnings for each filament type. ### Alternatives Considered Ive tried looking in the menu for each filament and there is a "Delete Tag" button but it greyed out in most cases. Where it wasnt greyed out i clicked it, but unsure what it does! ### 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-07 00:10:42 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

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

Not sure if I understand your request.

Why should one want to remove a tag from a Bambu Lab spool?

The "Delete Tag" button is exactly doing what the name says: it deletes the tag from the spool?!

@maziggy commented on GitHub (Mar 17, 2026): Not sure if I understand your request. Why should one want to remove a tag from a Bambu Lab spool? The "Delete Tag" button is exactly doing what the name says: it deletes the tag from the spool?!

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

@hollycroftlabs commented on GitHub (Mar 17, 2026):

Lets understand what we mean by "Tag". I'm using it in the taxonomy sense, a tab/label against a spool/filament type.

So for example, I might want to tag my spools that are used in production items, by add a tag/label of "Production". I might want to set a different lower alert limit for these spools specifically.

Going further i have 2 products, 1 uses 50g of filament, 1 uses 350g. I might want to tag/label those spools differently and then set different alert limits accordingly.

I also have some spools that i just mess around with, they are for prototyping/personal projects so i don't care if they run out.

I guess I'm thinking this would be a way for me to filter/sort my filaments. I could then use tags/labels to show me my current filaments by product (creating a tag/label for each product).

You could then assign these tags/labels to a filament type. Lets say i want all my Bambu Labs Matte Ash Gray filaments to have a tag/label of "production" and "product x" then anytime the systems adds a new spool these tags/labels get added automatically.

@hollycroftlabs commented on GitHub (Mar 17, 2026): Lets understand what we mean by "Tag". I'm using it in the taxonomy sense, a tab/label against a spool/filament type. So for example, I might want to tag my spools that are used in production items, by add a tag/label of "Production". I might want to set a different lower alert limit for these spools specifically. Going further i have 2 products, 1 uses 50g of filament, 1 uses 350g. I might want to tag/label those spools differently and then set different alert limits accordingly. I also have some spools that i just mess around with, they are for prototyping/personal projects so i don't care if they run out. I guess I'm thinking this would be a way for me to filter/sort my filaments. I could then use tags/labels to show me my current filaments by product (creating a tag/label for each product). You could then assign these tags/labels to a filament type. Lets say i want all my Bambu Labs Matte Ash Gray filaments to have a tag/label of "production" and "product x" then anytime the systems adds a new spool these tags/labels get added automatically.

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

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

Ahhhh....got it.

@maziggy commented on GitHub (Mar 17, 2026): Ahhhh....got it.

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

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

Before we commit to building this, I'd like to gauge community interest. If you'd find this feature useful, please give this issue a thumbs up (👍) reaction so we can prioritize accordingly.

@maziggy commented on GitHub (Mar 24, 2026): Before we commit to building this, I'd like to gauge community interest. If you'd find this feature useful, please give this issue a thumbs up (👍) reaction so we can prioritize accordingly.

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 20, 2026):

@netscout2001

@maziggy commented on GitHub (Apr 20, 2026): @netscout2001

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

@netscout2001 commented on GitHub (Apr 20, 2026):

@maziggy this is not a spoolman thing but a tag thing. For spoolman it is out of scope.

@netscout2001 commented on GitHub (Apr 20, 2026): @maziggy this is not a spoolman thing but a tag thing. For spoolman it is out of scope.

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 22, 2026):

You're right, sorry.

@maziggy commented on GitHub (Apr 22, 2026): You're right, sorry.

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

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

Available/Fixed in branch dev and available with the next release or daily build.

Shipping is the cheap version that covers the underlying need without taking on the full taxonomy:

Per-spool Category — free text on the spool form (autocompletes from categories already in use across your other spools, so "Production" stays consistent and you don't accidentally end up with "production" / "prod" duplicates). Optional. Shows up as a filter chip in the inventory list once at least one spool has a category set.
Per-spool low-stock threshold — % override that defaults to the global setting if you leave it blank. So you can set "Production" PLA spools to alert at 50 % while letting prototype spools stay quiet until 5 %. Honored by both the stat-card "Low Stock" count and the "Low Stock" filter.

What's not shipping from the original proposal:

Multi-tag taxonomy (one spool → many tags)
Auto-apply rules ("all Bambu Matte Ash Gray inherits Production")
A separate per-tag alerts/notifications page

Those would have been ~5× the scope for the same underlying value. If demand for true tags grows past the current 3 thumbs-up, the design can layer on top of these fields without breaking anything.

One side fix while we were here: the Delete Tag button you mentioned in the original post (the one that's greyed out most of the time) is renamed to Clear RFID Tag. It only ever cleared the RFID UID/UUID off the spool record so the row could be re-attached to a different physical spool — calling it "Delete Tag" made it look like a taxonomy delete, which is exactly the confusion you flagged.

Closing this. If the new fields don't cover your workflow, please open a fresh issue with the specific gap and we'll take it from there.

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

@maziggy commented on GitHub (Apr 25, 2026): Available/Fixed in branch dev and available with the next release or daily build. Shipping is the cheap version that covers the underlying need without taking on the full taxonomy: - Per-spool Category — free text on the spool form (autocompletes from categories already in use across your other spools, so "Production" stays consistent and you don't accidentally end up with "production" / "prod" duplicates). Optional. Shows up as a filter chip in the inventory list once at least one spool has a category set. - Per-spool low-stock threshold — % override that defaults to the global setting if you leave it blank. So you can set "Production" PLA spools to alert at 50 % while letting prototype spools stay quiet until 5 %. Honored by both the stat-card "Low Stock" count and the "Low Stock" filter. What's not shipping from the original proposal: - Multi-tag taxonomy (one spool → many tags) - Auto-apply rules ("all Bambu Matte Ash Gray inherits Production") - A separate per-tag alerts/notifications page Those would have been ~5× the scope for the same underlying value. If demand for true tags grows past the current 3 thumbs-up, the design can layer on top of these fields without breaking anything. One side fix while we were here: the Delete Tag button you mentioned in the original post (the one that's greyed out most of the time) is renamed to Clear RFID Tag. It only ever cleared the RFID UID/UUID off the spool record so the row could be re-attached to a different physical spool — calling it "Delete Tag" made it look like a taxonomy delete, which is exactly the confusion you flagged. Closing this. If the new fields don't cover your workflow, please open a fresh issue with the specific gap and we'll take it from there. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!