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

[GH-ISSUE #300] [Feature]: H2C Support #184

Closed
opened 2026-05-07 00:07:11 +02:00 by BreizhHardware · 81 comments

Originally created by @maziggy on GitHub (Feb 8, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/300

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Implement H2C support.

Proposed Solution

https://www.diffchecker.com/bcmZ1INm/

Alternatives Considered

No response

Feature Category

Other

Priority

Would improve my workflow

Mockups or Examples

No response

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @maziggy on GitHub (Feb 8, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/300 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Implement H2C support. ### Proposed Solution https://www.diffchecker.com/bcmZ1INm/ ### Alternatives Considered _No response_ ### Feature Category Other ### Priority Would improve my workflow ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-07 00:07:11 +02:00
Author
Owner

@JasonSwindle commented on GitHub (Feb 8, 2026):

I have an H2C and I'm happy to help test this.

<!-- gh-comment-id:3867792346 --> @JasonSwindle commented on GitHub (Feb 8, 2026): I have an H2C and I'm happy to help test this.
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 9, 2026):

It seems to pull the data for the H2C, just limited on current controls.

Image
<!-- gh-comment-id:3869217070 --> @jjjonesjr33 commented on GitHub (Feb 9, 2026): It seems to pull the data for the H2C, just limited on current controls. <img width="765" height="794" alt="Image" src="https://github.com/user-attachments/assets/967badd8-46d2-4060-a99a-ff74b1c3e842" />
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

First shot available in branch 0.1.9b. Could you please give it a try? I'm also interested seeing how the printer card looks like with the newly added nozle rack.

<!-- gh-comment-id:3870099083 --> @maziggy commented on GitHub (Feb 9, 2026): First shot available in branch 0.1.9b. Could you please give it a try? I'm also interested seeing how the printer card looks like with the newly added nozle rack.
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 9, 2026):

Nozzle rack shows, but does not show type of nozzle or if they are occupied.
Image

bambuddy-support-20260209-030436.zip

<!-- gh-comment-id:3870331684 --> @jjjonesjr33 commented on GitHub (Feb 9, 2026): Nozzle rack shows, but does not show type of nozzle or if they are occupied. <img width="747" height="736" alt="Image" src="https://github.com/user-attachments/assets/ca0f79ff-35c5-4eae-9716-8149b4acfc39" /> [bambuddy-support-20260209-030436.zip](https://github.com/user-attachments/files/25178631/bambuddy-support-20260209-030436.zip)
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 9, 2026):

Nozzles show for a split sec and then they are gone, I seem to be able to trigger them showing when I switch the size from M to L? Sometimes they stay for a min, and then gone the next.

Image
<!-- gh-comment-id:3870351241 --> @jjjonesjr33 commented on GitHub (Feb 9, 2026): Nozzles show for a split sec and then they are gone, I seem to be able to trigger them showing when I switch the size from M to L? Sometimes they stay for a min, and then gone the next. <img width="750" height="745" alt="Image" src="https://github.com/user-attachments/assets/0bb4b57c-bf39-4476-89c7-2988c4667bf3" />
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 9, 2026):

One thing I just noticed with the nozzles as well, its showing all 6 slots filled ... there's only 5 filled in mine and the one in use.
I would almost think it would show the nozzle size where the L and R are as well ... No?

Image
<!-- gh-comment-id:3870431537 --> @jjjonesjr33 commented on GitHub (Feb 9, 2026): One thing I just noticed with the nozzles as well, its showing all 6 slots filled ... there's only 5 filled in mine and the one in use. I would almost think it would show the nozzle size where the L and R are as well ... No? <img width="156" height="80" alt="Image" src="https://github.com/user-attachments/assets/9a908e52-9a41-457e-b7ee-9d9b220e3376" />
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

The payload dump was already done before debug logging started. Don't see any nozle related logs. Please enable debug logging, force some rack nozzle actions and then download the support package.

<!-- gh-comment-id:3870467594 --> @maziggy commented on GitHub (Feb 9, 2026): The payload dump was already done before debug logging started. Don't see any nozle related logs. Please enable debug logging, force some rack nozzle actions and then download the support package.
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

