mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #311] [Bug]: H2C Update Issue #193
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
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#193
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 @jjjonesjr33 on GitHub (Feb 9, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/311
Originally assigned to: @maziggy on GitHub.
Bug Description
When downloading an update for the H2C through the UI, it’s being detected as an H2D and ends up pulling the wrong firmware.
Expected Behavior
Updates should download and install firmware for the correct printer model.
Steps to Reproduce
When an update is shown, click Update to begin the process.
Printer Model
H2C
Bambuddy Version
v01.9b
Printer Firmware Version
01.01.03.00
Installation Method
Docker
Operating System
Docker
Relevant Logs / Support Package
Screenshots
Additional Context
I noticed an update was available and went to try it, but found out it was for the wrong make and model of printer.
Checklist
@maziggy commented on GitHub (Feb 10, 2026):
Fixed in branch 0.1.9b. Please let me know if it works now.
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
I'll try as soon as docker says update available 😄
@maziggy commented on GitHub (Feb 10, 2026):
docker pull ghcr.io/maziggy/bambuddy:0.1.9b
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
Can confirm—the update no longer appears. The only thing is, I would’ve expected it to show as updated with a green indicator like the others. Similar to how the firmware updater worked before, it would be nice if it displayed the currently installed firmware along with the release notes for that version. Would it be possible to add that?
@maziggy commented on GitHub (Feb 10, 2026):
Not sure...can you please explain more detailed?
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
Example: Have the version number in green when its updated to the latest, and then when out of date do the orange color
And when you click on the version it gives you the current release notes similar to what the latest update pulls.
So instead of this, it would be green, show the current version its on since its up to date, with the current release notes for v01.01.03.00 .... ect ...
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
Speaking about how the update is listed, you could tecnically do that for the AMS units as well. I know when I first got mine it said they were out of date and needed an update. I don't know if you have it programmed to show they are out of date, but might be something to add to confirm version.
You could also add hover over for serial number like how you are doing with the nozzles.
@maziggy commented on GitHub (Feb 10, 2026):
May I ask you please to open a separate feature request for the AMS? Thx
@maziggy commented on GitHub (Feb 10, 2026):
Available in branch 0.1.9b.
Oh...wait Sir.....docker pull ghcr.io/maziggy/bambuddy:0.1.9b3 :)
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
Love that!
The only thing I would add would be to have the release notes for the current firmware listed. But this is great.
@maziggy commented on GitHub (Feb 10, 2026):
Hmmm...for the H2D i see it.
@maziggy commented on GitHub (Feb 10, 2026):
X1C
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
I wonder if it's because I am on the beta firmware for the H2C?
@maziggy commented on GitHub (Feb 10, 2026):
Ahhh....yes, that's it! Let me check what we can do.
Are the beta firmware details public?
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
You know I am not sure, but it is a public beta so? It pulls like a normal OTA
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
Was able to get that setup for you in https://github.com/maziggy/bambuddy/issues/321
@maziggy commented on GitHub (Feb 10, 2026):
Problem is, that Bambu Lab simply hasn't published any firmware data for the H2C on their download page yet.
commit
19289855de(HEAD -> 0.1.9b, origin/0.1.9b)Author: maziggy mz@v8w.de
Date: Tue Feb 10 12:31:14 2026 +0100
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@jjjonesjr33 commented on GitHub (Feb 10, 2026):
Hmmmm,
I wouldn't say that was misleading, to me that would read acurate, does the info when it pulls show exactly like
If it does, you could have it say for example: v01.01.03.00(Latest Version) Beta. That keeps me on track with my dev machines.
Version v0.1.9
@maziggy commented on GitHub (Feb 11, 2026):
The challenge is that Bambu Lab's API doesn't return any firmware data for the H2C yet — no latest version, no release notes, no beta/stable distinction. So Bambuddy has nothing to compare your installed version against.
Showing a green "up to date" badge in that situation would be unreliable — it would show green even if you were several versions behind, simply because there's no reference point. And labeling it "Beta" or "Latest Version" isn't something Bambuddy can determine on its own without that upstream data.
Once Bambu publishes H2C firmware info to their API (which will likely happen when H2C exits beta), the badge will automatically appear with proper version comparison and release notes — just like it works for the H2D and X1C today.