mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #1068] [Feature]: (Spoolman) Don't Sync AMS tray UUID as tag with 3rd Party Spools #759
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#759
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 @xeonixo on GitHub (Apr 21, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1068
Originally assigned to: @netscout2001 on GitHub.
Problem or Use Case
Hi! I use Bambuddy v0.2.4b1 with external Spoolman (0.23.1).
One thing, that annoys me, is the synced tray UUID as "spool tag". I print mostly SUNLU filament.
SUNLU Spool:

Bambu Spool:

Proposed Solution
Only sync supported bambu spool tags, but not tray UUIDs
Alternatives Considered
disabled sync to spoolman.. but this is not a real solution.
Feature Category
Spoolman Integration
Priority
Nice to have
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Apr 21, 2026):
@netscout2001
@netscout2001 commented on GitHub (Apr 22, 2026):
@xeonixo, thank you very much for your report.
I’m not quite sure what your problem is, though. You’re showing a Sunlu spool that apparently has an RFID tag attached to it, which is saved as a tag in Spoolman. That’s exactly how it’s supposed to work. I’m not sure where the problem lies. Maybe you could describe it in more detail.
Best regards,
Sn0rri
@xeonixo commented on GitHub (Apr 22, 2026):
@netscout2001 thanks for the fast reply!
Unfortunately, that’s not the case. This tag is also written in Spoolman for other spools in that tray. That's why I am assuming, that it is the tray UUID.
As far as I know, SUNLU spools don’t have a tag; at least, I haven’t found one yet.
Furthermore, I’m quite certain that Bambulab doesn’t read third-party tags, since they aren’t signed correctly.
@netscout2001 commented on GitHub (Apr 22, 2026):
Oh, thanks. That makes it clearer now. So you have this tag UUID in multiple coils. That shouldn't be the case, of course.
Thanks for the information.
@xeonixo commented on GitHub (Apr 22, 2026):
I found those tags on multiple spools from different brands:
6319B70A00FF0000 (GEEETECH TPU black, used on external spool left head)
6319B70A00000000 (SUNLU ABS gray)
6319B70A00000001 (SUNLU PLA+2.0 black)
0F08D7BF00000000 (SUNLU PETG pink)
6319B70A00000002 (SUNLU PETG gray)
Based on this, it's probably based on "generic", "material", "color" and "tray number". But it's not unique.
(AMS 2 Pro, X2D)
Edit: SUNLU PETG Pink was last used on my P1S with AMS Gen1. My fault.
Edit 2: it's probably just the UUID Printer + AMS Tray number
@maziggy commented on GitHub (Apr 22, 2026):
The question is: where are the tags coming from? Bambuddy doesn't write any non BL tags to the inventory.
@maziggy commented on GitHub (Apr 24, 2026):
After thinking about it I'm going to leave this as-is for now. The tag_uid fallback has been in place since an upstream
fix for a firmware/reader combo where tray_uuid isn't reliably published, and the AMS sync path as a whole is at a level of stability I don't want to disturb for a cosmetic Spoolman pollution issue. If a synthetic tag ends up in Spoolman, it can be deleted manually once, or automatically via script; the printer won't keep re-creating it as long as the entry exists and matches by location.