r/OpenBambu

Multi-pronged Approach Will Help Users Quickly while Seeking Optimal Long-Term Solutions

"Software Freedom Conservancy (“SFC”) announces a new initiative regarding the software right to repair for users and consumers of 3D printers manufactured by Bambu Lab. After recent news of violations of the Affero General Public License, version 3 (“AGPLv3”), SFC staff began a comprehensive AGPLv3 compliance investigation of both the userspace software and firmware on Bambu's devices. While the investigation is ongoing, two specific AGPLv3 violations have been confirmed."

Full article:

https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/

Happened upon the other post and people were so mad about it that I took 5 minutes to make it without ai. Someone else can make it a sticker if they want, I'm too lazy and can't be arsed.

May 18 2026 - Description: Help us reach this goal so we can dedicate a full-time SFC staffer on our software right to repair work for 3D printers, and take action on Bambu Lab's AGPLv3 violations!

The project is by: Bradley M. Kühn & Software Freedom Conservancy

https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/

Apparently, some people are too lazy to read: This is Bradley M. Kühn & Software Freedom Conservancy - The original author of the Affero General Public License that Bambu use, or, almost every 3D printer manufacturer.

The link takes you to HIS organization. If you don't trust the link, just Google the organization:

• Software Freedom Conservancy

https://xcancel.com/josefprusa/status/2056483660107337847#m

I'm posting this here as a mirror, since it's not allowed on official channels. The workaround, posted official by Bambu in 2024 on their own GitHub project. Yes, it was actually posted by Bambu themselves back in 2024. The developer, Paweł Jarczak, simply picked it up for his fork.

Anyone can check this for themselves using the link; it goes directly to the official Bambu GitHub page.

https://github.com/bambulab/BambuStudio/blob/35e03568080b5897ee969a47a0524000d2dd6988/version.inc

Prusa on Bambus AGPL violations - Full statement: https://x.com/josefprusa/status/2054602354851254330

...has already been posted in the official subreddit as well as in the official forum. Here as a repost/mirror.

Greetings,

Hopefully this is the correct sub for this. I've got a P1S that I've had for some 18 months now. I got it shortly before all the contretemps from BambuLabs regarding locking out other slicers and such.

I've got it in LAN mode and other than start up, have never updated the firmware. It works great with OrcaSlicer running on a Linux box.

This week, I stood up an instance of Bambuddy in my home lab. It's interesting, but what I was primarily looking for was a way to slice and print from my Windows 10 machine which has no internet connectivity.

I've worked through a number of niggles, but I'm not able to print. Bambuddy sees the printer, but the comm's just time out when a print job is sent.

Working with the dev, he commented that my firmware is over a year old and suggested updating it.

My apologies, as I've really not followed this, but what is the current school of thought regarding updating firmware?

Thank you

Hey all,

I got tired of the official Bambu Handy app requiring a cloud account to do things that never needed to leave my house, so I built a local-only Android companion app for my P1S.

BambuMobile: It connects directly to your printer over LAN using MQTT on port 8883 and the camera stream on port 6000. No Bambu cloud. No account. No data leaving your network. Works the same way OrcaSlicer and the other community tools do.

What it does:

• Live MJPG camera feed (pure Rust TLS implementation)
• Print status: progress %, layers, remaining time, stage
• Nozzle and bed temperatures with targets
• Pause / Resume / Stop
• Chamber light toggle
• Speed mode (Silent / Standard / Sport / Ludicrous)
• AMS view: per-unit humidity grade (A–E), per-slot filament type and colour
• External spool display
• Manual jog controls with an OrcaSlicer-style XY wheel, separate extruder column, and Z/bed column: ±1 and ±10 mm steps plus home
• Credentials saved to app data: no browser storage

On right to repair:

You paid $700+ for a printer. The MQTT broker is on the printer. The camera stream is on the printer. None of it needs the internet. But the official app routes it through Bambu's servers anyway. Projects like OpenBambuAPI document these protocols so that community tools can exist independent of whatever Bambu decides to do with their cloud, their ToS, or their business model in the future. That's worth building for.

Disclaimer:

