[Bug]: Wrong filament mapping – dual extruder (H2C) has only one active nozzle

[behrinml]

Bug Description

The H2C allows a nozzle size to be selected in the Vortek system that is not available in the left extruder—for example, 0.4 mm on the left and 0.2 mm on the right.

If a print is then started that exclusively uses the corresponding nozzle on the right extruder, a setup is created which erroneously claims that the nozzle in use is the one on the left. This occurs because only one extruder is detected, leading the system to assume the groupID must address that specific one.

Consequently, the filament assignment selected in the slicer cannot be chosen within the UI of Bambuddy.

Happens with docker and git clone, Linux and MacOS

Expected Behavior

The same filament mapping/slot should be possible between Bambuddy and Bambu Studio

Steps to Reproduce

1. Use different nozzles in the vortek system than in the left nozzle (e.g., only 0.2 in L but at least one 0.4 in R)
2. Sync the nozzles with Bambu Studio. You should receive Left Nozzle (0), Right Nozzle (1+) if you select 0.4 as nozzle size
3. Slice the model with 0.4 and select the corresponding filament from the AMS (I used AMS B)
4. Upload print to Bambuddy, press print and look into the filament mapping, this shows now only the option to select filament from AMS A

Printer Model

H2C

Bambuddy Version

0.2.2.1

Printer Firmware Version

01.01.05.00

Installation Method

Manual (git clone)

Operating System

macOS

Relevant Logs / Support Package

No response

Screenshots

Same 3mf

Current Bambuddy version. Only AMS A, wrong colors:

Fix (and correct color mapping)

Additional Context

Already fixed, if interested and assigned I happily create the corresponding pull request

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

[maziggy]

Why reinventing the wheel? Please open a pull request and note our rules in CONTRIBUTING.md.

Thanks!

[behrinml]

Thanks for assigning, I'm going to create the PR on during the weekend after additional tests.

What do you refer to with "the wheel"? Based on the Contributing.md:

"Every contribution starts with an issue. Before writing any code or opening a pull request:

Open a new issue or comment on an existing one describing what you'd like to work on
Wait for agreement — discuss the approach with a maintainer so we're aligned on scope and direction
Get assigned — once we agree, a maintainer will assign the issue to you
Then start coding — only open a PR for an issue that is assigned to you
No assigned issue = no PR. Pull requests without a corresponding assigned issue will be closed."

So I guess, I followed the rules?

[maziggy]

Yes, all is good.