Available metrics:

  • Nozzle type code (HS = Hardened Steel, SS = Stainless Steel
  • Nozzle diameter in mm
  • Status (0=docked, likely 1=mounted/active)
  • Wear percentage
  • Max temperature rating (°C). 0 = not set, 350 = rated to 350°C
  • Nozzle serial number
  • Current filament color (RGBA hex). "00000000" = no filament
  • Bambu filament ID. Empty = no filament loaded

Yes, we could move the nozle diameter to the l/r card. What do you want to see on the new rack card?

<!-- gh-comment-id:3870490227 --> @maziggy commented on GitHub (Feb 9, 2026): Available metrics: - Nozzle type code (HS = Hardened Steel, SS = Stainless Steel - Nozzle diameter in mm - Status (0=docked, likely 1=mounted/active) - Wear percentage - Max temperature rating (°C). 0 = not set, 350 = rated to 350°C - Nozzle serial number - Current filament color (RGBA hex). "00000000" = no filament - Bambu filament ID. Empty = no filament loaded Yes, we could move the nozle diameter to the l/r card. What do you want to see on the new rack card?
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

What's about coloring the slots with assigned filament color (if available), indicating the active nozle and showing remaining details on hover?

<!-- gh-comment-id:3870631223 --> @maziggy commented on GitHub (Feb 9, 2026): What's about coloring the slots with assigned filament color (if available), indicating the active nozle and showing remaining details on hover?
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 9, 2026):

These would be really handy if the extra details were available via a hover-over on each nozzle or nozzle rack icon. That said, I realize that might be difficult given how much information is already being displayed. I do like what you are suggesting:

Available metrics:

  • Nozzle type code (HS = Hardened Steel, SS = Stainless Steel)
  • Nozzle diameter (mm)
  • Status (0 = docked, likely 1 = mounted/active)
  • Wear percentage
  • Max temperature rating (°C) — 0 = not set, 350 = rated to 350 °C
  • Nozzle serial number
  • Current filament color (RGBA hex) — 00000000 = no filament

Moving the nozzle diameter to the L/R card makes sense. For the nozzles that are in use. For the rack card, I’d expect it to mirror the nozzle card behavior: for example, showing the currently installed nozzle (like a 0.4 mm), with additional stats available on hover.

Alternatively, instead of relying on hover-over, the nozzle card itself could be expanded to display more of this information directly.

Longer-term, it would be really interesting to track nozzle usage hours. If the serial number can be read and correlated with when a nozzle is mounted (e.g., in the right nozzle slot), that data could be used to estimate wear over time.

Filament color being shown on the nozzle (similar to how it’s displayed on the H2C) isn’t really necessary, unless someone is actively tracking which color is loaded in which nozzle using this software.

Also, I’ll need to grab another payload for you in the morning—my current print still has about 7 hours left to go.

<!-- gh-comment-id:3870704118 --> @jjjonesjr33 commented on GitHub (Feb 9, 2026): These would be really handy if the extra details were available via a hover-over on each nozzle or nozzle rack icon. That said, I realize that might be difficult given how much information is already being displayed. I do like what you are suggesting: Available metrics: - Nozzle type code (HS = Hardened Steel, SS = Stainless Steel) - Nozzle diameter (mm) - Status (0 = docked, likely 1 = mounted/active) - Wear percentage - Max temperature rating (°C) — 0 = not set, 350 = rated to 350 °C - Nozzle serial number - Current filament color (RGBA hex) — `00000000` = no filament Moving the nozzle diameter to the L/R card makes sense. For the nozzles that are in use. For the rack card, I’d expect it to mirror the nozzle card behavior: for example, showing the currently installed nozzle (like a 0.4 mm), with additional stats available on hover. Alternatively, instead of relying on hover-over, the nozzle card itself could be expanded to display more of this information directly. Longer-term, it would be really interesting to track nozzle usage hours. If the serial number can be read and correlated with when a nozzle is mounted (e.g., in the right nozzle slot), that data could be used to estimate wear over time. Filament color being shown on the nozzle (similar to how it’s displayed on the H2C) isn’t really necessary, unless someone is actively tracking which color is loaded in which nozzle using this software. Also, I’ll need to grab another payload for you in the morning—my current print still has about 7 hours left to go.
Author
Owner

@Keybored02 commented on GitHub (Feb 9, 2026):

Same behavior as @jjjonesjr33 . Juts for reference, 1-6 on mine are 0.2 0.4 0.4 0.4 x 0.6

bambuddy-support-20260209-144644.zip

Moving the nozzle diameter to the L/R card makes sense. For the nozzles that are in use. For the rack card, I’d expect it to mirror the nozzle card behavior: for example, showing the currently installed nozzle (like a 0.4 mm), with additional stats available on hover.

Second this. Last material used per nozzle on hover would be great too.

<!-- gh-comment-id:3871830575 --> @Keybored02 commented on GitHub (Feb 9, 2026): Same behavior as @jjjonesjr33 . Juts for reference, 1-6 on mine are 0.2 0.4 0.4 0.4 x 0.6 [bambuddy-support-20260209-144644.zip](https://github.com/user-attachments/files/25184713/bambuddy-support-20260209-144644.zip) > Moving the nozzle diameter to the L/R card makes sense. For the nozzles that are in use. For the rack card, I’d expect it to mirror the nozzle card behavior: for example, showing the currently installed nozzle (like a 0.4 mm), with additional stats available on hover. Second this. Last material used per nozzle on hover would be great too.
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

6661bbf866

<!-- gh-comment-id:3871966747 --> @maziggy commented on GitHub (Feb 9, 2026): 6661bbf86682a6abc759a4d3cc2097d114dfd2ed
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

Please pull branch 0.1.9b and try again.

<!-- gh-comment-id:3871982637 --> @maziggy commented on GitHub (Feb 9, 2026): Please pull branch 0.1.9b and try again.
Author
Owner

@Keybored02 commented on GitHub (Feb 9, 2026):

Much better, it does not go blank anymore. Still, 6 nozzles appear as docked, while only 5 actually are. Ad the 0.6 one is missing. My hypothesis is that it's reading the wrong IDs and excluding the last rack position. Possibly reading L and R first as IDs 0 and 1? And then there are 16-17-18 (? empty)-19-20-21 for the rack. Which would mean that its assigning it as rows 1-3-5-2-4-6.

<!-- gh-comment-id:3872083267 --> @Keybored02 commented on GitHub (Feb 9, 2026): Much better, it does not go blank anymore. Still, 6 nozzles appear as docked, while only 5 actually are. Ad the 0.6 one is missing. My hypothesis is that it's reading the wrong IDs and excluding the last rack position. Possibly reading L and R first as IDs 0 and 1? And then there are 16-17-18 (? empty)-19-20-21 for the rack. Which would mean that its assigning it as rows 1-3-5-2-4-6.
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

Can you post a screenshot?

<!-- gh-comment-id:3872129328 --> @maziggy commented on GitHub (Feb 9, 2026): Can you post a screenshot?
Author
Owner

@Keybored02 commented on GitHub (Feb 9, 2026):

Image
<!-- gh-comment-id:3872134129 --> @Keybored02 commented on GitHub (Feb 9, 2026): <img width="111" height="103" alt="Image" src="https://github.com/user-attachments/assets/493eebc9-f749-414c-ad48-aaeae823b830" />
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

A little more please. Would like to see if the cards fits visually to the printer card.

<!-- gh-comment-id:3872163904 --> @maziggy commented on GitHub (Feb 9, 2026): A little more please. Would like to see if the cards fits visually to the printer card.
Author
Owner

@Keybored02 commented on GitHub (Feb 9, 2026):

Image
<!-- gh-comment-id:3872168161 --> @Keybored02 commented on GitHub (Feb 9, 2026): <img width="1565" height="928" alt="Image" src="https://github.com/user-attachments/assets/679e74a7-2e48-4a08-b7ee-b69f5a5280ac" />
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

Thanks. At least the alignment is now correct ;)

<!-- gh-comment-id:3872179878 --> @maziggy commented on GitHub (Feb 9, 2026): Thanks. At least the alignment is now correct ;)
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

