starred/bambuddy

Fork 0

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

[GH-ISSUE #525] [Bug]: Internal Filament Management - Manually entering spool weight not possible #336

New issue

Closed

opened 2026-05-06 12:28:23 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-06 12:28:23 +02:00

Owner

Originally created by @peter-k-de on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/525

Originally assigned to: @maziggy on GitHub.

Bug Description

When manually changing the measured spool weight or the remaining weight via the spool details dialog, the entered value is immediately overwritten after clicking Save. It appears to revert to the last AMS-reported estimated spool weight.
When updating the remaining spool weight via the API (PATCH api/v1/inventory/spools/{ID}), the value is initially stored and displayed correctly. However, once the spool is inserted into the AMS, the manually set value is overwritten again by the AMS estimate.

As a result, there seems to be no reliable way to enter and persist an exact spool weight in Bambuddy (e.g., after using the spool in another printer and weighing it manually).

Expected Behavior

It should be possible to manually enter and persist a spool weight (gross or remaining) without it being automatically overwritten by AMS estimates.

Steps to Reproduce

Option 1 (UI):
1. Open the spool details dialog in Bambuddy.
2. Manually enter a new spool weight (remaining or gross).
3. Click Save.
4. The entered value is immediately replaced by a different value (likely the last AMS estimate).

Option 2 (API):
1. Send a PATCH request to api/v1/inventory/spools/{ID} with a new remaining weight.
2. The weight is displayed correctly at first.
3. Insert the spool into the AMS.
4. The manually set weight is overwritten by the AMS estimate.

Printer Model

H2D

Bambuddy Version

v0.2.2b1

Printer Firmware Version

01.02.10.00

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

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 @peter-k-de on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/525 Originally assigned to: @maziggy on GitHub. ### Bug Description 1. When manually changing the measured spool weight or the remaining weight via the spool details dialog, the entered value is immediately overwritten after clicking Save. It appears to revert to the last AMS-reported estimated spool weight. 2. When updating the remaining spool weight via the API (PATCH api/v1/inventory/spools/{ID}), the value is initially stored and displayed correctly. However, once the spool is inserted into the AMS, the manually set value is overwritten again by the AMS estimate. As a result, there seems to be no reliable way to enter and persist an exact spool weight in Bambuddy (e.g., after using the spool in another printer and weighing it manually). ### Expected Behavior It should be possible to manually enter and persist a spool weight (gross or remaining) without it being automatically overwritten by AMS estimates. ### Steps to Reproduce Option 1 (UI): 1. Open the spool details dialog in Bambuddy. 2. Manually enter a new spool weight (remaining or gross). 3. Click Save. 4. The entered value is immediately replaced by a different value (likely the last AMS estimate). Option 2 (API): 1. Send a PATCH request to api/v1/inventory/spools/{ID} with a new remaining weight. 2. The weight is displayed correctly at first. 3. Insert the spool into the AMS. 4. The manually set weight is overwritten by the AMS estimate. ### Printer Model H2D ### Bambuddy Version v0.2.2b1 ### Printer Firmware Version 01.02.10.00 ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### 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-06 12:28:23 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:28:23 +02:00

Author

Owner

@peter-k-de commented on GitHub (Feb 25, 2026):

Correction: In the spool details dialog, the manually entered weight is displayed correctly after reopening the dialog, at least sometimes. However, in all other parts of the UI, the previous (AMS-reported) value is still used.

@peter-k-de commented on GitHub (Feb 25, 2026): Correction: In the spool details dialog, the manually entered weight is displayed correctly after reopening the dialog, at least sometimes. However, in all other parts of the UI, the previous (AMS-reported) value is still used.

BreizhHardware commented

2026-05-06 12:28:23 +02:00

Author

Owner

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

Fixed in branch 0.2.1. Please let me know if it works for you now.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Feb 26, 2026): Fixed in branch 0.2.1. Please let me know if it works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!

BreizhHardware commented

2026-05-06 12:28:24 +02:00

Author

Owner

@peter-k-de commented on GitHub (Feb 26, 2026):

Thank you so much, switched to 0.2.1. and just tested it with a couple of spools - now it works reliably. Fantastic work!

@peter-k-de commented on GitHub (Feb 26, 2026): Thank you so much, switched to 0.2.1. and just tested it with a couple of spools - now it works reliably. Fantastic work!

BreizhHardware referenced this issue

2026-05-06 12:34:37 +02:00

[PR #411] [MERGED] v0.2.0 #1034