1
0
Fork 0
mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #677] [Bug]: Filament usage data not being sent to Spoolman #450

Closed
opened 2026-05-07 00:10:19 +02:00 by BreizhHardware · 2 comments

Originally created by @shrunbr on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/677

Originally assigned to: @shrunbr on GitHub.

Bug Description

Upon aborted, failed or successful print, filament usage data should be getting reported back to Spoolman. However, as of version 0.2.2b3 log messages such as the ones below are seen.

[backend.app.services.spoolman_tracking] [SPOOLMAN] No tracking data for print (printer=1, archive=10)
[backend.app.main] [SPOOLMAN] Failed to store tracking data: '>=' not supported between instances of 'str' and 'int'

Expected Behavior

Filament usage data should be properly reported to Spoolman upon aborted, failed or successful print.

Steps to Reproduce

  1. Ensure Bambuddy is properly connected to Spoolman
  2. Start a print
  3. Wait for it to finish
  4. Check filament data in Spoolman
  5. See data is unchanged
  6. Check Bambuddy logs
  7. See that it was not reported back to Spoolman

Printer Model

P2S

Bambuddy Version

0.2.2b3

Printer Firmware Version

01.01.03.00

Installation Method

Docker

Operating System

Docker

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 @shrunbr on GitHub (Mar 12, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/677 Originally assigned to: @shrunbr on GitHub. ### Bug Description Upon aborted, failed or successful print, filament usage data should be getting reported back to Spoolman. However, as of version 0.2.2b3 log messages such as the ones below are seen. `[backend.app.services.spoolman_tracking] [SPOOLMAN] No tracking data for print (printer=1, archive=10)` `[backend.app.main] [SPOOLMAN] Failed to store tracking data: '>=' not supported between instances of 'str' and 'int'` ### Expected Behavior Filament usage data should be properly reported to Spoolman upon aborted, failed or successful print. ### Steps to Reproduce 1. Ensure Bambuddy is properly connected to Spoolman 2. Start a print 3. Wait for it to finish 4. Check filament data in Spoolman 5. See data is unchanged 6. Check Bambuddy logs 7. See that it was not reported back to Spoolman ### Printer Model P2S ### Bambuddy Version 0.2.2b3 ### Printer Firmware Version 01.01.03.00 ### Installation Method Docker ### Operating System Docker ### 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-07 00:10:19 +02:00
Author
Owner

@shrunbr commented on GitHub (Mar 12, 2026):

This can get assigned to me, I am investigating cause and will fix.

<!-- gh-comment-id:4046623480 --> @shrunbr commented on GitHub (Mar 12, 2026): This can get assigned to me, I am investigating cause and will fix.
Author
Owner

@shrunbr commented on GitHub (Mar 13, 2026):

This has been resolved in #686 and it has been merged. Closing issue.

<!-- gh-comment-id:4055825203 --> @shrunbr commented on GitHub (Mar 13, 2026): This has been resolved in #686 and it has been merged. Closing issue.
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-maziggy-1#450
No description provided.