What version do you guys like?

Image
<!-- gh-comment-id:3872724661 --> @maziggy commented on GitHub (Feb 9, 2026): What version do you guys like? <img width="723" height="1029" alt="Image" src="https://github.com/user-attachments/assets/1165893c-7d15-4d48-87a1-3391e7ee0fd8" />
Author
Owner

@Keybored02 commented on GitHub (Feb 9, 2026):

Current isn't bad, before and circular do not fit the theme very well. Nozzle tip and compact are ok. I would either try to mimic the BL studio one, which differentiates between Row A and B, or just fit the theme and keep the text to a minimum until you hover.

<!-- gh-comment-id:3872911232 --> @Keybored02 commented on GitHub (Feb 9, 2026): Current isn't bad, before and circular do not fit the theme very well. Nozzle tip and compact are ok. I would either try to mimic the BL studio one, which differentiates between Row A and B, or just fit the theme and keep the text to a minimum until you hover.
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 9, 2026):

I like the look of both

  • After Current Code
  • Option C - Compact

But I feel like Option C has a cleaner look to it.

<!-- gh-comment-id:3873169087 --> @jjjonesjr33 commented on GitHub (Feb 9, 2026): I like the look of both - After Current Code - Option C - Compact But I feel like Option C has a cleaner look to it.
Author
Owner

@maziggy commented on GitHub (Feb 9, 2026):

Never saw that im Bambu Studio. Show me please.

<!-- gh-comment-id:3873309805 --> @maziggy commented on GitHub (Feb 9, 2026): Never saw that im Bambu Studio. Show me please.
Author
Owner

@Keybored02 commented on GitHub (Feb 9, 2026):

Here's the wiki page https://public-cdn.bblmw.com/wiki/new/h2c/manual/bambu-studio-operation/image-13.png

<!-- gh-comment-id:3873351557 --> @Keybored02 commented on GitHub (Feb 9, 2026): Here's the wiki page https://public-cdn.bblmw.com/wiki/new/h2c/manual/bambu-studio-operation/image-13.png
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

