starred/bambuddy

Fork 0

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

[GH-ISSUE #639] [Bug]: Spoolman Not showing link spool with spoolman configured #417

New issue

Closed

opened 2026-05-06 12:29:16 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-06 12:29:16 +02:00

Owner

Originally created by @errolsancaktar on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/639

Originally assigned to: @maziggy on GitHub.

Bug Description

Have everything set up and can see the comms between bambuddy and spoolman. spoolman has spools available

Expected Behavior

Should let me link spools

Steps to Reproduce

set up per docs

Printer Model

Bambuddy Version

v0.2.1.1

Printer Firmware Version

1.07.02.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
My printer has Developer Mode enabled

Originally created by @errolsancaktar on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/639 Originally assigned to: @maziggy on GitHub. ### Bug Description Have everything set up and can see the comms between bambuddy and spoolman. spoolman has spools available ### Expected Behavior Should let me link spools ### Steps to Reproduce set up per docs ### Printer Model A1 ### Bambuddy Version v0.2.1.1 ### Printer Firmware Version 1.07.02.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots <img width="825" height="747" alt="Image" src="https://github.com/user-attachments/assets/ebf3f06e-fc91-4c69-b844-c91aea81e38b" /> <img width="1417" height="321" alt="Image" src="https://github.com/user-attachments/assets/10c42813-00fd-4ea0-9a03-de807a93d5c6" /> <img width="460" height="1008" alt="Image" src="https://github.com/user-attachments/assets/218bea57-aba8-45ba-9a17-82a0b266eb90" /> ### 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:29:16 +02:00

closed this issue
added the
invalid
label

BreizhHardware commented

2026-05-06 12:29:17 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 7, 2026):

What spools are you talking about? Need some more details.

@maziggy commented on GitHub (Mar 7, 2026): What spools are you talking about? Need some more details.

BreizhHardware commented

2026-05-06 12:29:17 +02:00

Author

Owner

@errolsancaktar commented on GitHub (Mar 7, 2026):

maybe i'm misunderstanding the process but heres my scenario:

i dont use bambu or any rfid spools right now
i store my spools in spoolman
id like to be able to load a spool into my a1 and have it record usage against it in spoolman

based on what i'm seein in the code however, it seems that spool tracking in bambuddy bases the spool on the tag_uuid of the loaded filament.

Some tests i've run through:

the interaction between bambuddy and spoolman seems fine, i can pull filaments, spools, etc through the api of bambuddy
everything is conifugred and bambuddy accepts that spoolman is there
if i set a dummy 32 bit hex val in tag i can force "link" the spool to a tray in bb but i still dont see any spoolman specific stuff
tried running current beta with no change
does this have to do with the A1 loading null for the tray_uuuid or is that how all bambus work?

@errolsancaktar commented on GitHub (Mar 7, 2026): maybe i'm misunderstanding the process but heres my scenario: - i dont use bambu or any rfid spools right now - i store my spools in spoolman - id like to be able to load a spool into my a1 and have it record usage against it in spoolman based on what i'm seein in the code however, it seems that spool tracking in bambuddy bases the spool on the tag_uuid of the loaded filament. Some tests i've run through: - the interaction between bambuddy and spoolman seems fine, i can pull filaments, spools, etc through the api of bambuddy - everything is conifugred and bambuddy accepts that spoolman is there - if i set a dummy 32 bit hex val in tag i can force "link" the spool to a tray in bb but i still dont see any spoolman specific stuff - tried running current beta with no change - does this have to do with the A1 loading null for the tray_uuuid or is that how all bambus work?

BreizhHardware commented

2026-05-06 12:29:17 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 7, 2026):

As per documentation, this is only available for the internal inventory.

There's already a PR to add this also for Spoolman, but I didn't check it so far.

@maziggy commented on GitHub (Mar 7, 2026): As per documentation, this is only available for the internal inventory. There's already a PR to add this also for Spoolman, but I didn't check it so far.