[GH-ISSUE #681] [Bug]: Filament spool profile is not applied correctly to AMS slot #451

Closed
opened 2026-05-06 12:29:40 +02:00 by BreizhHardware · 26 comments

Originally created by @RosdasHH on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/681

Originally assigned to: @maziggy on GitHub.

Bug Description

When assigning a filament spool to an AMS slot, Bambuddy selects a different filament profile than the one used when creating the spool.

Expected Behavior

The filament profile used when creating the spool should be applied to the AMS slot on spool assign.

Steps to Reproduce

  1. Go to the Filaments tab.
  2. Create a new spool.
  3. Select a filament preset (for example Generic PLA or Bambu PLA Basic).
  4. Click Add Spool.
  5. Go to the Printers tab.
  6. Assign the created spool to an AMS slot.

Result:
Instead of the created filament profile being used, another profile gets selected. Here are my observerd mappings:

  • Generic PLA -> Overture Matte PLA (Wrong)
  • Bambu PLA Basic -> PolyLite PLA (Wrong)
  • Bambu PLA Matte -> PolyTerra PLA (Wrong)
  • Generic PETG -> "" (Wrong!?)
  • Bambu PETG Basic -> Bambu PETG Basic (Correct)

Printer Model

Not printer-related

Bambuddy Version

v0.2.2b3

Printer Firmware Version

A1M: 01.07.02.00 | P1S: 01.09.01.00

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

[bambuddy-support-20260312-180921.zip](https://github.com/user-attachments/files/25943468/bambuddy-support-20260312-180921.zip)

Screenshots

Creating Spool
Image

Selected Profile is Generic
Image

Assigning the new Generic spool
Image

Profile is now set to Overture PLA Basic

Image Image

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 @RosdasHH on GitHub (Mar 12, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/681 Originally assigned to: @maziggy on GitHub. ### Bug Description When assigning a filament spool to an AMS slot, Bambuddy selects a different filament profile than the one used when creating the spool. ### Expected Behavior The filament profile used when creating the spool should be applied to the AMS slot on spool assign. ### Steps to Reproduce 1. Go to the Filaments tab. 2. Create a new spool. 3. Select a filament preset (for example Generic PLA or Bambu PLA Basic). 4. Click Add Spool. 5. Go to the Printers tab. 6. Assign the created spool to an AMS slot. Result: Instead of the created filament profile being used, another profile gets selected. Here are my observerd mappings: - Generic PLA -> Overture Matte PLA (Wrong) - Bambu PLA Basic -> PolyLite PLA (Wrong) - Bambu PLA Matte -> PolyTerra PLA (Wrong) - Generic PETG -> "" (Wrong!?) - Bambu PETG Basic -> Bambu PETG Basic (Correct) ### Printer Model Not printer-related ### Bambuddy Version v0.2.2b3 ### Printer Firmware Version A1M: 01.07.02.00 | P1S: 01.09.01.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell [bambuddy-support-20260312-180921.zip](https://github.com/user-attachments/files/25943468/bambuddy-support-20260312-180921.zip) ``` ### Screenshots Creating Spool <img width="547" height="567" alt="Image" src="https://github.com/user-attachments/assets/89fcb9f6-e21d-4bdd-9133-7f26f80f1071" /> Selected Profile is Generic <img width="336" height="333" alt="Image" src="https://github.com/user-attachments/assets/b6f88216-d6c8-4948-b84b-7b2ff3f007db" /> Assigning the new Generic spool <img width="428" height="286" alt="Image" src="https://github.com/user-attachments/assets/1386118f-2e54-4f77-af58-273ae0973422" /> Profile is now set to Overture PLA Basic <img width="206" height="288" alt="Image" src="https://github.com/user-attachments/assets/e8ad0232-274d-484b-b80d-ef94bb281eab" /> <img width="378" height="107" alt="Image" src="https://github.com/user-attachments/assets/d7d0ecf3-d453-4558-b362-cc8204d42d41" /> ### 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:40 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

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

No, that's not correct.

Currently Bambuddy only supports auto AMS slot configuration for Bambu Lab Spools. For non Bambu Lab spools you need to configure th AMS slot manually and - optional - you can assign it to an inventory spool to track filament usage.

Wait for a few weeks. We are currently stafting beta testing for a fully automatic spool management which also supports non Bambu Lab spools with your own RFID tags.

<!-- gh-comment-id:4054147138 --> @maziggy commented on GitHub (Mar 13, 2026): No, that's not correct. Currently Bambuddy only supports auto AMS slot configuration for Bambu Lab Spools. For non Bambu Lab spools you need to configure th AMS slot manually and - optional - you can assign it to an inventory spool to track filament usage. Wait for a few weeks. We are currently stafting beta testing for a fully automatic spool management which also supports non Bambu Lab spools with your own RFID tags.
Author
Owner

@RosdasHH commented on GitHub (Mar 13, 2026):

Thanks for the clarification.

I initially assumed that assigning a filament spool to an AMS slot would both start the filament tracking and automatically apply the corresponding filament preset and color.

So just to confirm: this is currently not intended to work that way, and the expected workflow is:

  1. Assign the inventory spool to the AMS slot (for tracking).
  2. Manually configure the filament preset and color in the AMS slot configuration.

Is that correct?

I was confused because sometimes the color of the assigned filament gets applied to the slot and changes the preset, but to a wrong one.

<!-- gh-comment-id:4056609330 --> @RosdasHH commented on GitHub (Mar 13, 2026): Thanks for the clarification. I initially assumed that assigning a filament spool to an AMS slot would both start the filament tracking and automatically apply the corresponding filament preset and color. So just to confirm: this is currently not intended to work that way, and the expected workflow is: 1. Assign the inventory spool to the AMS slot (for tracking). 2. Manually configure the filament preset and color in the AMS slot configuration. Is that correct? I was confused because sometimes the color of the assigned filament gets applied to the slot and changes the preset, but to a wrong one.
Author
Owner

@peter-k-de commented on GitHub (Mar 13, 2026):

I can confirm that this does not work quite as one would expect. Let me give an example:

State before starting:

  • Current slot configuration: Generic PLA Green (or empty — doesn’t matter)
  • A non-Bambu spool (type doesn’t matter since it has no RFID) is inserted into AMS Slot 1

Steps:

  1. Assign a non-Bambu spool from the inventory with the profile “Generic PETG HF” to that slot.
    → The GUI shows the green popup: “Spool Assigned and AMS Slot Configured.”
    → After a few seconds, the slot is automatically configured as “Generic PETG HF” as expected.
    This works well, but it differs from what you wrote (“For non-Bambu Lab spools you need to configure the AMS slot manually”), which does not seem to apply in this case.

  2. Click “Unassign Spool” for that slot.
    → The spool gets unassigned (as expected).
    → The slot remains configured as “Generic PETG HF” (which is arguably OK).

  3. Now assign a spool from the inventory with the profile “Generic PLA Silk.”
    → The GUI again shows the popup: “Spool Assigned and AMS Slot Configured.”
    → However, the slot is now configured with a different, unrelated profile (Generic PLA White in this case).

I assume this is what the original issue reporter meant and that this behavior might not be intended.

I’m running v0.2.2b4-daily.20260313 and can provide a support package if needed. Thanks a lot for your fantastic work!

<!-- gh-comment-id:4057181186 --> @peter-k-de commented on GitHub (Mar 13, 2026): I can confirm that this does not work quite as one would expect. Let me give an example: State before starting: - Current slot configuration: Generic PLA Green (or empty — doesn’t matter) - A non-Bambu spool (type doesn’t matter since it has no RFID) is inserted into AMS Slot 1 Steps: 1. Assign a non-Bambu spool from the inventory with the profile “Generic PETG HF” to that slot. → The GUI shows the green popup: “Spool Assigned and AMS Slot Configured.” → After a few seconds, the slot is automatically configured as “Generic PETG HF” as expected. This works well, but it differs from what you wrote (“For non-Bambu Lab spools you need to configure the AMS slot manually”), which does not seem to apply in this case. 2. Click “Unassign Spool” for that slot. → The spool gets unassigned (as expected). → The slot remains configured as “Generic PETG HF” (which is arguably OK). 3. Now assign a spool from the inventory with the profile “Generic PLA Silk.” → The GUI again shows the popup: “Spool Assigned and AMS Slot Configured.” → However, the slot is now configured with a different, unrelated profile (Generic PLA White in this case). I assume this is what the original issue reporter meant and that this behavior might not be intended. I’m running v0.2.2b4-daily.20260313 and can provide a support package if needed. Thanks a lot for your fantastic work!
Author
Owner

@RosdasHH commented on GitHub (Mar 13, 2026):

Yeah that sounds like what I meant. Sorry if I was unclear.

<!-- gh-comment-id:4057251791 --> @RosdasHH commented on GitHub (Mar 13, 2026): Yeah that sounds like what I meant. Sorry if I was unclear.
Author
Owner

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

THere's currently some related work going on.

@peter-k-de a support package with latest daily version would be very helpful.

<!-- gh-comment-id:4060124869 --> @maziggy commented on GitHub (Mar 14, 2026): THere's currently some related work going on. @peter-k-de a support package with latest daily version would be very helpful.
Author
Owner

@peter-k-de commented on GitHub (Mar 14, 2026):

Thank you so much :-)

  1. State of AMS Slot 4 when log starts:
Image
  1. Then I'm assigning this Spool (Profile: Generic PLA Silk):
Image

{ "material": "PLA", "subtype": "Silk", "color_name": "Dual Black White", "rgba": "FFFFFFFF", "brand": "SUNLU", "label_weight": 1000, "core_weight": 250, "core_weight_catalog_id": 24, "weight_used": 156.97, "slicer_filament": "GFSL99_01", "slicer_filament_name": "Generic PLA Silk", "nozzle_temp_min": null, "nozzle_temp_max": null, "note": "....... (removed)........", "tag_uid": null, "tray_uuid": null, "data_origin": null, "tag_type": null, "cost_per_kg": 20.99, "weight_locked": true, "last_scale_weight": null, "last_weighed_at": null, "id": 43, "added_full": null, "last_used": "2026-03-13T13:57:48.410197", "encode_time": null, "archived_at": null, "created_at": "2026-02-28T18:48:43", "updated_at": "2026-03-13T13:57:48", "k_profiles": [] }

  1. State of AMS Slot 4 afterwards (Slot 4 now got Generic PLA Profile instead Generic PLA SILK Profile):
Image

API Printer State after the Assignment: (see AMS id 0 slot id 3):

{
"id": 1,
"name": "H2D R176",
"connected": true,
.........
},
"cover_url": null,
"hms_errors": [
{
"code": "0x2001b",
"attr": 201326848,
"module": 12,
"severity": 1
}
],
"ams": [
{
"id": 0,
"humidity": 8,
"temp": 27.2,
"is_ams_ht": false,
"tray": [
.........
{
"id": 3,
"tray_color": "FFFFFFFF",
"tray_type": "PLA",
"tray_sub_brands": "",
"tray_id_name": "",
"tray_info_idx": "GFL99",
"remain": -1,
"k": null,
"cali_idx": -1,
"tag_uid": null,
"tray_uuid": null,
"nozzle_temp_min": 190,
"nozzle_temp_max": 230,
"drying_temp": 0,
"drying_time": 0
}
],
},
............

/api/v1/inventory/assignments after the Assignment::

...

{
"id": 54,
"spool_id": 43,
"printer_id": 1,
"printer_name": "H2D R176",
"ams_id": 0,
"tray_id": 3,
"fingerprint_color": "FFFFFFFF",
"fingerprint_type": "PLA",
"created_at": "2026-03-14T18:47:48",
"spool": {
"material": "PLA",
"subtype": "Silk",
"color_name": "Dual Black White",
"rgba": "FFFFFFFF",
"brand": "SUNLU",
"label_weight": 1000,
"core_weight": 250,
"core_weight_catalog_id": 24,
"weight_used": 156.97,
"slicer_filament": "GFSL99_01",
"slicer_filament_name": "Generic PLA Silk",
"nozzle_temp_min": null,
"nozzle_temp_max": null,
"note": "own_tagid=0427F404C12A81 last_scan=2026-03-13T12:40:15 rgb2=000000 last_weight=1126.70 last_weigh_timestamp=2026-03-04T14:29:35",
"tag_uid": null,
"tray_uuid": null,
"data_origin": null,
"tag_type": null,
"cost_per_kg": 20.99,
"weight_locked": true,
"last_scale_weight": null,
"last_weighed_at": null,
"id": 43,
"added_full": null,
"last_used": "2026-03-13T13:57:48.410197",
"encode_time": null,
"archived_at": null,
"created_at": "2026-02-28T18:48:43",
"updated_at": "2026-03-13T13:57:48",
"k_profiles": []
},
"configured": false,
"ams_label": null
},

]

bambuddy-support-20260314-191845.zip

<!-- gh-comment-id:4061101904 --> @peter-k-de commented on GitHub (Mar 14, 2026): Thank you so much :-) 1. State of AMS Slot 4 when log starts: <img width="243" height="329" alt="Image" src="https://github.com/user-attachments/assets/003e1aa4-0a9d-4599-8c5d-a40fae5e38d6" /> 2. Then I'm assigning this Spool (Profile: Generic PLA Silk): <img width="603" height="691" alt="Image" src="https://github.com/user-attachments/assets/74eb6e99-5b27-4da7-9ffc-c547c4283937" /> `{ "material": "PLA", "subtype": "Silk", "color_name": "Dual Black White", "rgba": "FFFFFFFF", "brand": "SUNLU", "label_weight": 1000, "core_weight": 250, "core_weight_catalog_id": 24, "weight_used": 156.97, "slicer_filament": "GFSL99_01", "slicer_filament_name": "Generic PLA Silk", "nozzle_temp_min": null, "nozzle_temp_max": null, "note": "....... (removed)........", "tag_uid": null, "tray_uuid": null, "data_origin": null, "tag_type": null, "cost_per_kg": 20.99, "weight_locked": true, "last_scale_weight": null, "last_weighed_at": null, "id": 43, "added_full": null, "last_used": "2026-03-13T13:57:48.410197", "encode_time": null, "archived_at": null, "created_at": "2026-02-28T18:48:43", "updated_at": "2026-03-13T13:57:48", "k_profiles": [] }` 3. State of AMS Slot 4 afterwards (Slot 4 now got Generic PLA Profile instead Generic PLA SILK Profile): <img width="225" height="375" alt="Image" src="https://github.com/user-attachments/assets/7a0edf19-ccd8-4f73-8337-54c50756f4a3" /> API Printer State after the Assignment: (see AMS id 0 slot id 3): { "id": 1, "name": "H2D R176", "connected": true, ......... }, "cover_url": null, "hms_errors": [ { "code": "0x2001b", "attr": 201326848, "module": 12, "severity": 1 } ], "ams": [ { "id": 0, "humidity": 8, "temp": 27.2, "is_ams_ht": false, "tray": [ ......... { "id": 3, "tray_color": "FFFFFFFF", "tray_type": "PLA", "tray_sub_brands": "", "tray_id_name": "", "tray_info_idx": "GFL99", "remain": -1, "k": null, "cali_idx": -1, "tag_uid": null, "tray_uuid": null, "nozzle_temp_min": 190, "nozzle_temp_max": 230, "drying_temp": 0, "drying_time": 0 } ], }, ............ /api/v1/inventory/assignments after the Assignment:: ... { "id": 54, "spool_id": 43, "printer_id": 1, "printer_name": "H2D R176", "ams_id": 0, "tray_id": 3, "fingerprint_color": "FFFFFFFF", "fingerprint_type": "PLA", "created_at": "2026-03-14T18:47:48", "spool": { "material": "PLA", "subtype": "Silk", "color_name": "Dual Black White", "rgba": "FFFFFFFF", "brand": "SUNLU", "label_weight": 1000, "core_weight": 250, "core_weight_catalog_id": 24, "weight_used": 156.97, "slicer_filament": "GFSL99_01", "slicer_filament_name": "Generic PLA Silk", "nozzle_temp_min": null, "nozzle_temp_max": null, "note": "own_tagid=0427F404C12A81 last_scan=2026-03-13T12:40:15 rgb2=000000 last_weight=1126.70 last_weigh_timestamp=2026-03-04T14:29:35", "tag_uid": null, "tray_uuid": null, "data_origin": null, "tag_type": null, "cost_per_kg": 20.99, "weight_locked": true, "last_scale_weight": null, "last_weighed_at": null, "id": 43, "added_full": null, "last_used": "2026-03-13T13:57:48.410197", "encode_time": null, "archived_at": null, "created_at": "2026-02-28T18:48:43", "updated_at": "2026-03-13T13:57:48", "k_profiles": [] }, "configured": false, "ams_label": null }, ] [bambuddy-support-20260314-191845.zip](https://github.com/user-attachments/files/25999158/bambuddy-support-20260314-191845.zip)
Author
Owner

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

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

Please let me know if it works for you now.


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

<!-- gh-comment-id:4062597246 --> @maziggy commented on GitHub (Mar 15, 2026): Fixed in branch dev and available in the next release or daily build. Please let me know if it works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!
Author
Owner

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

I just tested the new daily build, and the problem is completely solved now. Thanks a lot for your work on this project. I really appreciate it.

<!-- gh-comment-id:4063260032 --> @RosdasHH commented on GitHub (Mar 15, 2026): I just tested the new daily build, and the problem is completely solved now. Thanks a lot for your work on this project. I really appreciate it.
Author
Owner

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


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

<!-- gh-comment-id:4063263310 --> @maziggy commented on GitHub (Mar 15, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!
Author
Owner

@peter-k-de commented on GitHub (Mar 16, 2026):

I tested it too, and it seems to be fixed to some extend, but let me show you this - state before (Slot 4 configured as Generic PETG Red to better see the problem):

Image

Then, after assigning the same spool as in my logs last time (Spool profile = Generic PLA Silk):

Image

The Tray-button is now correctly labeled as PLA, but in the slot popup it still say Generic PETG. On the printer itself though, it is perfectly fine now (configured as Generic PLA Silk), which wasn't the case before your fix:

Image

But Bambuddy API also reports the wrong preset for this slot (the PETG one before assigning the spool):

{
"ams_id": 0,
"tray_id": 3,
"preset_id": "GFSG99",
"preset_name": "Generic PETG"
}

<!-- gh-comment-id:4066007485 --> @peter-k-de commented on GitHub (Mar 16, 2026): I tested it too, and it seems to be fixed to some extend, but let me show you this - state before (Slot 4 configured as Generic PETG Red to better see the problem): <img width="240" height="320" alt="Image" src="https://github.com/user-attachments/assets/209ebf8e-9ffe-45c8-94a2-13adeb4ff0ce" /> Then, after assigning the same spool as in my logs last time (Spool profile = Generic PLA Silk): <img width="222" height="364" alt="Image" src="https://github.com/user-attachments/assets/e0db58a7-1d3b-420e-bf89-4fae1839c1bc" /> The Tray-button is now correctly labeled as PLA, but in the slot popup it still say Generic PETG. On the printer itself though, it is perfectly fine now (configured as Generic PLA Silk), which wasn't the case before your fix: <img width="1290" height="619" alt="Image" src="https://github.com/user-attachments/assets/7b02b595-5a95-4536-b6d2-d823b9a87456" /> But Bambuddy API also reports the wrong preset for this slot (the PETG one before assigning the spool): { "ams_id": 0, "tray_id": 3, "preset_id": "GFSG99", "preset_name": "Generic PETG" }
Author
Owner

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

What version are you running?

<!-- gh-comment-id:4066019248 --> @maziggy commented on GitHub (Mar 16, 2026): What version are you running?
Author
Owner

@peter-k-de commented on GitHub (Mar 16, 2026):

I'm on v0.2.2b4-daily.20260315 - so your patch for this issue should be included (and indeed works somehow - now the correct profile "Generic PLA Silk" is sent to the printer)

<!-- gh-comment-id:4066188538 --> @peter-k-de commented on GitHub (Mar 16, 2026): I'm on v0.2.2b4-daily.20260315 - so your patch for this issue should be included (and indeed works somehow - now the correct profile "Generic PLA Silk" is sent to the printer)
Author
Owner

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

What does "works somehow" mean?

<!-- gh-comment-id:4066354486 --> @maziggy commented on GitHub (Mar 16, 2026): What does "works somehow" mean?
Author
Owner

@RosdasHH commented on GitHub (Mar 16, 2026):

Yes, I can confirm this issue as well.

I selected a spool with the profile “Bambu PLA Silk”, and the correct filament information is successfully sent to the printer.
Image

However, the UI in Bambuddy does not update to reflect this change, even after reconnecting the printer.
Image

It appears that the issue is only related to the UI display. When selecting the spool, the printer receives the correct filament profile, but the profile shown in Bambuddy does not refresh or update accordingly.

<!-- gh-comment-id:4066397267 --> @RosdasHH commented on GitHub (Mar 16, 2026): Yes, I can confirm this issue as well. I selected a spool with the profile “Bambu PLA Silk”, and the correct filament information is successfully sent to the printer. <img width="360" height="91" alt="Image" src="https://github.com/user-attachments/assets/23c4b0ad-6dc3-4d08-bf16-401bcfefafbd" /> However, the UI in Bambuddy does not update to reflect this change, even after reconnecting the printer. <img width="197" height="280" alt="Image" src="https://github.com/user-attachments/assets/b2e9937c-41f4-4cd3-bfed-7a2875ed5252" /> It appears that the issue is only related to the UI display. When selecting the spool, the printer receives the correct filament profile, but the profile shown in Bambuddy does not refresh or update accordingly.
Author
Owner

@peter-k-de commented on GitHub (Mar 16, 2026):

@RosdasHH exactly my issue!

@maziggy what "works somehow" means : Before v0.2.2b4-daily.20260315, some special Filament types as "Generic PLA Silk" were replaced with other variants (in this case, Generic PLA) when assigning a spool to an AMS-Slot. So the slot got configured with the wrong type as the printer, too. Now the printer gets configured correctly (see screenshots of me above), but the slot info in bambuddy doesn't get updated (see my and @RosdasHHs screenshots).

<!-- gh-comment-id:4066417735 --> @peter-k-de commented on GitHub (Mar 16, 2026): @RosdasHH exactly my issue! @maziggy what "works somehow" means : Before v0.2.2b4-daily.20260315, some special Filament types as "Generic PLA Silk" were replaced with other variants (in this case, Generic PLA) when assigning a spool to an AMS-Slot. So the slot got configured with the wrong type as the printer, too. Now the printer gets configured correctly (see screenshots of me above), but the slot info in bambuddy doesn't get updated (see my and @RosdasHHs screenshots).
Author
Owner

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

Wait for the daily image later today. It should already be fixed.

<!-- gh-comment-id:4066456130 --> @maziggy commented on GitHub (Mar 16, 2026): Wait for the daily image later today. It should already be fixed.
Author
Owner

@RosdasHH commented on GitHub (Mar 16, 2026):

I just checked and can confirm that this issue is resolved in the latest dev branch.

<!-- gh-comment-id:4066610512 --> @RosdasHH commented on GitHub (Mar 16, 2026): I just checked and can confirm that this issue is resolved in the latest dev branch.
Author
Owner

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

It works for most of my spools. The only one I found that still isn't set correctly in the Bambuddy UI is "Bambu PLA Silk". It gets correctly sent to the printer, but in the Bambuddy UI the profile gets updated to "Bambu PLA Matte".

This is my silk filament:
Image

And this profile gets selected in Bambuddy when I assign the spool:
Image

On the printer side it's alright:
Image

There may be other filaments with the same problem, but I didn't find any others in my random sample test.

<!-- gh-comment-id:4076645848 --> @RosdasHH commented on GitHub (Mar 17, 2026): It works for most of my spools. The only one I found that still isn't set correctly in the Bambuddy UI is "Bambu PLA Silk". It gets correctly sent to the printer, but in the Bambuddy UI the profile gets updated to "Bambu PLA Matte". This is my silk filament: <img width="300" alt="Image" src="https://github.com/user-attachments/assets/bb262507-8121-4b4b-b004-551368a6ac81" /> And this profile gets selected in Bambuddy when I assign the spool: <img width="300" alt="Image" src="https://github.com/user-attachments/assets/56807f68-3d3d-4158-af4d-0d833fb348c7" /> On the printer side it's alright: <img width="300" alt="Image" src="https://github.com/user-attachments/assets/119d3115-64cb-4c4b-8ce8-da87f1cca2e4" /> There may be other filaments with the same problem, but I didn't find any others in my random sample test.
Author
Owner

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

And I am not sure if this is wanted or not, but when you search in the config tab of a filled AMS slot for something unavailable, you get results for the profile of the currently selected spool on this slot.

Example:
Generic PLA is on this slot right now and I find Generic PLA profiles when I search for a profile that isn't there:

Image

It's also interesting that when I select the slot with the silk profile from the above comment, I get results for "Bambu PLA Matte" and "Bambu PLA Silk". It seems that these two profiles get mixed in some way, which could lead to the issue of the issue in the comment above?

Image

But for my understanding nothing should be displayed if it doesn't match the search text, right?
<!-- gh-comment-id:4076786420 --> @RosdasHH commented on GitHub (Mar 17, 2026): And I am not sure if this is wanted or not, but when you search in the config tab of a filled AMS slot for something unavailable, you get results for the profile of the currently selected spool on this slot. Example: Generic PLA is on this slot right now and I find Generic PLA profiles when I search for a profile that isn't there: <img width="300" alt="Image" src="https://github.com/user-attachments/assets/929e55f2-728b-4214-b204-06e5a0081850" /> <br><br> It's also interesting that when I select the slot with the silk profile from the above comment, I get results for "Bambu PLA Matte" and "Bambu PLA Silk". It seems that these two profiles get mixed in some way, which could lead to the issue of the issue in the comment above? <br><br> <img width="300" alt="Image" src="https://github.com/user-attachments/assets/2b8c5d48-14c3-4b12-a353-4c0ed14206f1" /> <br><br> But for my understanding nothing should be displayed if it doesn't match the search text, right?
Author
Owner

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

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

<!-- gh-comment-id:4080242368 --> @maziggy commented on GitHub (Mar 18, 2026): Available in branch dev and available with the next release or daily build. Please let me know if it works for you now.
Author
Owner

@RosdasHH commented on GitHub (Mar 18, 2026):

Yepp works now. Thank you
What about my second message? Is this supposed to happen?

<!-- gh-comment-id:4083766008 --> @RosdasHH commented on GitHub (Mar 18, 2026): Yepp works now. Thank you What about my second message? Is this supposed to happen?
Author
Owner

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

What do you mean?

<!-- gh-comment-id:4084154219 --> @maziggy commented on GitHub (Mar 18, 2026): What do you mean?
Author
Owner

@RosdasHH commented on GitHub (Mar 18, 2026):

When I search in the slot configuration of an AMS slot for a filament profile that does not exist, the search results return profiles matching the type of the currently selected AMS slot.

Example:
I've selected a filament with the "Generic PLA" profile:

Image

When I then search for a non-existent filament profile within this slot, the results display multiple profiles related to “Generic PLA,” even though my search query does not include this term:

Image

I would expect no results to be displayed if there are no matches for the search query?

<!-- gh-comment-id:4084220629 --> @RosdasHH commented on GitHub (Mar 18, 2026): When I search in the slot configuration of an AMS slot for a filament profile that does not exist, the search results return profiles matching the type of the currently selected AMS slot. Example: I've selected a filament with the "Generic PLA" profile: <img width="200" alt="Image" src="https://github.com/user-attachments/assets/6bc41076-997b-4e2c-b554-ba83ff63563d" /> When I then search for a non-existent filament profile within this slot, the results display multiple profiles related to “Generic PLA,” even though my search query does not include this term: <img width="300" alt="Image" src="https://github.com/user-attachments/assets/ebb4e6e6-d400-4853-ac00-4a0ff002c0f6" /> I would expect no results to be displayed if there are no matches for the search query?
Author
Owner

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

Available/Fixed 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!

<!-- gh-comment-id:4088336041 --> @maziggy commented on GitHub (Mar 19, 2026): Available/Fixed 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/maziggy/bambuddy) — it helps others discover the project!
Author
Owner

@RosdasHH commented on GitHub (Mar 21, 2026):

The search works now as expected for most of the spools, but not for "Bambu PLA Silk".
When I assign a Bambu Silk spool and search for something not available I get "Bambu PLA Matte" instead of "Bambu PLA Silk":

Image Image
<!-- gh-comment-id:4103270946 --> @RosdasHH commented on GitHub (Mar 21, 2026): The search works now as expected for most of the spools, but not for "Bambu PLA Silk". When I assign a Bambu Silk spool and search for something not available I get "Bambu PLA Matte" instead of "Bambu PLA Silk": <img width="25%" alt="Image" src="https://github.com/user-attachments/assets/75e68692-53a0-4a19-b1e0-418ca2f526e0" /> <img width="60%" alt="Image" src="https://github.com/user-attachments/assets/280b9f76-48ef-4549-aebe-cdc8e7c9d114" />
Author
Owner

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

Sorry, should have tested it better.

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


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

<!-- gh-comment-id:4103308423 --> @maziggy commented on GitHub (Mar 21, 2026): Sorry, should have tested it better. Available/Fixed in branch dev and available with the next release or daily build. PLease let me know if it works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#451
No description provided.