I also prefer option C.

<!-- gh-comment-id:3875872886 --> @maziggy commented on GitHub (Feb 10, 2026): I also prefer option C.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Please try again with branch 0.1.9b and send me screenshots (normal and hover).

<!-- gh-comment-id:3875928757 --> @maziggy commented on GitHub (Feb 10, 2026): Please try again with branch 0.1.9b and send me screenshots (normal and hover).
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

docker pull ghcr.io/maziggy/bambuddy:0.1.9b

<!-- gh-comment-id:3876177586 --> @maziggy commented on GitHub (Feb 10, 2026): docker pull ghcr.io/maziggy/bambuddy:0.1.9b
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

That looks clean.
Image
I like how that’s done—any chance we could do the same thing for the L/R nozzle and have it show which nozzle is installed there too?

Image

You could almost remove the status entirely, since I’d always expect them to be docked anyway—especially because it’s only showing the five that are actually in the nozzle rack. You could potentially replace that with more useful details, like:

  • Wear percentage
  • Nozzle serial number
Image

Also, just adding this here as a follow-up to #311 having an “up to date” checkmark ( or the version number in green) for the device, would be awesome.

<!-- gh-comment-id:3876277129 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): That looks clean. <img width="305" height="83" alt="Image" src="https://github.com/user-attachments/assets/c3dbabfd-3735-4d75-940d-920fc37e4ceb" /> I like how that’s done—any chance we could do the same thing for the L/R nozzle and have it show which nozzle is installed there too? <img width="748" height="658" alt="Image" src="https://github.com/user-attachments/assets/4d11e5e3-cce9-4f08-8e76-09991492f806" /> You could almost remove the status entirely, since I’d always expect them to be docked anyway—especially because it’s only showing the five that are actually in the nozzle rack. You could potentially replace that with more useful details, like: - Wear percentage - Nozzle serial number <img width="744" height="648" alt="Image" src="https://github.com/user-attachments/assets/c1b08a36-f2e7-4537-85ed-f3fcf2714eae" /> Also, just adding this here as a follow-up to [#311](https://github.com/maziggy/bambuddy/issues/311) having an “up to date” checkmark ( or the version number in green) for the device, would be awesome.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

What's about the nozzle rack metrics? Does the rack card show correct values or do we need to look at the H2C MQTT stream more detailed?

<!-- gh-comment-id:3876385760 --> @maziggy commented on GitHub (Feb 10, 2026): What's about the nozzle rack metrics? Does the rack card show correct values or do we need to look at the H2C MQTT stream more detailed?
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

Yeah, it’s showing correctly right now—everything is hardened steel, and all of the currently installed ones are 0.4 mm. I can try swapping in the 0.2 mm and 0.6 mm nozzles tomorrow morning after this print and see if that updates properly.

<!-- gh-comment-id:3876487653 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): Yeah, it’s showing correctly right now—everything is hardened steel, and all of the currently installed ones are 0.4 mm. I can try swapping in the 0.2 mm and 0.6 mm nozzles tomorrow morning after this print and see if that updates properly.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Wait....why does it only show 5 nozzles in rack?

<!-- gh-comment-id:3876572922 --> @maziggy commented on GitHub (Feb 10, 2026): Wait....why does it only show 5 nozzles in rack?
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

Cause you can only have 5 in at a time so it can take the active one it has and docks it to switch to another nozzle.

<!-- gh-comment-id:3876582323 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): Cause you can only have 5 in at a time so it can take the active one it has and docks it to switch to another nozzle.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Ahhh....got it.

Nozzle wear and serial was added to hover modal.

<!-- gh-comment-id:3876604090 --> @maziggy commented on GitHub (Feb 10, 2026): Ahhh....got it. Nozzle wear and serial was added to hover modal.
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Yeah, but you can actually rack all 6 including the one on the head. Which means that the UI should have 6 positions, one of which is empty most of the time.

<!-- gh-comment-id:3876608162 --> @Keybored02 commented on GitHub (Feb 10, 2026): Yeah, but you can actually rack all 6 including the one on the head. Which means that the UI should have 6 positions, one of which is empty most of the time.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

That's what I expected. Let me check the code again once I finished my current task.

<!-- gh-comment-id:3876616819 --> @maziggy commented on GitHub (Feb 10, 2026): That's what I expected. Let me check the code again once I finished my current task.
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

When you look in Bambu Suite it shows that 1 of the nozzle racks spots is empty so thats why I am assuming why it didn't show.

Image
<!-- gh-comment-id:3876636356 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): When you look in Bambu Suite it shows that 1 of the nozzle racks spots is empty so thats why I am assuming why it didn't show. <img width="299" height="588" alt="Image" src="https://github.com/user-attachments/assets/ad660c0f-1fb9-4611-8034-659ff89bff52" />
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

