starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #829] [Feature]: Define Printer Location, used as Spool Location when removed from AMS #557

New issue

Open

opened 2026-05-06 12:30:54 +02:00 by BreizhHardware · 6 comments

BreizhHardware commented

2026-05-06 12:30:54 +02:00

Owner

Originally created by @ic9888 on GitHub (Mar 26, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/829

Originally assigned to: @netscout2001 on GitHub.

Problem or Use Case

In the scenario where you have printers in multiple locations, e.g. Office, Garage, Print Farm Wing A, etc. it can be challenging to know where your spools are when not in an AMS.

Oh, I need some filament x in the Garage, did I have a spool of in there or is it in the Office?

Proposed Solution

Create a location attribute for printers, e.g. Garage and when a spool is removed from that printers AMS bambuddy automatically assigns the spool to the location stored in the printers location attribute, that way you know where your partially used spools are stored, or at least where they were used last.

Happy to contribute to developing this if someone can give me some guidance, unfortunately my skills lie more in prompting claude to script adhoc network audits and montoring...

Alternatives Considered

I've tried both the internal filament management and the spool man integration and both have an empty location that's begging to be put to use :-)

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 @ic9888 on GitHub (Mar 26, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/829 Originally assigned to: @netscout2001 on GitHub. ### Problem or Use Case In the scenario where you have printers in multiple locations, e.g. Office, Garage, Print Farm Wing A, etc. it can be challenging to know where your spools are when not in an AMS. Oh, I need some filament x in the Garage, did I have a spool of in there or is it in the Office? ### Proposed Solution Create a location attribute for printers, e.g. Garage and when a spool is removed from that printers AMS bambuddy automatically assigns the spool to the location stored in the printers location attribute, that way you know where your partially used spools are stored, or at least where they were used last. Happy to contribute to developing this if someone can give me some guidance, unfortunately my skills lie more in prompting claude to script adhoc network audits and montoring... ### Alternatives Considered I've tried both the internal filament management and the spool man integration and both have an empty location that's begging to be put to use :-) ### Feature Category Spoolman Integration ### Priority Would improve my workflow ### Mockups or Examples _No response_ ### Contribution - [x] 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 added the

enhancement

contrib

labels

2026-05-06 12:30:54 +02:00

BreizhHardware commented

2026-05-06 12:30:55 +02:00

Author

Owner

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

The location field in both inventories is already in use. As soon as a spool is detected pr assigned to an AMS slot, the location field has - for example - "H2D-1 B4".

What we coul do is:

Add a new field "storage". If a spool is recognized by RFID or assigned to a slot, the new field is populated with the configured printer location.

Would that match your workflow?

@maziggy commented on GitHub (Mar 27, 2026): The location field in both inventories is already in use. As soon as a spool is detected pr assigned to an AMS slot, the location field has - for example - "H2D-1 B4". What we coul do is: Add a new field "storage". If a spool is recognized by RFID or assigned to a slot, the new field is populated with the configured printer location. Would that match your workflow?

BreizhHardware commented

2026-05-06 12:30:55 +02:00

Author

Owner

@ic9888 commented on GitHub (Mar 28, 2026):

Sure if you think that's the best approach. But then the new storage field sync with the existing spool location field right? There would be an extra storage field in spoolman too?

I figured it would be easier to just have another value in the existing location field and then an extra field wouldn't be needed. Perhaps it would be easier to just tag it with the printer name rather than a new storage field, that way you know where it was last used but it's obvious that it's not in the AMS.

@ic9888 commented on GitHub (Mar 28, 2026): Sure if you think that's the best approach. But then the new storage field sync with the existing spool location field right? There would be an extra storage field in spoolman too? I figured it would be easier to just have another value in the existing location field and then an extra field wouldn't be needed. Perhaps it would be easier to just tag it with the printer name rather than a new storage field, that way you know where it was last used but it's obvious that it's not in the AMS.

BreizhHardware commented

2026-05-06 12:30:55 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 5, 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 (Apr 5, 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-06 12:30:55 +02:00

Author

Owner

@ic9888 commented on GitHub (Apr 8, 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.

I'm happy to work on this (with my limited but improving agentic enabled skills) if that would be preferred?

@ic9888 commented on GitHub (Apr 8, 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. I'm happy to work on this (with my limited but improving agentic enabled skills) if that would be preferred?

BreizhHardware commented

2026-05-06 12:30:55 +02:00

Author

Owner

@TravisWilder commented on GitHub (Apr 15, 2026):

I like the idea of having a field to store the storage location. For me a free text field would be fine.
It should be for sure also an available field for spools on stock.
A full location system like in spoolease I do not need.
It would be also nice if the location which currently shows the AMS slot would switch to the storage field if the spooling is not in the AMS

@TravisWilder commented on GitHub (Apr 15, 2026): I like the idea of having a field to store the storage location. For me a free text field would be fine. It should be for sure also an available field for spools on stock. A full location system like in spoolease I do not need. It would be also nice if the location which currently shows the AMS slot would switch to the storage field if the spooling is not in the AMS

BreizhHardware commented

2026-05-06 12:30:55 +02:00

Author

Owner

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

@netscout2001

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