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 #817] [Bug]: Filament stock does not take in consideration multiple equal rolls #549

New issue

Closed

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

BreizhHardware commented

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

Owner

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

Originally assigned to: @Keybored02 on GitHub.

Bug Description

Under Filament if we add a second roll equal to one that is ending it does not consider this and keeps saying low stock.

Expected Behavior

It should know there is more of that role in stock and not say its low stock.

Steps to Reproduce

1 - Go to filaments
2 - Add a new but equal to a filament that is running out

Printer Model

P1S

Bambuddy Version

v0.2.2.1

Printer Firmware Version

01.08

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

No response

Screenshots

No response

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @odin6796 on GitHub (Mar 25, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/817 Originally assigned to: @Keybored02 on GitHub. ### Bug Description Under Filament if we add a second roll equal to one that is ending it does not consider this and keeps saying low stock. ### Expected Behavior It should know there is more of that role in stock and not say its low stock. ### Steps to Reproduce 1 - Go to filaments 2 - Add a new but equal to a filament that is running out ### Printer Model P1S ### Bambuddy Version v0.2.2.1 ### Printer Firmware Version 01.08 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package _No response_ ### Screenshots _No response_ ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

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

closed this issue
added the
wontfix
label

BreizhHardware commented

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

Author

Owner

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

Low Stock is simply a filter to show all spools under a certain fill level. If I'm understanding correctly, you'd prefer a inventory stock take, where if you have less than x amount of spools left for a given material, it shows it as low stock? So more a point of reorder approach?

Unlike Spoolman, Bambuddy Internal inventory treats all spools as individual entities. So instead of having the user create first a filament that is then used as template to add spools to inventory, each item is unique and not related to others of the same manufacturer/ material/ type/ color.

Implementing your request would mean quite a bit of rework, but I do admit that I like the Spoolman approach.

@Keybored02 commented on GitHub (Mar 25, 2026): Low Stock is simply a filter to show all spools under a certain fill level. If I'm understanding correctly, you'd prefer a inventory stock take, where if you have less than x amount of spools left for a given material, it shows it as low stock? So more a point of reorder approach? Unlike Spoolman, Bambuddy Internal inventory treats all spools as individual entities. So instead of having the user create first a filament that is then used as template to add spools to inventory, each item is unique and not related to others of the same manufacturer/ material/ type/ color. Implementing your request would mean quite a bit of rework, but I do admit that I like the Spoolman approach.

BreizhHardware commented

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

Author

Owner

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

Oh I see, well ok then! Thank you

@odin6796 commented on GitHub (Mar 25, 2026): Oh I see, well ok then! Thank you

BreizhHardware referenced this issue

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

[PR #555] [MERGED] v0.2.1.1 #1069

BreizhHardware referenced this issue

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