Actually key thing I just noticed to, it doesn't show if its a standard nozzle or a high flow nozzle in bambuddy, that might need to be added for the hover over.

I am assuning HS is just Hardened Steel

Image
<!-- gh-comment-id:3876645683 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): Actually key thing I just noticed to, it doesn't show if its a standard nozzle or a high flow nozzle in bambuddy, that might need to be added for the hover over. I am assuning HS is just Hardened Steel <img width="251" height="136" alt="Image" src="https://github.com/user-attachments/assets/a36fe0dd-8c5a-4da3-9bf7-d20f3981744b" />
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Yes, during normal operations there must be an empty slot for swapping out nozzles. But you can definitely occupy all 6 during initialization or just by stowing the 6th.

Regarding nozzles, the High Flow variant is not present in the payloads i sent, but should be as follows: HH is high flow, HS is normal, "00": "stainless_steel", "01": "hardened_steel", "05": "tungsten_carbide".

github.com/greghesp/ha-bambulab@e5fe603863/custom_components/bambu_lab/models.py (L4)

<!-- gh-comment-id:3876687547 --> @Keybored02 commented on GitHub (Feb 10, 2026): Yes, during normal operations there must be an empty slot for swapping out nozzles. But you can definitely occupy all 6 during initialization or just by stowing the 6th. Regarding nozzles, the High Flow variant is not present in the payloads i sent, but should be as follows: HH is high flow, HS is normal, "00": "stainless_steel", "01": "hardened_steel", "05": "tungsten_carbide". https://github.com/greghesp/ha-bambulab/blob/e5fe6038639198545299365b5556e269ac290c4d/custom_components/bambu_lab/models.py#L4
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Also, if hover could show last used material it would be neat. I'm sure there's already a conversion table somewhere but just in case https://github.com/Bambu-Research-Group/RFID-Tag-Guide/issues/42

<!-- gh-comment-id:3876713375 --> @Keybored02 commented on GitHub (Feb 10, 2026): Also, if hover could show last used material it would be neat. I'm sure there's already a conversion table somewhere but just in case https://github.com/Bambu-Research-Group/RFID-Tag-Guide/issues/42
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

We already have it all. Just need to add it to the hover card.

<!-- gh-comment-id:3876717315 --> @maziggy commented on GitHub (Feb 10, 2026): We already have it all. Just need to add it to the hover card.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

docker pull ghcr.io/maziggy/bambuddy:0.1.9b2

<!-- gh-comment-id:3876781659 --> @maziggy commented on GitHub (Feb 10, 2026): docker pull ghcr.io/maziggy/bambuddy:0.1.9b2
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Image

Nice! Though I would distinguish the fist two (IDs 0-1) which are L/R from the rest. Maybe no "Docked" status for them and instead something like "On Head" or "Installed". Or moving them to somewhere else? The 1-6 rack position should still have an empty slot (or more, if you have less than 6 nozzles) matching the missing ID. So if I'm missing 5, the 5th should be grey and empty? Materials aren't there on hover, but they might not be in my payload anyway, let me check.

<!-- gh-comment-id:3876867632 --> @Keybored02 commented on GitHub (Feb 10, 2026): <img width="795" height="826" alt="Image" src="https://github.com/user-attachments/assets/72b55ee7-705d-4c82-9eef-bcec658f69c6" /> Nice! Though I would distinguish the fist two (IDs 0-1) which are L/R from the rest. Maybe no "Docked" status for them and instead something like "On Head" or "Installed". Or moving them to somewhere else? The 1-6 rack position should still have an empty slot (or more, if you have less than 6 nozzles) matching the missing ID. So if I'm missing 5, the 5th should be grey and empty? Materials aren't there on hover, but they might not be in my payload anyway, let me check.
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

Nice, I like that change! Although the only problem is it thinks they are all docked, but I clearly have one in use...

version 0.1.9b2 >>>> Can confirm issues is still there on version 0.1.9b3

Image
<!-- gh-comment-id:3876883064 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): Nice, I like that change! Although the only problem is it thinks they are all docked, but I clearly have one in use... version 0.1.9b2 >>>> Can confirm issues is still there on version 0.1.9b3 <img width="326" height="189" alt="Image" src="https://github.com/user-attachments/assets/fd280559-8b90-4be4-b32d-797c759bcc2c" />
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Docked in BL terms does not distinguish from head or rack, it just means that it's occupying that position. The first two from the left are the L/R, then the 5 in the rack. The missing 6th is not included in the payload.

