starred/bambuddy

Fork 0

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

[GH-ISSUE #714] [Bug]: Manual "Link to Spoolman" rewrites RFID tag to short legacy value, breaking existing AMS/Spoolman matching #475

New issue

Closed

opened 2026-05-06 12:29:59 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

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

Owner

Originally created by @h-markus on GitHub (Mar 15, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/714

Originally assigned to: @shrunbr on GitHub.

Bug Description

What happened?

I am using Bambuddy with Spoolman and only genuine Bambu Lab RFID spools.

Auto-sync appears to identify AMS spools using a long RFID tag (32 hex chars), for example:

detected by auto-sync: F6CE8D9015614E658E6D69303DE38A22

When I manually click "Link to Spoolman" for that spool and select an existing Spoolman spool, Bambuddy appears to overwrite the tag in Spoolman with a different short tag instead, for example:

after manual link: 0AE9D2FE00000100

After that:

the Printers tab shows "Link to Spoolman" again instead of "Open in Spoolman"
spool fill level is missing in the Printers tab
auto-sync may no longer match the spool correctly unless I manually restore the long RFID tag in Spoolman

So it looks like:

auto-sync / AMS detection uses the long RFID tag
manual "Link to Spoolman" writes a different short/legacy tag
those two code paths do not agree on the spool identifier

Expected Behavior

Manual linking should preserve/use the same spool identifier that AMS auto-sync uses.

If the spool is already matched by its RFID tag, linking it manually should not replace the tag with a different value.

After linking, the UI should consistently show:

"Open in Spoolman" instead of "Link to Spoolman"
correct spool fill level in the Printers tab

Actual behavior

Manual linking changes the Spoolman tag from the long RFID tag to a short different value, which seems to break Bambuddy's linked-state/UI and causes inconsistent behavior between matching and linking.

Steps to Reproduce

Use a genuine Bambu Lab RFID spool in AMS
Let Bambuddy auto-sync to Spoolman
Observe that Bambuddy detects/creates/updates the spool using a long RFID tag, e.g.:
- F6CE8D9015614E658E6D69303DE38A22
In Spoolman, ensure that spool has this long tag
In Bambuddy, click "Link to Spoolman" on that spool and select the correct existing Spoolman spool
Check the tag in Spoolman again
Observe that the tag was changed to a different short value, e.g.:
- 0AE9D2FE00000100
Go back to the Printers tab
Observe that Bambuddy now shows "Link to Spoolman" again instead of "Open in Spoolman", and fill level may be missing

Printer Model

X1 Carbon

Bambuddy Version

v0.2.2b3

Printer Firmware Version

01.11.02.00

Installation Method

Docker

Operating System

Docker

Relevant Logs / Support Package

Logs

Relevant behavior from logs:

auto-sync creates/updates using long tags, e.g.:
- Creating new spool in Spoolman for PLA Wood (tag: F6CE8D9015614E65...)
- later:
- Updating existing spool 24 for tag F6CE8D9015614E65...

This suggests AMS matching is using the long RFID tag correctly.

Environment

Bambuddy version: v0.2.2b3
Deployment: Docker / Portainer on Synology
Printer: Bambu Lab X1C
Spool type: only genuine Bambu Lab RFID spools
Spoolman enabled

Additional notes

This may be related to the linked/unlinked UI state from #210, but this issue seems deeper:
the actual identifier written during manual linking appears to differ from the identifier used by AMS auto-sync.

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 @h-markus on GitHub (Mar 15, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/714 Originally assigned to: @shrunbr on GitHub. ### Bug Description ### What happened? I am using Bambuddy with Spoolman and only genuine Bambu Lab RFID spools. Auto-sync appears to identify AMS spools using a **long RFID tag** (32 hex chars), for example: - detected by auto-sync: `F6CE8D9015614E658E6D69303DE38A22` When I manually click **"Link to Spoolman"** for that spool and select an existing Spoolman spool, Bambuddy appears to overwrite the tag in Spoolman with a **different short tag** instead, for example: - after manual link: `0AE9D2FE00000100` After that: - the Printers tab shows **"Link to Spoolman"** again instead of **"Open in Spoolman"** - spool fill level is missing in the Printers tab - auto-sync may no longer match the spool correctly unless I manually restore the long RFID tag in Spoolman So it looks like: - **auto-sync / AMS detection** uses the long RFID tag - **manual "Link to Spoolman"** writes a different short/legacy tag - those two code paths do not agree on the spool identifier ### Expected Behavior Manual linking should preserve/use the same spool identifier that AMS auto-sync uses. If the spool is already matched by its RFID tag, linking it manually should not replace the tag with a different value. After linking, the UI should consistently show: - **"Open in Spoolman"** instead of **"Link to Spoolman"** - correct spool fill level in the Printers tab ### Actual behavior Manual linking changes the Spoolman tag from the long RFID tag to a short different value, which seems to break Bambuddy's linked-state/UI and causes inconsistent behavior between matching and linking. ### Steps to Reproduce 1. Use a genuine Bambu Lab RFID spool in AMS 2. Let Bambuddy auto-sync to Spoolman 3. Observe that Bambuddy detects/creates/updates the spool using a long RFID tag, e.g.: - `F6CE8D9015614E658E6D69303DE38A22` 4. In Spoolman, ensure that spool has this long tag 5. In Bambuddy, click **"Link to Spoolman"** on that spool and select the correct existing Spoolman spool 6. Check the tag in Spoolman again 7. Observe that the tag was changed to a different short value, e.g.: - `0AE9D2FE00000100` 8. Go back to the Printers tab 9. Observe that Bambuddy now shows **"Link to Spoolman"** again instead of **"Open in Spoolman"**, and fill level may be missing ### Printer Model X1 Carbon ### Bambuddy Version v0.2.2b3 ### Printer Firmware Version 01.11.02.00 ### Installation Method Docker ### Operating System Docker ### Relevant Logs / Support Package ### Logs Relevant behavior from logs: - auto-sync creates/updates using long tags, e.g.: - `Creating new spool in Spoolman for PLA Wood (tag: F6CE8D9015614E65...)` - later: - `Updating existing spool 24 for tag F6CE8D9015614E65...` This suggests AMS matching is using the long RFID tag correctly. ### Environment - Bambuddy version: v0.2.2b3 - Deployment: Docker / Portainer on Synology - Printer: Bambu Lab X1C - Spool type: only genuine Bambu Lab RFID spools - Spoolman enabled ### Additional notes This may be related to the linked/unlinked UI state from #210, but this issue seems deeper: the actual identifier written during manual linking appears to differ from the identifier used by AMS auto-sync. ### 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:29:59 +02:00

closed this issue
added the
bug

contrib
labels

BreizhHardware commented

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

Author

Owner

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

@shrunbr: can I assign it to you?

@maziggy commented on GitHub (Mar 15, 2026): @shrunbr: can I assign it to you?

BreizhHardware commented

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

Author

Owner

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

@maziggy - Yeah go ahead and assign this to me, I'll take a look at this soon.

@shrunbr commented on GitHub (Mar 15, 2026): @maziggy - Yeah go ahead and assign this to me, I'll take a look at this soon.

BreizhHardware commented

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

Author

Owner

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

Resolved in #719, this can be closed.

@shrunbr commented on GitHub (Mar 17, 2026): Resolved in #719, this can be closed.

BreizhHardware commented

2026-05-06 12:30:00 +02:00

Author

Owner

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

Available in branch dev and available with the next release or daily build.

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

@maziggy commented on GitHub (Mar 17, 2026): Available in branch dev and available with the next release or daily build. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!