mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #887] [Bug]: AMS slot changes sometimes fail to apply until printer reconnect #609
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
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-maziggy-1#609
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 (Apr 4, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/887
Originally assigned to: @maziggy on GitHub.
Bug Description
Sometimes the printer stops receiving AMS changes until I reconnect it using the button. I logged a slot change when it wasn’t working, then reconnected and logged another change, which worked. Comparing the logs, I noticed that when it fails, the affected printer’s developer_mode is set to null; when it works, it’s true. In this case, it happened on the A1 Mini, but I think I have seen it on the P1S as well.
When it doesn’t work, I can select a spool and the spool name updates correctly in Bambuddy, but the filament is not applied in the slicer, and the profile and K-factor are not updated in Bambuddy either.
Expected Behavior
I would expect that I can always communicate with the printer via. Bambuddy.
Steps to Reproduce
Can't really tell, it just randomly happens sometimes.
Printer Model
A1 Mini
Bambuddy Version
v0.2.3b1 daily
Printer Firmware Version
01.07.02.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Not working:
bambuddy-support-20260404-120805.zip
Working:
bambuddy-support-20260404-120944.zip
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Apr 4, 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.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@RosdasHH commented on GitHub (Apr 5, 2026):
Unfortunately the issue still persist. However the developer mode isn't set to null anymore.
Here is todays logfile:
bambuddy.log
I turned on debug logging as soon as I had the issue, assigned a spool which wasn't applied, I reconnected and was able to apply again. All that is in the log file from "2026-04-05 19:30:52,800" until the end. I hope this helps to find the problem.
@maziggy commented on GitHub (Apr 7, 2026):
Hopefully fixed in branch dev and available with the next release or daily build. Please test and let mw know how it goes.
@maziggy commented on GitHub (Apr 13, 2026):
?
@RosdasHH commented on GitHub (Apr 13, 2026):
I didn't had the problem again since your latest fix. I think it is solved, thank you!
@RosdasHH commented on GitHub (Apr 16, 2026):
Hi, unfortunately I've ran into this issue again.. A Force Refresh didn't help, I had to reconnect. The Log file contains multiple spool changes (which didn’t make it to the printer), 2x Force refreshes and a reconnect. I hope this helps
bambuddy-support-20260416-234726.zip
@RosdasHH commented on GitHub (Apr 16, 2026):
I just saw that both printers have had this problem right now. They were turned on the whole day without a single print, just a few spool changes in the afternoon and in the evening the problem occured again.
@maziggy commented on GitHub (Apr 17, 2026):
Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works now.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!