<!-- gh-comment-id:3876899187 --> @Keybored02 commented on GitHub (Feb 10, 2026): Docked in BL terms does not distinguish from head or rack, it just means that it's occupying that position. The first two from the left are the L/R, then the 5 in the rack. The missing 6th is not included in the payload.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

And I see 7 nozzles?!

<!-- gh-comment-id:3876927528 --> @maziggy commented on GitHub (Feb 10, 2026): And I see 7 nozzles?!
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Yep, it's still including L/R, it's not ignoring ID 0 and 1.

<!-- gh-comment-id:3876946237 --> @Keybored02 commented on GitHub (Feb 10, 2026): Yep, it's still including L/R, it's not ignoring ID 0 and 1.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Ahh right, the left nozzle.

<!-- gh-comment-id:3876951802 --> @maziggy commented on GitHub (Feb 10, 2026): Ahh right, the left nozzle.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Wait....why ignoring 0 and 1? Just 0. Or am I still too tired?

<!-- gh-comment-id:3876957341 --> @maziggy commented on GitHub (Feb 10, 2026): Wait....why ignoring 0 and 1? Just 0. Or am I still too tired?
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

You may need some sleep ... 😫 speaking of I need to head to bed myself. If you need something from me ping me and I'll get to it when I wake up 😄

<!-- gh-comment-id:3876971116 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): You may need some sleep ... 😫 speaking of I need to head to bed myself. If you need something from me ping me and I'll get to it when I wake up 😄
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Yep, might be the time to slow down. 0 and 1 are L and R, 16-21 are racked. I would go as far as saying that in the rack section only the latter should appear. We can think of L/R later, maybe a rework of their card and more info on hover?

You got it right in 53e13ec, only
IDs over 2 where considered.

