mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #681] [Bug]: Filament spool profile is not applied correctly to AMS slot #451
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
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#451
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 @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
Result:
Instead of the created filament profile being used, another profile gets selected. Here are my observerd mappings:
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
Screenshots
Creating Spool

Selected Profile is Generic

Assigning the new Generic spool

Profile is now set to Overture PLA Basic
Additional Context
No response
Checklist
@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.
@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:
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.
@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:
Steps:
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.
Click “Unassign Spool” for that slot.
→ The spool gets unassigned (as expected).
→ The slot remains configured as “Generic PETG HF” (which is arguably OK).
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!
@RosdasHH commented on GitHub (Mar 13, 2026):
Yeah that sounds like what I meant. Sorry if I was unclear.
@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.
@peter-k-de commented on GitHub (Mar 14, 2026):
Thank you so much :-)
{ "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": [] }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
@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!
@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.
@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!
@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):
Then, after assigning the same spool as in my logs last time (Spool profile = Generic PLA Silk):
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:
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"
}
@maziggy commented on GitHub (Mar 16, 2026):
What version are you running?
@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)
@maziggy commented on GitHub (Mar 16, 2026):
What does "works somehow" mean?
@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.

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

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.
@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).
@maziggy commented on GitHub (Mar 16, 2026):
Wait for the daily image later today. It should already be fixed.
@RosdasHH commented on GitHub (Mar 16, 2026):
I just checked and can confirm that this issue is resolved in the latest dev branch.
@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:

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

On the printer side it's alright:

There may be other filaments with the same problem, but I didn't find any others in my random sample test.
@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:
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?
But for my understanding nothing should be displayed if it doesn't match the search text, right?
@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.
@RosdasHH commented on GitHub (Mar 18, 2026):
Yepp works now. Thank you
What about my second message? Is this supposed to happen?
@maziggy commented on GitHub (Mar 18, 2026):
What do you mean?
@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:
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:
I would expect no results to be displayed if there are no matches for the search query?
@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!
@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":
@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!