Yes it was vibe coded. With Claude. Please don't come whining about it. It's open source so you can go and fix it if you want. I don't write Rust.

The app works great on my P1S. If someone can test it on a P1P, X1C, or A1 that'd be excellent. Don't @ me about code quality.

Built with Tauri v2 (Rust backend) + React/TypeScript. Licensed AGPL-3.0 so you can fork it, but keep it open.

GitHub: https://github.com/joel-sgc/BambooMobile

Roadmap has multiple printer support and some kind of print file browsing. We'll see what's possible on the protocol side.

More background on the MCP server in general from my last update here: https://www.reddit.com/r/BambuLab/comments/1ruzvov/updated_and_improved_mcp_server_for_bambu/

Updated implementation: https://github.com/DMontgomery40/bambu-printer-mcp

Thank you, FULU Foundation , u/larossmann and everyone else contributing to the open source community and the right to repair mission.

Testers for Windows needed! Please submit issues with as many log details as possible!! (always scrub PII first)

I am working on getting Openbu into the Google Play Store. It is a replacement for Bambu Handy and Lanbu, and has been around for three months.

I need your help. Google has requirements of 20 testers before they will publish a new app to the store. Please DM me your Google Play Store account's email address, aka the Google account email address you logged into your Android device with and use with the Google Play Store. After I add it you can use this link on the Android device.

The goal with getting it into the Google Play Store is to reach a wider audience. It is Open Source, and free. It will be staying free.

Screenshots of Openbu can be found here.

If you aren't interested in being test it for entry from the Google Play Store you can also just download the apk from here.

Features:

• Auto-detects printers, and auto fills in the ip address and serial number. Hence only requires the access code.
• Saving the printer connection settings by default
• Bed and nozzle temperature control
• Fan speed control
• Allows the user to add an external RTSP stream to the dashboard by entering a RTSP URL, and with pinch to zoom
• Supports the A1 and P1 series video stream based on JPEGs with pinch to zoom.
• Support RTSP streams from non-P1 series internal cameras with pinch to zoom
• Supports toggling of the chamber light
• AMS HT, AMS, and AMS 2 Pro
  • Knows the correct number of trays per model
  • Shows temperature, humidity, filament types, and filament colors
  • Assigning filament types and filament colors per tray
• Showing filament type and filament color of the External Spool
• Assigning filament types and filament for the External Spool
• Shows job status including layers, time left, estimated time, job name, and percentage of job done
• Shows status of the nozzle and bed
• Shows status of part fan, aux fan, and chamber fan depending on what the printer model has
• Setting print speed
• Pause/Resume and Stop
• File management via File Manager which uses FTPS
• Skip Objects support
• Remote access via openbu-relay

Edit: 5 testers enrolled, and 15 more to go.

Finally it's here and it's working. Thanks to great work of Alexey Cluster!

So here is the source: https://github.com/ClusterM/open-bambu-networking

And I've compiled it for Orca Slicer 2.3.2 and above (tested on dev build 2.4.0): https://github.com/Lojza007/open-bambu-networking/releases

It works with Alexey P2S and mine P1S. Now you can access files on printer and time lapses too. And I hope it'll be soon included in Orca Slicer.

If you want to compile by your self you need:

- GIT: https://github.com/git-for-windows/git/releases/tag/v2.54.0.windows.1

- Visual Studio 2019 Community Edition: https://aka.ms/vs/16/release/vs_community.exe (and select Desktop development with C++)

- VCPKG: https://github.com/microsoft/vcpkg (and after clone execute bootstrap-vcpkg.bat)

And then you need to open Developer PowerShell for VS 2019 and execute:

$env:VCPKG_ROOT = "C:\path\to\vcpkg"
.\configure.ps1 -ClientType orca_slicer
cmake --build   build --config Release
cmake --install build --config Release

I just installed my new BMCU370c with 4 dry boxes setup hoping I would be able to keep the spools in without needing to store them in a sealed bag every time I finish printing.

I sealed the upper lid with silicone but when pressing the box I do notice some air flow from the ptfe tube on the bmcu side.

I put some silica gel and I noticed it absorbed some moister in 2 days and turned pink.

Should I keep the spools in the dry boxes or will it ruin them?