<!-- gh-comment-id:3876977040 --> @Keybored02 commented on GitHub (Feb 10, 2026): Yep, might be the time to slow down. 0 and 1 are L and R, 16-21 are racked. I would go as far as saying that in the rack section only the latter should appear. We can think of L/R later, maybe a rework of their card and more info on hover? You got it right in [53e13ec](https://github.com/maziggy/bambuddy/commit/53e13ecbd2e1c11305bfa608e0306d80debb2859), only IDs over 2 where considered.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

I still don't get it.

Left nozzle is static. Right nozzle has attached one nozzle of the rack. So I have a total of 7 nozles and the rack should show 6 nozles (incl. one currently empty in rack, because it's attached to right).

<!-- gh-comment-id:3877058735 --> @maziggy commented on GitHub (Feb 10, 2026): I still don't get it. Left nozzle is static. Right nozzle has attached one nozzle of the rack. So I have a total of 7 nozles and the rack should show 6 nozles (incl. one currently empty in rack, because it's attached to right).
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Or does the rack have 7 "slots" and only 6 have a nozzle?

<!-- gh-comment-id:3877061364 --> @maziggy commented on GitHub (Feb 10, 2026): Or does the rack have 7 "slots" and only 6 have a nozzle?
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

The first is right. The data the H2C passes lists all the nozzles it can sense, so the L/R on the head, plus the ones on the rack. 7 total.

<!-- gh-comment-id:3877082984 --> @Keybored02 commented on GitHub (Feb 10, 2026): The first is right. The data the H2C passes lists all the nozzles it can sense, so the L/R on the head, plus the ones on the rack. 7 total.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Exactly and therefore the nozzle rack has to show 6 and not 7 (as on your latest screenshot).

<!-- gh-comment-id:3877102915 --> @maziggy commented on GitHub (Feb 10, 2026): Exactly and therefore the nozzle rack has to show 6 and not 7 (as on your latest screenshot).
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Yep. The L/R nozzle card could be reworked too for both the H2D and H2C. Want me to look into that? Not super strong with UIs but should be simple enough

<!-- gh-comment-id:3877113509 --> @Keybored02 commented on GitHub (Feb 10, 2026): Yep. The L/R nozzle card could be reworked too for both the H2D and H2C. Want me to look into that? Not super strong with UIs but should be simple enough
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

What do you want to change for the L/R nozle card?

<!-- gh-comment-id:3877132930 --> @maziggy commented on GitHub (Feb 10, 2026): What do you want to change for the L/R nozle card?
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Got it. I'm currently working on it anyway. Will add it to L/R card.

<!-- gh-comment-id:3877155498 --> @maziggy commented on GitHub (Feb 10, 2026): Got it. I'm currently working on it anyway. Will add it to L/R card.
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Same as now, just a bit different:

Image
<!-- gh-comment-id:3877158302 --> @Keybored02 commented on GitHub (Feb 10, 2026): Same as now, just a bit different: <img width="216" height="270" alt="Image" src="https://github.com/user-attachments/assets/ba07c23c-a568-41bb-b04a-cde379a34e5c" />
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Side note: the AMS temp/hum graphs are really nice. Plans on implementing them for the rest of the temp sensors?

<!-- gh-comment-id:3877163821 --> @Keybored02 commented on GitHub (Feb 10, 2026): Side note: the AMS temp/hum graphs are really nice. Plans on implementing them for the rest of the temp sensors?
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Not planned so far. If you wnt to have more stats you could use the Prometheus metrics export.

<!-- gh-comment-id:3877171137 --> @maziggy commented on GitHub (Feb 10, 2026): Not planned so far. If you wnt to have more stats you could use the Prometheus metrics export.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

docker pull ghcr.io/maziggy/bambuddy:0.1.9b4

Image Image
<!-- gh-comment-id:3877361628 --> @maziggy commented on GitHub (Feb 10, 2026): docker pull ghcr.io/maziggy/bambuddy:0.1.9b4 <img width="241" height="304" alt="Image" src="https://github.com/user-attachments/assets/8acb3290-4dfb-4e4f-b208-6e0ad5a61cad" /> <img width="396" height="250" alt="Image" src="https://github.com/user-attachments/assets/475ff245-6fab-4084-81af-a37d3189a250" />
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Image

Medium cards breaks it, but good job!

Image

The dual nozzle card is correct.

The rack is showing the wrong slot as empty, should be 5 instead of 6. Regarding the materials, I'm not sure why they rean't showing still. Code looks ok - maybe it's the ams tray reference?

<!-- gh-comment-id:3877411494 --> @Keybored02 commented on GitHub (Feb 10, 2026): <img width="642" height="478" alt="Image" src="https://github.com/user-attachments/assets/74568c55-0d5f-4c8a-a809-105db80e4d95" /> Medium cards breaks it, but good job! <img width="726" height="442" alt="Image" src="https://github.com/user-attachments/assets/26da970b-efa7-44f6-a2b6-d8af081c1df9" /> The dual nozzle card is correct. The rack is showing the wrong slot as empty, should be 5 instead of 6. Regarding the materials, I'm not sure why they rean't showing still. Code looks ok - maybe it's the ams tray reference?
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Hopefully that's it.

docker pull ghcr.io/maziggy/bambuddy:0.1.9b5

<!-- gh-comment-id:3877495100 --> @maziggy commented on GitHub (Feb 10, 2026): Hopefully that's it. docker pull ghcr.io/maziggy/bambuddy:0.1.9b5
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Works as intended. The filament name is still the shorthand (e.g. GFU99).

Migth want to consider adding the H2C machine image (still using the H2D).

<!-- gh-comment-id:3877709255 --> @Keybored02 commented on GitHub (Feb 10, 2026): Works as intended. The filament name is still the shorthand (e.g. GFU99). Migth want to consider adding the H2C machine image (still using the H2D).
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Oh yes, forgot to map the filament id.

<!-- gh-comment-id:3877732813 --> @maziggy commented on GitHub (Feb 10, 2026): Oh yes, forgot to map the filament id.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Here we go....

docker pull ghcr.io/maziggy/bambuddy:0.1.9b6

Can you please send me screenshots of the overall look and the nozzle rack modal? Thx.

<!-- gh-comment-id:3877902551 --> @maziggy commented on GitHub (Feb 10, 2026): Here we go.... docker pull ghcr.io/maziggy/bambuddy:0.1.9b6 Can you please send me screenshots of the overall look and the nozzle rack modal? Thx.
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Image

Here you go. Unfortunately, still using the abbreviations instead of the material name

<!-- gh-comment-id:3877937737 --> @Keybored02 commented on GitHub (Feb 10, 2026): <img width="767" height="822" alt="Image" src="https://github.com/user-attachments/assets/c9f71da6-c54c-4b2e-be21-5fc993f2e5bf" /> Here you go. Unfortunately, still using the abbreviations instead of the material name
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

Can you check logs for

  1. get_filament_info — shows what filament IDs are sent to the cloud lookup, and whether the nozzle rack's filament_id values are included
  2. Failed to get cloud preset — if the cloud API can't resolve a nozzle rack filament ID
  3. Nozzle info — the raw MQTT nozzle data (logged once per printer on first message)
<!-- gh-comment-id:3877982557 --> @maziggy commented on GitHub (Feb 10, 2026): Can you check logs for 1. get_filament_info — shows what filament IDs are sent to the cloud lookup, and whether the nozzle rack's filament_id values are included 2. Failed to get cloud preset — if the cloud API can't resolve a nozzle rack filament ID 3. Nozzle info — the raw MQTT nozzle data (logged once per printer on first message)
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Sure, here's a log anyway.

bambuddy-support-20260210-151901.zip

<!-- gh-comment-id:3877989662 --> @Keybored02 commented on GitHub (Feb 10, 2026): Sure, here's a log anyway. [bambuddy-support-20260210-151901.zip](https://github.com/user-attachments/files/25213026/bambuddy-support-20260210-151901.zip)
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

get_filament_info reports correctly but Failed to get cloud preset is present for all materials.

<!-- gh-comment-id:3878029205 --> @Keybored02 commented on GitHub (Feb 10, 2026): get_filament_info reports correctly but Failed to get cloud preset is present for all materials.
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

docker pull ghcr.io/maziggy/bambuddy:0.1.9b7

<!-- gh-comment-id:3878078712 --> @maziggy commented on GitHub (Feb 10, 2026): docker pull ghcr.io/maziggy/bambuddy:0.1.9b7
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Fixed! Maybe consider adding it to the L/R too? I think L/R nozzle info are inverted as only the R can have a serial. So maybe IDs are swapped?

Image
<!-- gh-comment-id:3878188373 --> @Keybored02 commented on GitHub (Feb 10, 2026): Fixed! Maybe consider adding it to the L/R too? I think L/R nozzle info are inverted as only the R can have a serial. So maybe IDs are swapped? <img width="735" height="477" alt="Image" src="https://github.com/user-attachments/assets/8167c301-02a3-4230-b82a-a33e3eaf9d55" />
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

docker pull ghcr.io/maziggy/bambuddy:0.1.9b8

Please show me how the nozle rack hover card looks!

<!-- gh-comment-id:3878428027 --> @maziggy commented on GitHub (Feb 10, 2026): docker pull ghcr.io/maziggy/bambuddy:0.1.9b8 Please show me how the nozle rack hover card looks!
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Can't currently build in dev venv, got an error regarding one of the latest additions about meail auth https://pastebin.com/8Y7JTM1w
Already updated dependencies, let me see if it's just me.
Edit Fixed

<!-- gh-comment-id:3878853744 --> @Keybored02 commented on GitHub (Feb 10, 2026): Can't currently build in dev venv, got an error regarding one of the latest additions about meail auth https://pastebin.com/8Y7JTM1w Already updated dependencies, let me see if it's just me. Edit Fixed
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

It's already fixed. Wait.....use ghcr.io/maziggy/bambuddy:0.1.9b9

<!-- gh-comment-id:3878908716 --> @maziggy commented on GitHub (Feb 10, 2026): It's already fixed. Wait.....use ghcr.io/maziggy/bambuddy:0.1.9b9
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Not using docker rn, and I can't see a new commit on the branch

<!-- gh-comment-id:3878944965 --> @Keybored02 commented on GitHub (Feb 10, 2026): Not using docker rn, and I can't see a new commit on the branch
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

Anyway, I sorted it out. Maybe I'll propose a PR later.

Image Image
<!-- gh-comment-id:3878955542 --> @Keybored02 commented on GitHub (Feb 10, 2026): Anyway, I sorted it out. Maybe I'll propose a PR later. <img width="741" height="464" alt="Image" src="https://github.com/user-attachments/assets/bf497d74-5e85-48ba-b363-957faf80d9c7" /> <img width="729" height="466" alt="Image" src="https://github.com/user-attachments/assets/ea3b4b0e-4c93-4c65-a0bb-222f280c722b" />
Author
Owner

@Keybored02 commented on GitHub (Feb 10, 2026):

FWI, latest commit fixes

<!-- gh-comment-id:3878976032 --> @Keybored02 commented on GitHub (Feb 10, 2026): FWI, latest commit fixes
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):


