mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #493] [Bug]: Filament assignments do not persist #314
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#314
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 @Keybored02 on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/493
Originally assigned to: @maziggy on GitHub.
Bug Description
Non-bambu filament assignments do not persist a container/machine restart when mapped to the external spools. The AMS and ext, spool assignments do not persist a container update.
Expected Behavior
All filaments remain assigned until changed by the user. Ideally, when connecting, if the filament profile of the AMS/spool tray isn't the same as the one saved on last connection, the spool is unassigned automatically.
Steps to Reproduce
Printer Model
H2C
Bambuddy Version
0.2.1b2
Printer Firmware Version
01.01.05.00
Installation Method
Docker
Operating System
Docker
Relevant Logs / Support Package
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 23, 2026):
As already assumed, state restore was missing for external slots.
Fixed in branch 0.2.1b3. Please let me know how it goes.