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 #496] [Bug]: Filament weight reported correctly in printer card, but incorrectly in filament menu #314

New issue

Closed

opened 2026-05-07 00:08:48 +02:00 by BreizhHardware · 10 comments

BreizhHardware commented

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

Owner

Originally created by @hollycroftlabs on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/496

Originally assigned to: @maziggy on GitHub.

Bug Description

Some filaments are reported incorrectly in the filament menu despite being reported correctly in the AMS section of the printer card.

Expected Behavior

Printer weights reported correctly between both menus

Steps to Reproduce

Check difference between filament menu and printer card

Printer Model

P1S

Bambuddy Version

0.2.1b2

Printer Firmware Version

01.09.01.00

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

Screenshots

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

Originally created by @hollycroftlabs on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/496 Originally assigned to: @maziggy on GitHub. ### Bug Description Some filaments are reported incorrectly in the filament menu despite being reported correctly in the AMS section of the printer card. ### Expected Behavior Printer weights reported correctly between both menus ### Steps to Reproduce 1. Check difference between filament menu and printer card ### Printer Model P1S ### Bambuddy Version 0.2.1b2 ### Printer Firmware Version 01.09.01.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots <img width="1153" height="95" alt="Image" src="https://github.com/user-attachments/assets/51bb6eec-f592-4057-9b2c-087219677506" /> <img width="217" height="257" alt="Image" src="https://github.com/user-attachments/assets/b02a77f6-6b23-4eee-aa10-998806d291cb" /> ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [ ] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode

BreizhHardware

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

closed this issue
added the
bug
label

BreizhHardware commented

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

Author

Owner

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

Please try branch 0.2.1b3. It the problem is still there, I need a support package please.

@maziggy commented on GitHub (Feb 23, 2026): Please try branch 0.2.1b3. It the problem is still there, I need a support package please.

BreizhHardware commented

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

Author

Owner

@Keybored02 commented on GitHub (Feb 23, 2026):

bambuddy-support-20260223-104841.zip

Same issue on the latest 0.2.1b3.

In my case it affects only the Bambu spools that where created automatically in Spoolman and then re-inserted manually into the internal database when I switched to it. It does report the fill level based on what Spoolman reports. Setting inventoryFill to Internal fixes the issue (obviously). Fill is working for spools that are not Bambu, or Bambu spools created directly in the new database.

