[GH-ISSUE #805] [Feature]: Prefer lowest remaining filament in auto-matching #535

New issue

Closed

opened 2026-05-07 00:11:23 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:11:23 +02:00

Owner

Originally created by @greatmastix on GitHub (Mar 25, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/805

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

When using auto-matching (virtual printer, queue, or archive pre-selection), BambuBuddy matches filaments based on color/type, which works great.

However, when multiple spools match the same criteria, the selection appears to follow AMS slot order rather than considering how much filament is left on each spool.

This makes it harder to efficiently use up partial spools, and often results in multiple nearly-empty rolls instead of consuming them one by one.

Proposed Solution

Introduce an optional setting to prioritize spools with the lowest remaining filament during auto-matching.

Suggested behavior:

When multiple spools match (same material/color/profile)
Sort them by remaining filament (ascending)
Select the spool with the least remaining filament first

Optional:

Add a toggle in settings: “Prefer lowest remaining filament first”
Fall back to current behavior if filament data is missing

Alternatives Considered

Manually rearranging spools in AMS slots (works but is inconvenient)
Manually overriding filament selection before each print
Accepting current behavior and managing leftovers manually

These workarounds are functional but reduce the convenience of auto-matching.

Also just to be transparent: I used AI to help structure this request, but the idea and use case come from my actual usage

Feature Category

Print Queue & Scheduling

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 @greatmastix on GitHub (Mar 25, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/805 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case When using auto-matching (virtual printer, queue, or archive pre-selection), BambuBuddy matches filaments based on color/type, which works great. However, when multiple spools match the same criteria, the selection appears to follow AMS slot order rather than considering how much filament is left on each spool. This makes it harder to efficiently use up partial spools, and often results in multiple nearly-empty rolls instead of consuming them one by one. ### Proposed Solution Introduce an optional setting to prioritize spools with the lowest remaining filament during auto-matching. Suggested behavior: When multiple spools match (same material/color/profile) Sort them by remaining filament (ascending) Select the spool with the least remaining filament first Optional: Add a toggle in settings: “Prefer lowest remaining filament first” Fall back to current behavior if filament data is missing ### Alternatives Considered Manually rearranging spools in AMS slots (works but is inconvenient) Manually overriding filament selection before each print Accepting current behavior and managing leftovers manually These workarounds are functional but reduce the convenience of auto-matching. Also just to be transparent: I used AI to help structure this request, but the idea and use case come from my actual usage ### Feature Category Print Queue & Scheduling ### 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:11:23 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:11:24 +02:00

Author

Owner

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

Good catch!

@maziggy commented on GitHub (Mar 25, 2026): Good catch!

BreizhHardware commented

2026-05-07 00:11:24 +02:00

Author

Owner

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

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

Please let me know if it works for you.

@maziggy commented on GitHub (Mar 31, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.