If you find Bambuddy useful, please consider giving it a on GitHub — it helps others discover the project!

<!-- gh-comment-id:3879088260 --> @maziggy commented on GitHub (Feb 10, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!
Author
Owner

@jjjonesjr33 commented on GitHub (Feb 10, 2026):

The fillament in the nozzle is super hard to read when it's actually colored like that. I would have rather just liked it to stay within the popup/hover over.

Image Image
<!-- gh-comment-id:3879906453 --> @jjjonesjr33 commented on GitHub (Feb 10, 2026): The fillament in the nozzle is super hard to read when it's actually colored like that. I would have rather just liked it to stay within the popup/hover over. <img width="266" height="260" alt="Image" src="https://github.com/user-attachments/assets/b8742f41-3d36-4330-8985-4a06d0d9b3d5" /> <img width="757" height="662" alt="Image" src="https://github.com/user-attachments/assets/2d1eec3d-1630-423e-a298-54a59a9acd1b" />
Author
Owner

@maziggy commented on GitHub (Feb 11, 2026):

ghcr.io/maziggy/bambuddy:0.2.0b1

<!-- gh-comment-id:3882626667 --> @maziggy commented on GitHub (Feb 11, 2026): ghcr.io/maziggy/bambuddy:0.2.0b1
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#184
No description provided.