@Keybored02 commented on GitHub (Feb 23, 2026): [bambuddy-support-20260223-104841.zip](https://github.com/user-attachments/files/25481753/bambuddy-support-20260223-104841.zip) Same issue on the latest 0.2.1b3. In my case it affects only the Bambu spools that where created automatically in Spoolman and then re-inserted manually into the internal database when I switched to it. It does report the fill level based on what Spoolman reports. Setting `inventoryFill` to Internal fixes the issue (obviously). Fill is working for spools that are not Bambu, or Bambu spools created directly in the new database.

BreizhHardware commented

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

Author

Owner

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

Not sure if I got it. Can you please explain a little bit more detailed?

How were these spools created in the internal database? You mentioned they were "created automatically in Spoolman and then re-inserted manually." Did you:
- Manually create new spools via the Inventory form?
- Or was there some other method (e.g. auto-created when disabling Spoolman)?
What does "Setting inventoryFill to Internal" mean exactly? Did you change a specific setting in Bambuddy, or do you mean you disabled Spoolman entirely?
Was Spoolman still enabled/connected when you noticed the wrong fill levels? Or had you already fully switched to internal inventory?
For the affected spools — were they ever used in prints while assigned in the internal inventory? Trying to understand if the usage tracker (3MF-based) could have accumulated incorrect weight_used values, or if the spools started with wrong values from the beginning.

@hollycroftlabs same questions for your setup — are you using Spoolman, internal inventory, or both?

@maziggy commented on GitHub (Feb 23, 2026): Not sure if I got it. Can you please explain a little bit more detailed? 1. How were these spools created in the internal database? You mentioned they were "created automatically in Spoolman and then re-inserted manually." Did you: - Manually create new spools via the Inventory form? - Or was there some other method (e.g. auto-created when disabling Spoolman)? 2. What does "Setting inventoryFill to Internal" mean exactly? Did you change a specific setting in Bambuddy, or do you mean you disabled Spoolman entirely? 3. Was Spoolman still enabled/connected when you noticed the wrong fill levels? Or had you already fully switched to internal inventory? 4. For the affected spools — were they ever used in prints while assigned in the internal inventory? Trying to understand if the usage tracker (3MF-based) could have accumulated incorrect weight_used values, or if the spools started with wrong values from the beginning. @hollycroftlabs same questions for your setup — are you using Spoolman, internal inventory, or both?

BreizhHardware commented

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

Author

Owner

@Keybored02 commented on GitHub (Feb 23, 2026):

The spools where manually created after I switched to the Internal Inventory tracking.
I set inventoryFill in PrintersPage to ignore all other sources and track only from Inventory. This fixed the fill percentage
Spoolman was not connected. I had already switched to Internal for a while when I noticed this.
Yes, they have been used. The usage itself is tracked, weight is deducted correctly and the fill level goes down when a print finishes but a 664g spool has a 77% fill level.

@Keybored02 commented on GitHub (Feb 23, 2026): 1. The spools where manually created after I switched to the Internal Inventory tracking. 2. I set `inventoryFill` in `PrintersPage` to ignore all other sources and track only from Inventory. This fixed the fill percentage 3. Spoolman was not connected. I had already switched to Internal for a while when I noticed this. 4. Yes, they have been used. The usage itself is tracked, weight is deducted correctly and the fill level goes down when a print finishes but a 664g spool has a 77% fill level.

BreizhHardware commented

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

Author

Owner

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

What does "I set inventoryFill in PrintersPage" mean?

@maziggy commented on GitHub (Feb 23, 2026): What does "I set inventoryFill in PrintersPage" mean?

BreizhHardware commented

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

Author

Owner

@Keybored02 commented on GitHub (Feb 23, 2026):

Edit to the source code in PrintersPage.tsx. Mentioned the wrong variable, sorry, meant fillSource = 'inventory'.

                                const inventoryAssignment = onGetAssignment?.(printer.id, ams.id, slotIdx);
                                const inventoryFill = (() => {
                                  const sp = inventoryAssignment?.spool;
                                  if (sp && sp.label_weight > 0 && sp.weight_used != null) {
                                    return Math.round(Math.max(0, sp.label_weight - sp.weight_used) / sp.label_weight * 100);
                                  }
                                  return null;
                                })();
                                const effectiveFill = inventoryFill;
                                const fillSource = 'inventory' as const;

@Keybored02 commented on GitHub (Feb 23, 2026): Edit to the source code in `PrintersPage.tsx`. Mentioned the wrong variable, sorry, meant `fillSource = 'inventory'`. ``` const inventoryAssignment = onGetAssignment?.(printer.id, ams.id, slotIdx); const inventoryFill = (() => { const sp = inventoryAssignment?.spool; if (sp && sp.label_weight > 0 && sp.weight_used != null) { return Math.round(Math.max(0, sp.label_weight - sp.weight_used) / sp.label_weight * 100); } return null; })(); const effectiveFill = inventoryFill; const fillSource = 'inventory' as const; ```

BreizhHardware commented

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

Author

Owner

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

Got it. Will look into it later.

@maziggy commented on GitHub (Feb 23, 2026): Got it. Will look into it later.

BreizhHardware commented

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

Author

Owner

@hollycroftlabs commented on GitHub (Feb 23, 2026):

I'm using internal inventory now, but was using spoolman.

I'm not sure this issue is just related to spoolman, i just inserted a brand new full spool into my ams and got the same issue. Printer card shows full, filament menu shows empty

@hollycroftlabs commented on GitHub (Feb 23, 2026): I'm using internal inventory now, but was using spoolman. I'm not sure this issue is just related to spoolman, i just inserted a brand new full spool into my ams and got the same issue. Printer card shows full, filament menu shows empty

BreizhHardware commented

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

Author

Owner

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

Hopefully fixed in branch 0.2.1b3. Please let me know.

@maziggy commented on GitHub (Feb 23, 2026): Hopefully fixed in branch 0.2.1b3. Please let me know.

BreizhHardware commented

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

Author

Owner

@Keybored02 commented on GitHub (Feb 23, 2026):