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 #261] [Feature]: Per filament price setting #161

New issue

Closed

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

BreizhHardware commented

2026-05-07 00:06:59 +02:00

Owner

Originally created by @Roycinger on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/261

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

At the moment, there's only a default filament cost setting:

However, BamBuddy tracks the different materials being used already in the statistics dashboard:

Due to different pricing of materials and vendors, it would be beneficial to have separate cost settings per filament type (i.e. PLA = 22,99, ABS-GF = 32,99, etc) to track the cost of individual prints separately and to have an accurate overall cost tracking.
An average price setting is not accurate enough and may not represent the individual and overall cost of filament depending on the amount of material used.

Proposed Solution

It would be great to have an individual price / cost setting per filament type, i.e. in the Filament Tab of the settings section which is used to calculate the cost of individual prints (accumulated with electricity cost via Smart Plug if present) and overall filament consumption.

Alternatives Considered

No response

Feature Category

Monitoring & Stats

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 @Roycinger on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/261 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case At the moment, there's only a default filament cost setting: <img width="452" height="438" alt="Image" src="https://github.com/user-attachments/assets/6898b312-20a7-4f41-8846-8b59611886ad" /> However, BamBuddy tracks the different materials being used already in the statistics dashboard: <img width="396" height="294" alt="Image" src="https://github.com/user-attachments/assets/f87d0869-dde4-4c6a-8a1d-a59293ac8686" /> Due to different pricing of materials and vendors, it would be beneficial to have separate cost settings per filament type (i.e. PLA = 22,99, ABS-GF = 32,99, etc) to track the cost of individual prints separately and to have an accurate overall cost tracking. An average price setting is not accurate enough and may not represent the individual and overall cost of filament depending on the amount of material used. ### Proposed Solution It would be great to have an individual price / cost setting per filament type, i.e. in the Filament Tab of the settings section which is used to calculate the cost of individual prints (accumulated with electricity cost via Smart Plug if present) and overall filament consumption. ### Alternatives Considered _No response_ ### Feature Category Monitoring & Stats ### 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:06:59 +02:00

closed this issue
added the
wontfix
label

BreizhHardware commented

2026-05-07 00:06:59 +02:00

Author

Owner

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

Why don't you use Spoolman?

@maziggy commented on GitHub (Feb 10, 2026): Why don't you use Spoolman?

BreizhHardware commented

2026-05-07 00:06:59 +02:00

Author

Owner

@joaorgoncalves commented on GitHub (Feb 10, 2026):

Is the Spoolman integration working without the AMS? If not, this could be a great workaround while the Spoolman integration only works with AMS.

@joaorgoncalves commented on GitHub (Feb 10, 2026): Is the Spoolman integration working without the AMS? If not, this could be a great workaround while the Spoolman integration only works with AMS.

BreizhHardware commented

2026-05-07 00:06:59 +02:00

Author

Owner

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

Ehm....without an AMS? How are you going to calculate the used filament if you have no AMS?

Now I don't understand your feature request at all.

@maziggy commented on GitHub (Feb 10, 2026): Ehm....without an AMS? How are you going to calculate the used filament if you have no AMS? Now I don't understand your feature request at all.

BreizhHardware commented

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

Author

Owner

@Roycinger commented on GitHub (Feb 10, 2026):

Why don't you use Spoolman?

Because Spoolman does not work properly (sync issues all around) and not everyone is willing to use an extra tool to dig into (and does not provide a simple solution overall).

@Roycinger commented on GitHub (Feb 10, 2026): > Why don't you use Spoolman? Because Spoolman does not work properly (sync issues all around) and not everyone is willing to use an extra tool to dig into (and does not provide a simple solution overall).

BreizhHardware commented

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

Author

Owner

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

I understand the desire for more accurate cost tracking, but I think Spoolman is the right solution here — it already provides per-spool pricing, and Bambuddy integrates with it for exactly this purpose.

Building a separate per-material cost table inside Bambuddy would essentially be a less capable version of what Spoolman already does (per-spool vs per-material-type, vendor-specific pricing, etc.).

If you're running into Spoolman sync issues, I'd be happy to look into those.

Going to close this one for now, but feel free to reopen if I'm missing something about your use case.

@maziggy commented on GitHub (Feb 11, 2026): I understand the desire for more accurate cost tracking, but I think Spoolman is the right solution here — it already provides per-spool pricing, and Bambuddy integrates with it for exactly this purpose. Building a separate per-material cost table inside Bambuddy would essentially be a less capable version of what Spoolman already does (per-spool vs per-material-type, vendor-specific pricing, etc.). If you're running into Spoolman sync issues, I'd be happy to look into those. Going to close this one for now, but feel free to reopen if I'm missing something about your use case.

BreizhHardware commented

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

Author

Owner

@Roycinger commented on GitHub (Feb 11, 2026):

I understand your point of view but in general, BamBuddy should not rely on optional and external tools to do a calculation that's already being done, but only with an generic average value (Default filament cost).

@Roycinger commented on GitHub (Feb 11, 2026): I understand your point of view but in general, BamBuddy should not rely on optional and external tools to do a calculation that's already being done, but only with an generic average value (Default filament cost).

BreizhHardware commented

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

Author

Owner

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

Wait a little bit. We are already working on something.

@maziggy commented on GitHub (Feb 11, 2026): Wait a little bit. We are already working on something.

BreizhHardware referenced this issue

2026-05-07 00:15:12 +02:00

[PR #201] [MERGED] Add group-based permissions system with granular access control #961