[GH-ISSUE #857] [Bug]: Filament color name and subtypes are out of sync between Filament window, AMS Slot window, and the AMS page on the actual printer.

BreizhHardware commented

2026-05-07 00:11:50 +02:00

Owner

Originally created by @lightmaster on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/857

Originally assigned to: @maziggy on GitHub.

Bug Description

I noticed some inconsistencies between the Filament's page and the Printer page's AMS Slot, as well as some missing filament subtypes.

Bambu's Silk+ is missing, and seeing as it's distinctly different from their original Silk filament, I think it should have it's own subtype. It's different enough that Bambu says Silk can't be printed on the SuperTak plate but Silk+ can be.
In my screenshots, I have Bambu's PLA Silk+ Titan Gray filament loaded. On the Filament page, the automatic recognition from the AMS labels it as just "Silk" filament, whereas on the AMS Slot on the Printer page it does show up as "Silk+".
On both the Edit Spool window and the configure AMS Slot window, the color for this filament is selected as "Titan Gray", however in the mouseover popup for the AMS slot, it calls the filament color "Dark Gray" instead.
I noticed a similar issue for the Gradient and Dual Color filaments, but in this case the Configure AMS Slot window doesn't show the name "South Beach", but the mouseover popup does show the name "South Beach". If I attempt to change it in Bambuddy, it sets the color on the AMS to be "Pink" instead of "South Beach" (the AMS shows a gradient shift from Pink to Blue, whereas Bambuddy shows just Pink).
In fact, none of the Gradient and Dual Color filaments I have show up as prefilled names on the Edit Spool and Configure AMS Slot windows.
Bambu PLA Silk Dual Color get's auto detected as "Silk" instead of "Dual Color" and Bambu PLA Basic Gradient gets auto detected as "PLA Basic" instead of "Gradient". While they are actually Silk and PLA Basic filaments, I think the Dual Color and Gradient subtypes fit better to better describe what these filaments are.

Expected Behavior

Each type of Bambu filament should have it's own separate subtype (adding Silk+ and recategorizing PLA Basic Gradient and PLA Silk Dual Color). The Filaments window and the Printer's AMS Slot windows should agree on the information of what each filament is (name and type of filament)

Steps to Reproduce

Sync (or create a spool) using Silk+, PLA Basic Gradient, or PLA Silk Dual Color filaments
Check the color names and types on both the Edit Spool and AMS Slot windows

Printer Model

X1 Carbon

Bambuddy Version

0.2.2.2

Printer Firmware Version

99.00.00.00 (X1Plus firmare)

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

bambuddy-support-20260331-044224.zip

Screenshots

Additional Context

My printer is running X1Plus, which negates the need for LAN Only or Developer Mode, granting full access to MQTT and SSH root while being in cloud mode.

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 @lightmaster on GitHub (Mar 31, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/857 Originally assigned to: @maziggy on GitHub. ### Bug Description I noticed some inconsistencies between the Filament's page and the Printer page's AMS Slot, as well as some missing filament subtypes. 1. Bambu's Silk+ is missing, and seeing as it's distinctly different from their original Silk filament, I think it should have it's own subtype. It's different enough that Bambu says Silk can't be printed on the SuperTak plate but Silk+ can be. 2. In my screenshots, I have Bambu's PLA Silk+ Titan Gray filament loaded. On the Filament page, the automatic recognition from the AMS labels it as just "Silk" filament, whereas on the AMS Slot on the Printer page it does show up as "Silk+". 3. On both the Edit Spool window and the configure AMS Slot window, the color for this filament is selected as "Titan Gray", however in the mouseover popup for the AMS slot, it calls the filament color "Dark Gray" instead. 4. I noticed a similar issue for the Gradient and Dual Color filaments, but in this case the Configure AMS Slot window doesn't show the name "South Beach", but the mouseover popup does show the name "South Beach". If I attempt to change it in Bambuddy, it sets the color on the AMS to be "Pink" instead of "South Beach" (the AMS shows a gradient shift from Pink to Blue, whereas Bambuddy shows just Pink). 5. In fact, none of the Gradient and Dual Color filaments I have show up as prefilled names on the Edit Spool and Configure AMS Slot windows. 6. Bambu PLA Silk Dual Color get's auto detected as "Silk" instead of "Dual Color" and Bambu PLA Basic Gradient gets auto detected as "PLA Basic" instead of "Gradient". While they are actually Silk and PLA Basic filaments, I think the Dual Color and Gradient subtypes fit better to better describe what these filaments are. ### Expected Behavior Each type of Bambu filament should have it's own separate subtype (adding Silk+ and recategorizing PLA Basic Gradient and PLA Silk Dual Color). The Filaments window and the Printer's AMS Slot windows should agree on the information of what each filament is (name and type of filament) ### Steps to Reproduce 1. Sync (or create a spool) using Silk+, PLA Basic Gradient, or PLA Silk Dual Color filaments 2. Check the color names and types on both the Edit Spool and AMS Slot windows ### Printer Model X1 Carbon ### Bambuddy Version 0.2.2.2 ### Printer Firmware Version 99.00.00.00 (X1Plus firmare) ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package [bambuddy-support-20260331-044224.zip](https://github.com/user-attachments/files/26372900/bambuddy-support-20260331-044224.zip) ### Screenshots <img width="579" height="897" alt="Image" src="https://github.com/user-attachments/assets/dd9b2e27-4fde-4c1e-983f-2c3ecfddabbd" /> <img width="586" height="905" alt="Image" src="https://github.com/user-attachments/assets/fe46bbff-4b3b-4c30-9845-060637d89c61" /> <img width="1605" height="567" alt="Image" src="https://github.com/user-attachments/assets/dd4dbef5-0303-46a9-a6b3-3eac086b4890" /> <img width="237" height="287" alt="Image" src="https://github.com/user-attachments/assets/c5683388-ad3f-4700-8a31-f56ae3434a4e" /> <img width="535" height="734" alt="Image" src="https://github.com/user-attachments/assets/e95aad26-fbf5-413a-8113-c23c84f92dac" /> <img width="573" height="420" alt="Image" src="https://github.com/user-attachments/assets/13e04c8e-e83b-41f5-bc4f-f456540d2858" /> <img width="572" height="464" alt="Image" src="https://github.com/user-attachments/assets/f9942a97-fbe8-4188-a2b9-559468128b86" /> ### Additional Context My printer is running X1Plus, which negates the need for LAN Only or Developer Mode, granting full access to MQTT and SSH root while being in cloud mode. ### 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:11:50 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:11:50 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 1, 2026):

Now that's a perfect compiled issue 👍 💯

@maziggy commented on GitHub (Apr 1, 2026): Now that's a perfect compiled issue 👍 💯

BreizhHardware commented

2026-05-07 00:11:51 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 1, 2026):

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

Please let me know if it works for you.

@maziggy commented on GitHub (Apr 1, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.

BreizhHardware commented

2026-05-07 00:11:51 +02:00

Author

Owner

@lightmaster commented on GitHub (Apr 1, 2026):

For the sake of completeness, it was reported by lightmaster, not Frosty_Jackal

github.com/maziggy/bambuddy@75fa935851 (diff-06572a96a5)

@lightmaster commented on GitHub (Apr 1, 2026): For the sake of completeness, it was reported by lightmaster, not Frosty_Jackal https://github.com/maziggy/bambuddy/commit/75fa93585109f097125c96b1f79f05bb73e20c42#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edR23

BreizhHardware commented

2026-05-07 00:11:51 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 1, 2026):

Ups, fixed.

@maziggy commented on GitHub (Apr 1, 2026): Ups, fixed.

BreizhHardware commented

2026-05-07 00:11:51 +02:00

Author

Owner

@lightmaster commented on GitHub (Apr 2, 2026):

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

Please let me know if it works for you.

I attempted to, but the dev branch is bugged for me (Issue https://github.com/maziggy/bambuddy/issues/873) and I am unable to see anything about the AMS or much about the printer at all while on the dev branch.

@lightmaster commented on GitHub (Apr 2, 2026): > Available/Fixed in branch dev and available with the next release or daily build. > > Please let me know if it works for you. I attempted to, but the dev branch is bugged for me (Issue https://github.com/maziggy/bambuddy/issues/873) and I am unable to see anything about the AMS or much about the printer at all while on the dev branch.

BreizhHardware commented

2026-05-07 00:11:51 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 3, 2026):

Try again.

commit d327c70006
Author: maziggy mz@v8w.de
Date: Thu Apr 2 13:58:42 2026 +0200

  Fix WebSocket crash on printers without fun field (#873)

  Race condition in _update_state: dev mode probe released GIL via MQTT
  publish between raw_data overwrite and vt_tray list restoration, letting
  the event loop iterate over raw dict keys (strings) instead of spool
  dicts. Affects A1, P1, and X1Plus firmware that don't send the fun field.

  Fix: normalize vt_tray dict→list before raw_data assignment, restore
  preserved fields before any GIL-releasing work, add defensive guard in
  printer_state_to_dict.

@maziggy commented on GitHub (Apr 3, 2026): Try again. commit d327c70006bffd8a3fa3dbee1e0b1c2055455fbd Author: maziggy <mz@v8w.de> Date: Thu Apr 2 13:58:42 2026 +0200 Fix WebSocket crash on printers without fun field (#873) Race condition in _update_state: dev mode probe released GIL via MQTT publish between raw_data overwrite and vt_tray list restoration, letting the event loop iterate over raw dict keys (strings) instead of spool dicts. Affects A1, P1, and X1Plus firmware that don't send the fun field. Fix: normalize vt_tray dict→list before raw_data assignment, restore preserved fields before any GIL-releasing work, add defensive guard in printer_state_to_dict.

BreizhHardware commented

2026-05-07 00:11:51 +02:00

Author

Owner

@lightmaster commented on GitHub (Apr 9, 2026):

Sorry, forgot to get back to you. Haven't noticed anything messed up with this in the latest dev branch. Thanks.

@lightmaster commented on GitHub (Apr 9, 2026): Sorry, forgot to get back to you. Haven't noticed anything messed up with this in the latest dev branch. Thanks.

BreizhHardware commented

2026-05-07 00:11:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 9, 2026):

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

@maziggy commented on GitHub (Apr 9, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware commented

2026-05-07 00:11:52 +02:00

Author

Owner

@lightmaster commented on GitHub (Apr 10, 2026):

Actually, I just found one that's not right. PLA Translucent "Cherry Pink" is showing up as "Scarlet Red". I don't know if any of the other PLA Translucent filaments are affected, as this is the only one I have.

@lightmaster commented on GitHub (Apr 10, 2026): Actually, I just found one that's not right. PLA Translucent "Cherry Pink" is showing up as "Scarlet Red". I don't know if any of the other PLA Translucent filaments are affected, as this is the only one I have. <img width="227" height="260" alt="Image" src="https://github.com/user-attachments/assets/46fdfc68-b825-4ed0-bf79-7c5ed1d1a8e5" />   <img width="511" height="723" alt="Image" src="https://github.com/user-attachments/assets/c67e1037-1854-41a9-8f39-aa2fa9163b6f" />

BreizhHardware commented

2026-05-07 00:11:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 10, 2026):

Cannot reproduce.

What version you are running?
Did you changed anything in color database?
Cache problem (force reload page)?

@maziggy commented on GitHub (Apr 10, 2026): Cannot reproduce. - What version you are running? - Did you changed anything in color database? - Cache problem (force reload page)?

BreizhHardware commented

2026-05-07 00:11:52 +02:00

Author

Owner

@lightmaster commented on GitHub (Apr 10, 2026):

I'm running the same pull from the dev branch from yesterday, I'll pull again when this print gets done, but I don't see any commit that seems like it would effect anything since I last pulled.

I haven't changed anything in the color database, and the name of the color on the AMS, the K-profiles, and in my filament tab all say "Cherry Pink", it's only the Printer tab's AMS popup that says "Scarlet Red". Even the selected color/name for that slot says "Cherry Pink".

Just tried clearing the cache and refreshing the page and it still shows the same there.

I noticed it before starting this print and I unloaded that filament and reloaded it and the name still stuck.

bambuddy-support-20260410-044030.zip

@lightmaster commented on GitHub (Apr 10, 2026): I'm running the same pull from the dev branch from yesterday, I'll pull again when this print gets done, but I don't see any commit that seems like it would effect anything since I last pulled. I haven't changed anything in the color database, and the name of the color on the AMS, the K-profiles, and in my filament tab all say "Cherry Pink", it's only the Printer tab's AMS popup that says "Scarlet Red". Even the selected color/name for that slot says "Cherry Pink". Just tried clearing the cache and refreshing the page and it still shows the same there. I noticed it before starting this print and I unloaded that filament and reloaded it and the name still stuck. [bambuddy-support-20260410-044030.zip](https://github.com/user-attachments/files/26624965/bambuddy-support-20260410-044030.zip)

BreizhHardware commented

2026-05-07 00:11:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 11, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now.

Please note: The auto-created spool from 2026-04-04 is still in your database with color_name="Scarlet Red". The fix changes how new spools get named and how the live AMS popup looks up names from tray_color, but it can't retroactively rename existing inventory rows. Once you pull the next dev build, please rename spool 72 manually in Inventory →
edit → change color name to "Cherry Pink". It'll be a one-time cleanup.

@maziggy commented on GitHub (Apr 11, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now. Please note: The auto-created spool from 2026-04-04 is still in your database with color_name="Scarlet Red". The fix changes how new spools get named and how the live AMS popup looks up names from tray_color, but it can't retroactively rename existing inventory rows. Once you pull the next dev build, please rename spool 72 manually in Inventory → edit → change color name to "Cherry Pink". It'll be a one-time cleanup.

BreizhHardware referenced this issue

2026-05-07 00:15:54 +02:00

[PR #601] [CLOSED] v0.2.2b1 #1083

BreizhHardware referenced this issue

2026-05-07 00:15:54 +02:00

[PR #602] [MERGED] v0.2.2b1 #1084