[GH-ISSUE #568] [Feature]: Support upgrading to intermediate firmware versions #373

Closed
opened 2026-05-06 12:28:51 +02:00 by BreizhHardware · 10 comments

Originally created by @Cornelicorn on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/568

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

In https://github.com/maziggy/bambuddy/issues/520 it was raised that bambu didn't upload the offline package yet, which is true, but the assumption that they always do seems wrong. I ran into a similar problem with my P2S, which has an update available (Currently 01.00.05.00, available: 01.01.00.00,01.01.01.00,01.01.03.00). On the firmware website there's only 01.01.01.00 available. I wrote to Bambu Support and asked them what the expected timeline for the update is, to which they replied:

Firmware version 01.01.03.00 is a hotfix version, and there are no plans to release an offline package for it. The next one will likely be released around May.

It would be nice to update to intermediate releases. This would also be nice if the newest version has some known issue, but you still want to update to a version in between.

Proposed Solution

Intermediate firmware versions are available for downloading in the firmware update modal and can be downloaded to the printer independently of the newest firmware version.

Alternatives Considered

It's of course possible to manually download the firmware file and transfer it to the USB stick and then start the offline upgrade.

Feature Category

Other

Priority

Nice to have

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 @Cornelicorn on GitHub (Mar 2, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/568 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case In https://github.com/maziggy/bambuddy/issues/520 it was raised that bambu didn't upload the offline package yet, which is true, but the assumption that they always do seems wrong. I ran into a similar problem with my P2S, which has an update available (Currently `01.00.05.00`, available: `01.01.00.00`,`01.01.01.00`,`01.01.03.00`). On the firmware website there's only `01.01.01.00` available. I wrote to Bambu Support and asked them what the expected timeline for the update is, to which they replied: > Firmware version 01.01.03.00 is a hotfix version, and there are no plans to release an offline package for it. The next one will likely be released around May. It would be nice to update to intermediate releases. This would also be nice if the newest version has some known issue, but you still want to update to a version in between. ### Proposed Solution Intermediate firmware versions are available for downloading in the firmware update modal and can be downloaded to the printer independently of the newest firmware version. ### Alternatives Considered It's of course possible to manually download the firmware file and transfer it to the USB stick and then start the offline upgrade. ### Feature Category Other ### Priority Nice to have ### 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-06 12:28:51 +02:00
Author
Owner

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

Yeah, but how shall I do that if Bambu Lab doesn't publish the firmware?

<!-- gh-comment-id:3983204569 --> @maziggy commented on GitHub (Mar 2, 2026): Yeah, but how shall I do that if Bambu Lab doesn't publish the firmware?
Author
Owner

@Cornelicorn commented on GitHub (Mar 2, 2026):

What I'd imagine would be a drop down with all versions that are newer than the currently installed firmware, allowing to download in this case the version 01.01.01.00 explicitely instead of the newest version.

<!-- gh-comment-id:3983242203 --> @Cornelicorn commented on GitHub (Mar 2, 2026): What I'd imagine would be a drop down with all versions that are newer than the currently installed firmware, allowing to download in this case the version `01.01.01.00` explicitely instead of the newest version.
Author
Owner

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

Still don't get it. Bambu Lab has answered, that these versions are not available as offline packages?! So how should I detect them?

<!-- gh-comment-id:3983251439 --> @maziggy commented on GitHub (Mar 2, 2026): Still don't get it. Bambu Lab has answered, that these versions are not available as offline packages?! So how should I detect them?
Author
Owner

@Cornelicorn commented on GitHub (Mar 2, 2026):

In this case 01.01.01.00 is available as an offline package, but not 01.01.03.00. In the firmware release history all of them are listed.

<!-- gh-comment-id:3983273188 --> @Cornelicorn commented on GitHub (Mar 2, 2026): In this case `01.01.01.00` is available as an offline package, but not `01.01.03.00`. In the firmware release history all of them are listed.
Author
Owner

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

So it should list all found versions for printer model and indicate their status (available for download, not available for download)?

<!-- gh-comment-id:3983296820 --> @maziggy commented on GitHub (Mar 2, 2026): So it should list all found versions for printer model and indicate their status (available for download, not available for download)?
Author
Owner

@Cornelicorn commented on GitHub (Mar 2, 2026):

Yes, that would be ideal I think / would allow the upgrade to the available versions

<!-- gh-comment-id:3983303232 --> @Cornelicorn commented on GitHub (Mar 2, 2026): Yes, that would be ideal I think / would allow the upgrade to the available versions
Author
Owner

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

Got it.

<!-- gh-comment-id:3983356006 --> @maziggy commented on GitHub (Mar 2, 2026): Got it.
Author
Owner

@mandatoryoption commented on GitHub (Mar 4, 2026):

I was going to look into this myself. The container log shows:

2026-03-04 11:35:07,992 INFO [backend.app.services.bambu_ftp] FTP connected successfully to xxx.xxx.xxx.xxx (model=P2S, prot_c=False)
2026-03-04 11:35:08,084 WARNING [backend.app.services.firmware_check] No firmware download URL available for model: P2S
2026-03-04 11:35:08,085 ERROR [backend.app.services.firmware_update] Firmware upload failed for printer 1: Failed to download firmware

So as an intermediate step, what if we could provide the URL for the firmware in the dialog?

<!-- gh-comment-id:3998770255 --> @mandatoryoption commented on GitHub (Mar 4, 2026): I was going to look into this myself. The container log shows: ``` 2026-03-04 11:35:07,992 INFO [backend.app.services.bambu_ftp] FTP connected successfully to xxx.xxx.xxx.xxx (model=P2S, prot_c=False) 2026-03-04 11:35:08,084 WARNING [backend.app.services.firmware_check] No firmware download URL available for model: P2S 2026-03-04 11:35:08,085 ERROR [backend.app.services.firmware_update] Firmware upload failed for printer 1: Failed to download firmware ``` So as an intermediate step, what if we could provide the URL for the firmware in the dialog?
Author
Owner

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

Before we commit to building this, I'd like to gauge community interest. If you'd find this feature useful, please give this issue a thumbs up (👍) reaction so we can prioritize accordingly.

<!-- gh-comment-id:4116100060 --> @maziggy commented on GitHub (Mar 24, 2026): Before we commit to building this, I'd like to gauge community interest. If you'd find this feature useful, please give this issue a thumbs up (👍) reaction so we can prioritize accordingly.
Author
Owner

@maziggy commented on GitHub (Apr 14, 2026):

Available/Fixed in branch dev and available with the next release or daily build.

Image

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

<!-- gh-comment-id:4242683780 --> @maziggy commented on GitHub (Apr 14, 2026): Available/Fixed in branch dev and available with the next release or daily build. <img width="458" height="649" alt="Image" src="https://github.com/user-attachments/assets/23a92563-476f-426b-8af3-86a0a503d0f0" /> ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!
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#373
No description provided.