mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #784] [Bug]: Spool assignment on empty slot #522
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#522
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 22, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/784
Originally assigned to: @maziggy on GitHub.
Bug Description
I can assign a spool to an empty slot, but I can’t unassign it afterward. Once a spool is assigned, it becomes locked to that slot. Because of this, I’m unable to use the same spool in a different slot.
Expected Behavior
I would expect that spools can not be assigned to empty slots. And maybe not even be configurable when no spool is present?
Steps to Reproduce
Assign any spool to an empty slot.
Printer Model
Not printer-related
Bambuddy Version
v0.2.3b1-daily.20260321
Printer Firmware Version
.
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
No response
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Mar 22, 2026):
Sorry, cannot reproduce the problem.
If a spool is assigned, the button becomes "unassign" and if I click it, the spool is unassigned from slot properly.
@RosdasHH commented on GitHub (Mar 22, 2026):
Yes, but this does not apply to empty slots. By empty slots, I mean those where the AMS does not detect any physical spool. I am not referring to slots where a spool is physically loaded but simply has no spool assigned.
@maziggy commented on GitHub (Mar 22, 2026):
Yes, but it's the firmware that blocks it for empty slots. Even with BambuStudio this is not possible.
@RosdasHH commented on GitHub (Mar 22, 2026):
Yes thats why I think in bambuddy there shouldn't be an "assign spool" button for empty slots, because it is not possible via bambustudio either and wouldn't make sense to assign a spool to a physically not loaded slot. Because now I have a slot that is empty and has a spool assigned at the same time, and I can't unassign it:
@maziggy commented on GitHub (Mar 22, 2026):
Ahhhh, so why don't you say that. Interesting strategy: claim the button is not working, but want it to be removed :)
Now even me got it. Yes, you're right, should be removed in this state.
@RosdasHH commented on GitHub (Mar 22, 2026):
Yeah, sorry, when I said “I can’t unassign it afterward,” I didn’t mean the button doesn’t work. I meant I couldn’t unassign it because there is no unassign button. That’s how I ran into the issue, which is why I described it that way. Sorry for being unclear. So yes the assign button, probably also the configure button and maybe also the whole popup could be removed for empty slots.
@maziggy commented on GitHub (Mar 22, 2026):
Alll good!
@maziggy commented on GitHub (Mar 23, 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 23, 2026):
When I physically load a filament Bambuddy still says that the slot is empty.
Slicer:
Bambuddy:
I would expect that a slot is recognized as empty when there is no spool physically loaded and not when nothing is selected on this slot. In the Slicer I can configure Slot 2 and 3 because there is a spool loaded. But there I cannot configure slot 1 because "/" means no spool loaded. This is how I would expect it from Bambuddy too, because now I load a filament and cannot assign any spool because they are seen as empty. A workaround at the moment is to assign a color and filament type in the slicer so that the popup comes back in bambuddy.
So to conclude, there must be a difference between a not physically loaded spool and one that is loaded but not yet configured. The one that is physically loaded has to have the ability to be configured and a spool has to be assignable, but a not physically loaded spool should not have the ability.
@maziggy commented on GitHub (Mar 24, 2026):
This seems to be AMS Lite specific. Just checked and neither the AMS nor the AMS 2 Pro is reporting if a spool is inserted without filament inserted into the AMS feeder.
@RosdasHH commented on GitHub (Mar 24, 2026):
For me the problem is also with the AMS? In Bambuddy there are shown different icons for the empty slot and the not configured one. But when hovering, both say that they are empty slots.
@maziggy commented on GitHub (Mar 24, 2026):
Let me investigate more deeply.
@maziggy commented on GitHub (Mar 24, 2026):
Ahhh yes of course, because in case of a Bambu Lab spool the AMS reads the RFID tag. But that does not work with spools wihout tag.
@maziggy commented on GitHub (Mar 24, 2026):
Just successfully tested with my H2D. Please let me know if it works for you now.
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 24, 2026):
I just pulled the dev branch with your "Fix stale AMS slot data.." commit, but it doesn't work for me.
They are all shown as Empty when hovering and I can't assign anything. And yes you are right, I don't work with AMS RFID tags and manually select the wanted spool. I resetted the slots a few times, unloaded and loaded filaments but it doesn't change anything.
@RosdasHH commented on GitHub (Mar 24, 2026):
I wonder if the color of the numbers of the slots in the bambuddy ui show who set the value? White for bambuddy and black for a slicer?
@maziggy commented on GitHub (Mar 24, 2026):
That's not what I've said. But the tags are still on your spools, or do you removed them?
@RosdasHH commented on GitHub (Mar 24, 2026):
I mostly don't use Bambulab spools.
@RosdasHH commented on GitHub (Mar 24, 2026):
But is this a problem? Because the status if a spool is inserted is determined by the filament sensor, right? Otherwise it could not show me the difference between an empty slot and a loaded slot. And sorry, I should have told you that I don’t use Bambu spools but third-party ones. 😁
@maziggy commented on GitHub (Mar 24, 2026):
Spot on! and all good.
@RosdasHH commented on GitHub (Mar 25, 2026):
I looked into this a bit further and my problem is, that when a resetted slot (see the picture below), has a spool loaded, it shows it as empty and I can't configure it or assign a spool. But it works with the rfid tag scan, because it applies the fitting configuration, which brings back the buttons. But when the slot is not configured at all, which is the "?" in the slicer from previous messages there are no "assign spool" and "configure" buttons.
@RosdasHH commented on GitHub (Mar 26, 2026):
Hi, ich versuche es jetzt noch einmal auf Deutsch, da ich das Problem auf Englisch leider nicht richtig beschreiben konnte.
Das Problem ist, dass zwischen einem „physisch leeren Slot“ und einem „nicht konfigurierten Slot“ nicht unterschieden wird. Dadurch wird der Slot beim Zurücksetzen (über den Button im Configure Tab) auf „Empty Slot“ gesetzt, und kann daher anschließend nicht mehr konfiguriert werden. (Da ein leerer Slot richtigerweise nicht konfiguriert werden kann)
Es müsste also einen weiteren state geben, z. B. „Not Configured“, für den Fall, dass Filament physisch geladen ist, der Slot aber noch nicht konfiguriert wurde. In diesem state sollten sowohl der "Assign Spool“- als auch der "Configure“-Button verfügbar sein.
Auf diese Weise würde, wie im Slicer, zwischen physisch leeren und nicht konfigurierten Slots unterschieden werden. Man könnte dann nur noch die Slots die physisch belegt sind konfigurieren und es werden keine slots mehr fälschlicherweise als empty angezeigt.
Ich hoffe das war verständlicher als meine vorherigen Nachrichten. 😁
@maziggy commented on GitHub (Mar 27, 2026):
Moin :) Ich hatte es schon verstanden.
Das würde theoretisch nur für Bambu Lab Spulen funktionieren, aber nicht für andere. Der einzige Mechanismus zum erkennen einer Spule ist, der RFID Tag. Ich bin mir nicht sicher, ob wir das zuverlässig zum laufen bringen können.
Lass mich nochmal in Ruhe darüber nachdenken.