[GH-ISSUE #323] [Bug]: Spoolman remaining weight does not get updated after print #205

Closed
opened 2026-05-06 12:27:14 +02:00 by BreizhHardware · 10 comments

Originally created by @chrisonline on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/323

Originally assigned to: @maziggy on GitHub.

Bug Description

After print the remaining weight in Spoolman does not get updated.

Expected Behavior

Before print the red filament was 110,2 g remaining weight.
After print the remaining weight should be updated in Spoolman, but is still 110,2 g.

The print job shows 1 g.

Steps to Reproduce

  1. Connect Spool with Spoolman
  2. Print a job
  3. After Print check Spoolman remaining weight

Printer Model

A1

Bambuddy Version

0.1.9b

Printer Firmware Version

01.07.02.00

Installation Method

Docker

Operating System

Linux (Other)

Relevant Logs / Support Package

bambuddy-support-20260210-154808.zip

Screenshots

Image

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 @chrisonline on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/323 Originally assigned to: @maziggy on GitHub. ### Bug Description After print the remaining weight in Spoolman does not get updated. ### Expected Behavior Before print the red filament was 110,2 g remaining weight. After print the remaining weight should be updated in Spoolman, but is still 110,2 g. The print job shows 1 g. ### Steps to Reproduce 1. Connect Spool with Spoolman 2. Print a job 3. After Print check Spoolman remaining weight ### Printer Model A1 ### Bambuddy Version 0.1.9b ### Printer Firmware Version 01.07.02.00 ### Installation Method Docker ### Operating System Linux (Other) ### Relevant Logs / Support Package [bambuddy-support-20260210-154808.zip](https://github.com/user-attachments/files/25213596/bambuddy-support-20260210-154808.zip) ### Screenshots <img width="317" height="394" alt="Image" src="https://github.com/user-attachments/assets/ec0ebf6d-3fbe-41f9-a5d0-96f42799fcd6" /> ### 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
BreizhHardware 2026-05-06 12:27:14 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

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

I looked at the support package, but debug logging was only enabled right before generating it, so the logs don't contain any print lifecycle events (print start/completion). Without those, I can't tell where the weight update is failing.

  1. Enable debug logging in Settings
  2. Run a print from start to finish
  3. After the print completes, generate a new support package and attach it here

I'll need to see the [SPOOLMAN] log entries during the print to diagnose what's going wrong.

<!-- gh-comment-id:3882719659 --> @maziggy commented on GitHub (Feb 11, 2026): I looked at the support package, but debug logging was only enabled right before generating it, so the logs don't contain any print lifecycle events (print start/completion). Without those, I can't tell where the weight update is failing. 1. Enable debug logging in Settings 2. Run a print from start to finish 3. After the print completes, generate a new support package and attach it here I'll need to see the [SPOOLMAN] log entries during the print to diagnose what's going wrong.
Author
Owner

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

Strange because I have enabled it before the print.
Anyway I will do it again today and send you a new debug log.

<!-- gh-comment-id:3883033742 --> @chrisonline commented on GitHub (Feb 11, 2026): Strange because I have enabled it before the print. Anyway I will do it again today and send you a new debug log.
Author
Owner

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

@maziggy Now I have printed again with debug log on.
Here is the support zip file.

bambuddy-support-20260211-193942.zip

And here the screenshot of the log time:

Image

The filament was before 111,2 g and after print it hasn't changed.

<!-- gh-comment-id:3886245007 --> @chrisonline commented on GitHub (Feb 11, 2026): @maziggy Now I have printed again with debug log on. Here is the support zip file. [bambuddy-support-20260211-193942.zip](https://github.com/user-attachments/files/25242160/bambuddy-support-20260211-193942.zip) And here the screenshot of the log time: <img width="669" height="452" alt="Image" src="https://github.com/user-attachments/assets/e0ab66e2-2ef6-4eb0-9a85-3ad3ad669f5e" /> The filament was before 111,2 g and after print it hasn't changed.
Author
Owner

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

Please wait a few days. I'm currently completely refactoring the filament management.

<!-- gh-comment-id:3888933270 --> @maziggy commented on GitHub (Feb 12, 2026): Please wait a few days. I'm currently completely refactoring the filament management.
Author
Owner

@chrisonline commented on GitHub (Feb 12, 2026):

Yes no stress. Thanks for the info.

<!-- gh-comment-id:3889632221 --> @chrisonline commented on GitHub (Feb 12, 2026): Yes no stress. Thanks for the info.
Author
Owner

@redvers76 commented on GitHub (Feb 14, 2026):

I have a related issue, in that Spoolman was updated to set Used to 1KG and remaining to 0g, right at the start of the print. I'd setup Spoolman without the tag entries, so Bambuddy created new spool profiles. I then deleted those profiles and updated the existing ones with the RFID tags. This refreshed in Bambuddy and showed the %age remaining correctly on the AMS. But when it started printing and updated the location in Spoolman, the remaining went to 0g :(

<!-- gh-comment-id:3901673245 --> @redvers76 commented on GitHub (Feb 14, 2026): I have a related issue, in that Spoolman was updated to set Used to 1KG and remaining to 0g, right at the start of the print. I'd setup Spoolman without the tag entries, so Bambuddy created new spool profiles. I then deleted those profiles and updated the existing ones with the RFID tags. This refreshed in Bambuddy and showed the %age remaining correctly on the AMS. But when it started printing and updated the location in Spoolman, the remaining went to 0g :(
Author
Owner

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

PLease see my last comment.

<!-- gh-comment-id:3901675898 --> @maziggy commented on GitHub (Feb 14, 2026): PLease see my last comment.
Author
Owner

@redvers76 commented on GitHub (Feb 14, 2026):

PLease see my last comment.

Yes, that's why I added my comment here, as it might be part of the refactoring... Once that is done I am happy to retest with full logging in both Bambuddy & Spoolman!

<!-- gh-comment-id:3901678449 --> @redvers76 commented on GitHub (Feb 14, 2026): > PLease see my last comment. Yes, that's why I added my comment here, as it might be part of the refactoring... Once that is done I am happy to retest with full logging in both Bambuddy & Spoolman!
Author
Owner

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

It's already finished and in testing phase.

<!-- gh-comment-id:3901687121 --> @maziggy commented on GitHub (Feb 14, 2026): It's already finished and in testing phase.
Author
Owner

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

Available in next 0.2.0 release.

<!-- gh-comment-id:3904436356 --> @maziggy commented on GitHub (Feb 15, 2026): Available in next 0.2.0 release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#205
No description provided.