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
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#450
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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
@shrunbr commented on GitHub (Mar 12, 2026):
This can get assigned to me, I am investigating cause and will fix.
@shrunbr commented on GitHub (Mar 13, 2026):
This has been resolved in #686 and it has been merged. Closing issue.