1
0
Fork 0
mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #688] [Bug]: Schedule Print - Material Type issue with PA-CF / PAHT-CF / PA12-CF #455

Closed
opened 2026-05-07 00:10:25 +02:00 by BreizhHardware · 2 comments

Originally created by @aneopsy on GitHub (Mar 13, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/688

Originally assigned to: @maziggy on GitHub.

Bug Description

Schedule Print: Filament Type Mismatch & UI Issues
Setup: Sunlu PA12-CF filament configured in slicer.

Issue 1 – Filament type mismatch when scheduling to "Any H2S" printer
When on Schedule print modal:

Specific Printer tab: The filament matches correctly, PA-CF (Sunlu PA12-CF) in the slicer maps to PA12-CF (Sunlu PA12-CF) in the AMS.

Image

But once in queue and editing the job:
Image

Any H2S tab: The filament is displayed as PA-CF, but the dropdown is disabled, making it impossible to override it. The UI hints say that overriding should be possible, but the control is non-functional.

Image

The desired override would be to set the type to PA12-CF to match the AMS entry, Bambu Lab treats PA-CF and PA12-CF as equivalent on the printer side, but Bambuddy appears to differentiate them.
As a result, the scheduled print does not appear on the Printer page, likely because Bambuddy considers PA-CF ≠ PA12-CF. Since the dropdown is locked in the Schedule Print modal, there is currently no workaround.

Bonus: I tried to change on Bambuddy the AMS slot to:

  • Generic PA-CF but it's now considered as Generic PA
  • BBL PAHT-CF but doesn't match PA-CF of the file
  • Bambu PA-CF but it's now considered as Bambu PA-CF but show PA and doesn't match
  • SUNLU PA12-CF but doesn't match PA-CF of the file

Regression – Filament type override no longer available for scheduled prints

Issue 2 – Oversized click target on "Force color match" toggle (minor)
In the Schedule Print modal, clicking anywhere on the row, not just the checkbox or its label , toggles the Force color match option. The hit area should be scoped to the checkbox and the "Force color match" label only, to prevent accidental activation.

Image

Expected Behavior

Steps to Reproduce

Printer Model

X1 Carbon

Bambuddy Version

0.2.2b3

Printer Firmware Version

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package


Screenshots

No response

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 @aneopsy on GitHub (Mar 13, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/688 Originally assigned to: @maziggy on GitHub. ### Bug Description Schedule Print: Filament Type Mismatch & UI Issues Setup: Sunlu PA12-CF filament configured in slicer. Issue 1 – Filament type mismatch when scheduling to "Any H2S" printer When on Schedule print modal: Specific Printer tab: The filament matches correctly, PA-CF (Sunlu PA12-CF) in the slicer maps to PA12-CF (Sunlu PA12-CF) in the AMS. ✅ <img width="454" height="604" alt="Image" src="https://github.com/user-attachments/assets/3c23de91-2e15-40f6-9c86-7f76d66883aa" /> But once in queue and editing the job: <img width="872" height="1181" alt="Image" src="https://github.com/user-attachments/assets/706fc369-47fb-4447-a186-4e241fd56bc3" /> Any H2S tab: The filament is displayed as PA-CF, but the dropdown is disabled, making it impossible to override it. The UI hints say that overriding should be possible, but the control is non-functional. <img width="438" height="471" alt="Image" src="https://github.com/user-attachments/assets/e5e0786b-6fd9-4784-bad1-fff542684e51" /> The desired override would be to set the type to PA12-CF to match the AMS entry, Bambu Lab treats PA-CF and PA12-CF as equivalent on the printer side, but Bambuddy appears to differentiate them. As a result, the scheduled print does not appear on the Printer page, likely because Bambuddy considers PA-CF ≠ PA12-CF. Since the dropdown is locked in the Schedule Print modal, there is currently no workaround. Bonus: I tried to change on Bambuddy the AMS slot to: - Generic PA-CF but it's now considered as Generic PA - BBL PAHT-CF but doesn't match PA-CF of the file - Bambu PA-CF but it's now considered as Bambu PA-CF but show PA and doesn't match - SUNLU PA12-CF but doesn't match PA-CF of the file Regression – Filament type override no longer available for scheduled prints Issue 2 – Oversized click target on "Force color match" toggle (minor) In the Schedule Print modal, clicking anywhere on the row, not just the checkbox or its label , toggles the Force color match option. The hit area should be scoped to the checkbox and the "Force color match" label only, to prevent accidental activation. <img width="400" height="109" alt="Image" src="https://github.com/user-attachments/assets/09b72322-8dd8-4929-90f7-af8979aae005" /> ### Expected Behavior - ### Steps to Reproduce - ### Printer Model X1 Carbon ### Bambuddy Version 0.2.2b3 ### Printer Firmware Version - ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots _No response_ ### 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-07 00:10:25 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

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

Should be fixed in dev branch. PLease let me know. Thanks.

<!-- gh-comment-id:4054582758 --> @maziggy commented on GitHub (Mar 13, 2026): Should be fixed in dev branch. PLease let me know. Thanks.
Author
Owner

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

All good thx

<!-- gh-comment-id:4055030114 --> @aneopsy commented on GitHub (Mar 13, 2026): All good thx
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-maziggy-1#455
No description provided.