[Bug]: H2C nozzle selection not being preserved.

[mkoreen]

Product

Bambuddy

Area

Print Queue / scheduling

Bug Description

When sending prints to an H2C virtual printer via bambu studio and queuing the print, bambuddy does not seem to preserve the selected nozzle data from the print. After turning on debug mode, printer was on R4, I sent a print telling it to use R2, that first print actually did choose R2, but likely that was just luck, R1/R2 are both high flow nozzles (the rest aren't) since the print was high flow, it had to choose R1 or R2 and it chose R2.

Since this was unfortunately what I didn't want here to show the bug, I cancelled the print and tried again, this time selecting R1 in bambu studio, sent off the print, and it did not even try to switch nozzles, just used R2 again.

Having done this a few times now, it appears to just select the last nozzle in the set that matches the correct type (HF, Standard, or Nozzle size). Earlier I did a standard flow print where I told it to use R3 and it chose R4.

bambuddy-support-20260619-030722.zip

Please excuse my not using Host mode, we've had this discussion already.

Expected Behavior

I expected it to preserve the nozzle I chose in the slicer, (or alternatively let me actually set the nozzle in the "edit print" either in queue or archives.

Steps to Reproduce

Have H2C, have Virtual printer H2C, send print with bambu studio and choose which right nozzle.

Troubleshooting steps already taken

Obviously checked the forums, when I didn't see anything from searching, asked on discord, Martin asked me to create an issue.

Printer Model

H2C

Bambuddy Version

0.2.5b1 daily probably from a couple days ago.

SpoolBuddy Version

No response

Printer Firmware Version

01.02.00.00

Installation Method

Docker

Operating System

Linux (Other)

Support Package (.zip) and / or relevant logs

bambuddy-support-20260619-030722.zip

Screenshots

Additional Context

No response

Final checks

• I searched existing (open AND closed) issues and this bug hasn't already been reported or resolved
• I checked the Troubleshooting wiki and the relevant feature page for my issue
• I am using the latest version of Bambuddy (or the latest daily build)
• My printer is set to LAN Only mode
• My printer has Developer Mode enabled
• For any connection / printing / camera issue, I ran the in-app Connection Diagnostic and included the result above

[maziggy]

Thanks for the clear repro — the "last matching nozzle type" pattern you spotted matches what I'm seeing on Bambuddy's side.

To pin the fix down without a second revision, can you attach one of the sliced .gcode.3mf files from a test send — any plate, any nozzle pick — to this issue? In Bambu Studio: File → Export → Export Sliced File, or grab it from ~/.config/BambuStudio/ after a slice. I want the actual file with Metadata/slice_info.config so I can lock down the exact nozzle field BambuStudio writes for the H2C rack and match it byte-for-byte on Bambuddy's intake and dispatch paths.

[mkoreen]

TPU+Feed+Assist+Module+Housing+and+Frame+(1)_Indicator Guide - PLA Basic Jade White Recommended.gcode.3mf.zip

[maziggy]

Added a fix but not 100% sure if the field_names are correct.

Please try again with debug logging enabled.

Pull branch dev and re-build your image locally or wait for the next daily image.

[mkoreen]

I'd rather not build the dev version (there's a bug in portainer about building local images remotely), so I'll wait for the daily to update and try it once the fix has been pulled into the daily.

Thanks again. I will update when I test it.

[mkoreen]

Maybe as a future feature request, could make it so that if you edit a queued print or archived print (where you can change the filaments) maybe could also make it so you could select the nozzle used there. I realize that should probably be setup as a separate issue as a feature request, but I'm just sort of brainstorming. You already have drop downs for selecting different filaments and it shows L/R, just doesn't have a way to select R(1-6).

[maziggy]

Open a feature request.

[mkoreen]

Made a feature request, hopefully it makes sense. Need to figure out how to tell if today's "daily" has the new fix you setup.

[mkoreen]

Huh, despite seeing a newer image in docker hub tags, running docker pull is giving me yesterday's image, not todays. So I guess I'm waiting till tomorrow. It's pulling the arm64 image, just fyi. I dunno what is going on there.

[maziggy]

You are using tag daily?

[mkoreen]

Yup, the more I looked at it, it looked like the arm one wasn't updated last night? Not sure why.