This looks to be a clone of the prior state of the repository that caused all the Bambu drama earlier this week.
I did a ton of research because I didn't understand what people wanted here, and this is what's going on:
Right now, Bambu have adjusted their system into two modalities:
* "default" or "Cloud" mode, where you get an app, remote monitoring, but you have to use Bambu Studio or Bambu Connect to send prints. They implemented this by adding cloud auth to their "internal API;" the client application has to get a token from Bambu's servers, even if the request it eventually makes is a "local" one.
* LAN / Developer mode, where the device displays a token and you put it into your app. This disables all of the remote monitoring but in exchange, clients can send prints locally.
What users want is to "have their cake and eat it too;" they want the local token authentication _and_ the cloud authentication enabled at the same time. This isn't actually possible, so this plugin approximates it by emulating the interface to the cloud authentication to make the "Bambu Network" cloud RPC calls from a local slicer (one of these calls is a local_print call, so ostensibly this allows you to send prints without running them through the cloud, although with all of the online functionality still enabled and required, this seems like a pretty brave thing to trust).
Personally, I find the Bambu reaction distasteful, and there's an argument that the offline mode only exists due to similar outrage, but I don't see the current system as particularly bad and find the appetite to restore "untrustworthy" cloud functionality a bit amusing.
I dont understand what the issue is. Theres not really any benefit in having cloud enabled if local is working fine. I have my bambu printer set to local only, and dont miss the cloud offer one bit.
Sure, but it's their right to enact that restriction on their software. There are more open alternatives like Prusa , Elgoo, or Creality if people prefer a more open/freedom approach. On the other hand, Bambu has a reputation for having most of the best products in the space.
Of course, many prefer to break their license agreement because They Really Want It, in effect daring Bambu to get aggressive with license enforcement. They probably won't...
They have no rights to prevent people modifying and using AGPL software however they want.
They should have no rights to control how people use hardware they bought. ToS for hardware should simply be unenforceable.
People should have full rights to adversarial interoperability, even if it means modifying proprietary software or hardware.
It always surprises me when people (on this site particularly) are more interested in the law as it stands than how things could or should be.
I wonder whether tech has become so exploitative partly because so many of us have lost track of (or never understood) how important civil disobedience has always been in the process of democracy and securing our rights.
As an individual you really don’t have to follow the terms of service! You certainly don’t have to support the [ab]use of ToS, DRM and related tech to screw you at every opportunity!
> many prefer to break their license agreement because They Really Want It
By "many" do you mean Bambu Lab themselves who are violating the AGPL license of Prusa slicer & predecessors with their non-AGPL, proprietary networking plugin?
They're choosing to violate the license because they don't think anyone will actually dare to sue them, and they're probably right. Ascribing some sort of moral righteousness to Bambu's actions and accusing users of breaking their license is hysterical.
That's a highly creative interpretation of events. The software license agreement usually upfront covers what can or cannot not change. It is pretty rare in most countries to see successful legal action for changed features, but best of luck.
They will just fine them into oblivion; they are known to fine companies AUD10M to AUD50M for this sort of thing, and from 1st April this year they can now fine up to AUD100M.
Will this mean that Bambu will withdraw from the Australian market? Possibly maybe probably, but the ACCC takes a very hard stance against bait and switch.
The largest ACCC fine to date for a company undertaking anti consumer practices is $483m against an educational provider for misleading students.
I'd be reasonably happy to lodge a complaint if I could find a version that's reasonably articulated. As a Bambu customer in Australia I switched my printer to local mode and its been great.
It's a whole lot better than the US, but AUD100M isn't enough to scare a lot of companies. A law with real teeth would go after an increasing percentage of their revenue for each offense.
Taking functionality away from a product after you bought it is a scum move. If the law lets them get away with it, the law should be changed.
When I buy a product, I look at reviews and make my purchasing decision on the features and functionality at the time of sale. If a software update later ruins that, I want the option to get my money back.
No, it’s not creative at all, it’s what happened — I have first hand experience to corroborate this.
Regardless, at least in the US, not only are software-based ToS becoming unenforceable, but there’s a large upswing towards “right to repair” legislation, which, I think, is what you’re arguing against here… and I really think you’re going to be on the wrong side of history with your current line of thinking (despite what Bambu Labs does).
The "agreement" is at best coerced, and under blackmail of hardware you bought and paid for.
At worst, its a fraudulent indefinite rental masquerading as a 'sale'.
And lets discuss 'updates that fuck over your hardware'. In dwcent countries, thats hacking, and a serious criminal charge. But lol, companies are somehow exempt.
Maybe legally, but morally “you have permanent physical access to this but don’t ’own’ it” and anti-circumvention are debatable.
There’s a small benefit of anti-circumvention where businesses sell hardware for cheaper with restrictions and a TOS that prevents bypassing them. But even that doesn’t apply here because Bambu changed the software after purchase.
This reminds me of RMS and GPLv3. Now I personally don't use GPLv3, but this here is literally a case-in-point, and it is not even only limited to the "cloud-only". Because this now includes a company threatening to sue a developer. If they sue one developer, they, by proxy, sue all of them in principle. So RMS was kind of right.
> If you want to use Bambu's software against their TOS
How does the TOS get involved here? I don't use their TOS. Why would or should they be able to enforce it? Note that it also depends on the jurisdiction. For instance, Microsoft's EULA never had any legal bearings in the EU.
> it's their right to enact that restriction on their software
The issue here is less "they put in a restriction" and more "they are trying to bankrupt/imprison consumers for daring to modify the property they purchased."
Great: very few people care enough to actually try to understand! This is very much appreciated.
> What users want is to "have their cake and eat it too;" they want the local token authentication _and_ the cloud authentication enabled at the same time
No.
What I want is to use any slicer software (specifically OrcaSlicer, which is really good) with Bambu printers without losing functionality.
What most people who do not use 3d printing regularly do not understand is that there is more to 3d printing than just throwing a sliced file over the wall. For example, before I slice, I sync information from the printer so that the list of filaments I have in the slicer reflects what is actually in the printer. This sounds silly to people who imagine a printer with a single spool of filament loaded, but when you have multiple printers, each one with an AMS unit housing 4 spools, this becomes essential.
Please also remember that many people have printers in remote locations (workshop). "LAN mode" is a non-starter unless you set up a VPN.
I also want to monitor my prints using my phone, which is what Bambu Lab sold me: it is part of the functionality of the printer. I do not want to lose that functionality.
In other words, "LAN/Developer Mode" is NOT EQUIVALENT to "Cloud" mode (which used to work well with OrcaSlicer until Bambu killed it).
On our Bambu H2D Pro printers at work, we can print in cloud mode and LAN mode at the same time. Bambu literally has this firmware built but they reserve it for “pro” users. The other thing pro users can do is disable cloud without any developer mode stuff. Of course we do this.
Excellent machines by the way, primarily let down by the proprietary binary Bambu forces users to use for LAN mode which is extremely buggy and slow on Linux, and entirely technically unnecessary.
I think the enterprise “LAN Mode” is actually the thing this repo is emulating / replacing, which the consumer printers (might?) also support, where the cloud auth token is still in play but prints are (ostensibly, in a much more difficult to audit way given the client still needs access to the Bambu servers) sent directly to the printer.
Developer mode doesn’t require the proprietary binary.
There's no technical hurdle to achieving both modes or access types (local and cloud) simultaneously. This isn't a technical issue. Selling "Home" and "Pro" devices that are differentiated is also not necessarily a problem, a company is allowed to sell two products with different features and pricing.
There are two problems here. One is when the manufacturer sells something with some capabilities and later pulls the rug from under the users and decides to arbitrarily take some features away. This should entitle any customer to take an arbitrary amount of money back from the manufacturer. The second problem is that after a customer buys the product they aren't allowed to own it. If I buy a hammer I'm, allowed to cut it open, dissect everything, modify the handle or the head. That's ownership, not some shallow dismissal that user want to "have their cake and eat it too".
If someone sells you a cake then follows you down the street to take the frosting and one of the layers back, and tells you that any attempt to restore the cake is a crime, you'd start questioning whether it's really your cake to begin with, and what exactly are you eating.
I'm also trying to get my head around this, as an interested-but-not-directly-involved observer.
> What users want is to "have their cake and eat it too;" they want the local token authentication _and_ the cloud authentication enabled at the same time. This isn't actually possible, so this plugin approximates it by emulating the interface to the cloud authentication to make the "Bambu Network" cloud RPC calls from a local slicer (one of these calls is a local_print call, so ostensibly this allows you to send prints without running them through the cloud, although with all of the online functionality still enabled and required, this seems like a pretty brave thing to trust).
AIUI Bamba has made cloud access all or nothing: you either use local mode, with local slicing, and no cloud feature access at all, or you use cloud mode, with cloud slicing and access to all of the cloud features.
Can anyone explain what the cloud features that people want to retain are? Is it just app control of the printer, and print monitoring? Or are there other things to miss out on?
Being able to push prints and use the printer with direct local connection, while simultaneously having remote monitoring and remote printing when cloud/internet works and is available.
This is not the case of "wanting to have their cake and eat it too", as there is nothing mutually exclusive about these things. It requires no "emulation" or hacks - having a local API open to query state and push print jobs to the queue, while the printer connects to the cloud to publish state and pull the next job, presents no conflict.
Ultimaker has a similar feature set and had full local/cloud simultaneous integration. The only thing you "lost" by pushing a job locally was that when viewed in the cloud portal, the mini 3D model preview in the queue was missing, and only because they never bothered making the cloud solution pull it from the printer for local jobs.
But then they also did like Bambu and killed local printing entirely because they are all enterprise-only now want to sell you their higher Digital Factory subscriptions.
> Being able to push prints and use the printer with direct local connection, while simultaneously having remote monitoring and remote printing when cloud/internet works and is available.
So isn't an obvious approach to just cut Bambu out altogether and just create a FOSS cloud alternative, supporting the remote aspects that the users want to retain?
> This is not the case of "wanting to have their cake and eat it too", as there is nothing mutually exclusive about these things.
Nothing technically mutually exclusive, but isn't this exactly the choice that Bambu is enforcing? Which is crappy corporate enshittification behaviour, but something they can do if they so choose? (I'm not arguing in their favour - just trying to fully clarify the situation.)
> This looks to be a clone of the prior state of the repository that caused all the Bambu drama earlier this week.
It looks like it might be a clone, but the git history is squashed for some reason.
I would recommend against installing this unless/until someone can do an audit to figure out which commit it was forked from and what the changes are.
Or better yet, find one of any of the other copies of the repository that don't have their git history squashed.
This looks like someone's attempt to capitalize on the drama to bring attention to their foundation (?) but losing git history is not a good thing for code provenance or security.
There is some context missing, which this video [0] explains.
tl;dr: The original developer does not (or cannot) go into legal battle with Bambu Lab, so Louis Rossmann's project picked up the fight and hosts the (allegedly) troublesome code on their organization. As they have more financial resources, they look forward to the C&D letter.
The point he has (and I agree with that): The original developer is using the un-modified AGPL-code to talk to the cloud API. Bambu Lab states that the modified client pretends to be a Bambu lab client. But in fact, the modified client just uses the code as-is, which is perfectly fine from a AGPL perspective. From my non-lawyer point of view: If Bambu Lab would have made the User Agent a configurable variable, which gets set by some configuration files from outside the code, that get bundled with the binary version, but not the source code, they wouldn't have this leverage.
Just to confirm so I don't break anything accidentally, I currently have the app version where Bambu Studio is how I send prints to my Bambu P1S and I can look through its camera and see what filament is where and so on, but I also have the token that Home Assistant uses to watch the printer and its camera etc.
This isn't the thing you're talking about. There's a mode where I can send prints directly over the network which disables Bambu Studio, I assume?
You're missing two things from the whole picture:
1. Cloud mode works without local network access, so their server is involved in the transit of the data to the printer. This is pretty minor, but still within their rights to preserve.
2. For printing from the app, they actually run the computationally expensive slicing algorithm on their servers, so this is totally reasonable to protect.
Pretty sure you can still print locally either via LAN or just SD card. At least I can on my A1.
The current monetization that they are using is that you can charge for a print on their platform and they take a cut of the sale. If you don’t charge for the design, then it is still free hosting and delivery.
I see where the worry is, but at the moment it seems like people are imagining a worse case scenario.
If you turn on LAN mode, it acts exactly like every other printer. You can print directly to it from any slicer over your LAN, or dump gcode on the SD card directly.
People are saying the LAN mode lacks access to the webcam and possibly some other things. That is what this whole controversy is about. It's re-enabling some cloud features as local only and Bambu is calling it privacy or fraud.
They probably want to establish a commercial-use license. If you have a big print farm, you likely need all of those remote capabilities so you're going to need to pay for the license. The schmucks at home will likely continue to get it for free. Locking them into the cloud API by dangling convenient features just ensures most people won't stray into the local-only mode.
> No, we aren’t being blocked. Turn on LAN mode, pair regular Orca slicer, ignore Bambu for the rest of eternity. Plenty of people have done it.
You're just saying that Bambu users feel the need to purposely circumvent Bambu's artificial restrictions to be able to continue to use Bambu hardware they bought and paid for.
It's a toggle you set in the printer directly, nothing is circumvented. Only the access through their cloud service is impacted, but the printer works locally like any other.
> 2. For printing from the app, they actually run the computationally expensive slicing algorithm on their servers, so this is totally reasonable to protect.
That's an artificial vendor tie-in, and arguably a feature that only involves their client app and their backend. It's understandable if access to their backend is restricted to a subset of their users if that's the business model they wish. Preventing paying customers from using the hardware they bought and paid for by imposing artificial restrictions is not cool.
They've bought a machine that executes gcode and that it does (at least to my understanding) regardless of where that gcode comes from.
If you want special secret sauce gcode from the bambu cloud, you need to use the bambu cloud.
Those are not the same thing, so IMO it is legit what they do there, because it's such a clear-cut split.
You own the physical thing but not the ecosystem around it.
___
I would of course personally never buy a bambu lab printer, because they're cloud-tied nonsense that was going to behave exactly like that (the split between hw and ecosystem), but other people knew that too and still bought it, because "what a nice ecosystem".
idk.
I just don't think that "right to repair" should mean "right to be saved from the consequences of my own bad actions".
Those bad actions continuing to have no real painful consequences (and with that no real learnings + behavioral correction) after all is why the state of tech has become as bleak as it is right now.
And, honestly, if you can afford a bambu premium machine, there's a 97% chance that you could easily shoulder a total write-off.
There's also a 97% chance that your ego can't, but that's the main thing causing all the bad things in the world and should've died a long time ago. Approximately post-highschool.
Take a step back. What users want is to be able to use the machine they bought the way they want. The outrage is because Bambu are doing a bait-and-switch: selling an autonomous 3D printer, but switching to a 3D printing service. Enshittification pure and simple.
I don't think they baited and switched? I bought my P1S before the whole LAN mode debacle and even then it was all or nothing on the cloud. I just went with the cloud because they were using some IGMP stuff for the local connection, but I had the printer on a separate VLAN and pfsense IGMP proxying was broken.
A different way of looking at it is that Bambu is saying if you want to use their cloud you have to send everything through their cloud. Stupid? Sure. It's very much a technically solvable problem. But I don't think there was any rug pull (this time; in Jan 2025 they tried...)
I think this is all more out of incompetence than malice. Something bad happens, exposing wildly inadequate programming expertise, they panic and over correct, and the community pushes back. They're great at making 3D printers, terrible at cloud infra.
For me, I want to use orca for slicing there are many more additions to the local code. As both orca and Bambo are from the same open source, the current limitation in the Bambo version is breaking the licensing of the application, and my rights in that software are broken by this addition.
Then, during the print, I'm really happy to use the handy app to monitor the progress. This use case was supported when I got the hardware. Now I have to disable the app to get the slicer. I actually like to use both slicers to compare and see progress.
They are also terrible at software licensing, don't understand what open source is, and they found their main software on that. They probably should embrace the orca community and use their research for their own customers. Better slicing helps everyone.
Why should I have to send all my prints to Bambu when the printer is sitting right next to me? Why do I have to choose between being able to stop my printer remotely or Bambu not tracking my every move, when it's trivial to have both?
I don't think so. They can already track popularity very effectively because they control makerworld, and they could have Bambu studio, the app, and the printer phone home too. I don't think they care enough about the tiny tiny minority of users running orca with a LAN only printer.
More likely, it's technical incompetence. It's just easier (for their cloud) to send everything through their cloud
I think OP meant designs which are not on MakerWorld.
And I think technical incompetence is not a reason here otherwise they wouldn't gatekeep the access so much.
Using an AGPL violating mystery meat binary plugin that you run on your host, which potentially compromises any airgap you put around your printer (it attempts to connect to bambu servers, or did last time I checked it) and potentially your entire host.
> (...) I don't see the current system as particularly bad and find the appetite to restore "untrustworthy" cloud functionality a bit amusing.
This is a very dubious opinion to hold. Taking your claim about local mode at face value, there is absolutely no reason to disable monitoring when working on LAN mode. You need to go way out of your way to implement that restriction so that it works differently when the thing phones home or not. You are free to criticize implementation decisions that you feel make it "untrustworthy" but those are trivial to address if you think about it.
I really recommend you to reassess your whole philosophical stance on having corporations prevent you from using what you bought and paid for.
A lot of the distrust toward Bambu is because they originally announced cloud auth would be required even for printing locally in LAN mode, and only backpedalled on that when they saw the backlash.
Critical Operations That Require Authorization
The following printer operations will require authorization controls:
Binding and unbinding the printer.
Initiating remote video access.
Performing firmware upgrades.
Initiating a print job (via LAN or cloud mode).
Controlling motion system, temperature, fans, AMS settings, calibrations, etc.
> I'm not sure why their entire domain has been excluded from archive.org
Because they have a track record of altering their website, gaslighting the community, and then getting caught through archive.org so they simply blocked it, not realizing that other archives exist and then getting caught again.
They tried to alter their warranty terms and got caught. They altered their ToS which would allow them to block prints until the printer firmware was updated. When the community got upset, they not only backpedaled but altered the associated blog post and accused everyone of spreading baseless misinformation because "it's clearly explained in this [edited, backdated] article".
That's precisely the article you linked to. See the original version:
Reminder about the way Ubiquiti does this, as a vendor who wanted to provide users remote access to their own devices behind NAT: Unifi Cloud handles the auth and connection brokerage through a public portal, but you’re then connected straight to your own gear using your web browser (or one of the apps, if you choose). I can even turn all this off if I want to handle the remote access side of it myself.
The important part here is not just printer support, but whether users can keep using hardware they already own without depending on a vendor cloud path.
Local network support tends to look like a convenience feature until it disappears. Then it becomes obvious that it was part of the ownership model.
> whether users can keep using hardware they already own without depending on a vendor cloud path.
That’s a complete misunderstanding of the current state of affairs. Bambu didn’t take away local network support, and you can use any Bambu printer without any cloud or internet connection.
What you can’t do is use a 3rd party slicer with their cloud servers…
Yes they did. Chronology is important because it speaks to their motives. First they blocked Orca slicer and others from connecting to the printer even when the printer is running in LAN-only mode. Due to extensive backlash they later split "LAN mode" into "Standard mode LAN mode" and "Developer mode LAN mode".
The former, officially recommended, "secure" mode would prevent Orca slicer and others from using the printer.
"Developer mode LAN mode" dropped all form of access control (including existing access code + serial number pairing mechanism), leaving users completely exposed - any device on your network, and any process on your machine can freely take control of the printer. They simultaneously absolved themselves of all customer support responsibilities for anyone using this mode.
They also abandoned all work on features and bugs related to LAN mode (whether they affect standard mode or developer mode). Bambu Slicer is plagued by basic connectivity and usability issues that only affect LAN mode, feature parity is not there and there's been quite literally zero activity on any of the issues I've been following.
That’s a vibe coded AI slop website if I’ve ever seen one. It even has a careers page that they didn’t try to edit out.
There’s basically no information there. Is this just a copy of the other GitHub repo that was removed and someone is trying to rebrand it as their own? Or did they do some different work?
From what I gathered from (part of) the video, it's not about the HTML, it's the copy. Basically Google is accidentally/intentionally optimizing for copy that sounds like it came from an LLM or a LinkedIn lunatics post.
I'm skeptical but I don't have time to watch the entire video so I don't want to cast an initial judgement on if he's correct or if it just has to do with his specific copy.
yes, but that is not the problem here. the problem is that google search favors AI slop that makes this the preferred method of webdesign.
there is a huge difference between creating AI slop because i am lazy (which i think most people doing that are) and creating AI slop because otherwise google gives your website a bad rating.
now you and i may not care about google ratings, but many other people do, and the end result will be that all websites that want good ratings will end up being AI slop.
somehow we need to send google a message to stop that.
The Google excuse doesn’t even hold water when you consider that the content of the website is so bad that it’s not even going to register for the relevant search terms. It’s just empty AI slop copy.
What are they even trying to rank for? It doesn’t make sense.
i think it does. you have to think through the development process here. if we start with the promise that an AI generated site gets more hits, then you'd want to change as little as possible from what the AI generates by hand. yes it's dumb, but the whole premise of generating a website with AI is dumb to begin with.
i'd say that when louis discovered that AI websites work better, it broke him in that regard. the choice is now creating a website that i own, as in "this is mine, i made this". or a website that works with google. but i'd want to distance myself from that website as far as possible. "i didn't make this myself, i needed this for google. i don't want to touch it"
I considered buying bambu lab A1, bout watching this and previous dramas I rather go with different vendor. Are there any good alternatives for newcomers? I like hacker nature and openness of Prusa, but I’m worried if it is good printer as a first one…
Prusa printer are really good. Well at least a few month after the first release :D They tend to release banana products that ripe at the customers.
But for example I had some problems with my linear rods, talked to support for just a few minutes and 2 days later I had replacement parts at my door. This was a few years back though.
Also they give firmware updates, and even hardware upgrade for years! This IS really nice and I'm not sure any other printer manufacturer that sells to private people does this.
Yes, your upfront price is a bit higher. I say it's worth it.
I got a second hand Prusa Mk3s about a year ago as my first printer, around 300 € perhaps. I'm still enjoying it a lot, even though I'm now eyeing one of their upcoming (more expensive) models.
I think it depends mostly on how you expect to use it. There may be alternatives that give you perfect prints with minimal fuzz. But for me it was great to have a machine I dare play around with. Like getting a tractor before a race car :)
I've only had one Prusa printer, a MINI+ and it's been an absolute workhorse and easy to repair using the official instructions (I assembled my unit myself and pulled a zip-tie too tight, which caused the part cooling fan cable to break).
You do pay a premium. I, personally, also found PrusaSlicer to have better presets and usability than OrcaSlicer or it's forks.
it honestly depends on your budget. prusa is definitely overpriced for what you get. but, i bought one anyway specifically because of their stance on OSS, and this kind of bullshit the bambu is pulling. even though bambu objectively has a better or at least equal product for significantly less money.
Just make sure never, ever to buy from them again.
It's the same story as Synology with their forced reliance on specific hard drives.
As long as there are still other providers out there...
Wild speculation here obviously, but it could be a regulation play--there's a lot of potential legislation that would regulate what you can legally 3D print, which would warrant a system to be the age-verification equivalent for 3D printing.
If this is the angle then I'm even more suspicious that they're secretly pushing for the legislation so when it goes into effect they'll effectively be the only game in town.
This is admittedly a bit tinfoil hat, but they wouldn't be the first company to attempt to legislate away the competition.
I've wondered the same thing because lately I've noticed a bunch of consumer companies forcing cloud-required models where it's not necessary and many/most users have no need for whatever features cloud connectivity may provide. Yet the companies keep insisting on it even when there's significant user blow back and bad brand PR. When they even bother to comment on "why", the answers never make much sense.
When it's companies based in the U.S. or EU, like Chamberlain / LiftMaster garage door openers, it's pretty obvious they plan to monetize some cloud services subscription for upgraded features beyond the free basic tier as well as probably selling consumer data.
However, the China-based companies like Bambu Lab (and many others) are more puzzling because meaningful ongoing subscription revenue seems unlikely. Especially in the case of lower-end consumer tech peripherals where the companies usually invest as little as possible in their websites, ongoing feature updates or direct end-user support. Which makes no sense if they really aspire to build long-term subscription revenue. Here's my theory: the Chinese government is quietly compelling them to require cloud connections to China-based data centers as a long-term strategy.
I'm not even saying the companies are some direct arm of the Chinese government or planting nefarious firmware. I think that's too likely to be caught if done at mass scale and it's not even necessary. As long as the cloud servers are in Chinese data centers, the Chinese government can get consumer IP addresses and usage data just from passive packet sniffing and if things turn icy with some foreign countries, they can cause a lot of turmoil simply by selectively blocking packets at the firewall to brick millions of consumer devices.
I know it maybe sounds paranoid and, to be clear, I'm not claiming Bambu Labs specifically is doing this. I actually came up with this theory before I ever heard of Bambu Labs because I have a lot of inexpensive Chinese home automation devices and was surprised by their bizarre insistence on forcing cloud connectivity despite there being no apparent business model incentive and these smaller-scale Shenzen hardware companies showing zero enthusiasm for making a real business out of cloud services. Their cloud implementations are almost invariably the bare minimum possible and seem woefully underfunded. After all, for a low-margin hardware peripheral, every dollar spent running a no-revenue cloud after the sale is pure overhead in a business that live or dies by pennies. It's almost like requiring a cloud connection is an export tax the company is paying just to be left alone to sell their hardware overseas.
For home automation gear, cloud-connectivity is a non-starter in my book. In some cases, it's literally built into our walls, so I only buy devices which will work on a local-only subnet or on which I can install open source firmware like Tasmota or ESPHome.
This. No conspiracy tin foil hat bs, just money. Everything got cloud because investor story time, just like everything has AI now, in every talk I have with either my boss, potential partners and clients its: “where is the AI”? (Source: i am in China). There are a couple of other things that other can maybe highlight, like how every one is blocking Chinese IP’s and vice versa, maybe something on the legislative side also? Not sure. Something something malice/incompetence
Probably regulations, there are a few states trying to make it illegal for felons to own 3D printers by EOY. These things are about to get regulated like firearms, which is wild.
Some of the proposed 3d printer laws will require printers being sold to be capable of evaluating what you are using them for and blocking “bad” usages. I’m not aware of any such legislation around firearms.
Presumably the original dev that implemented the changes for this functionality that pulled the repo does not want to be associated so some level of squashing was required but yeah, the whole history was maybe a bit silly.
There are many reasons one might prefer OrcaSlicer over Bambu Studio. One might be perfectly fine using Bambu's cloud services while preferring OrcaSlicer for different reasons; this is for those people.
Others might not want to use Bambu's cloud services at all; OrcaSlicer as it currently exists is fine for them.
there's not enough appeal with the investors and stock holders.
they're going to try to make everything you have a subscription, starting with the homes you might try to buy. they don't even live here, but there's no laws stopping them, because your representatives personally benefit from letting things go for certain corporations/people (the same thing after the Citizens United decision)
I have an Ender3 that I use plugging in a microsd card to do prints with. What am I missing here? Seems like you can do the same with these printers. People want to use the cloud?
Even with an Ender3 many, including myself, would connect it to a raspberryPi with octoprint to be able to send prints over the network. The SD card flow gets very tedious very quickly.
Oh god. OctoPrint, I forgot about that tool. Jesus, I'm still subscribed after all of these years. I do not want to know how much money I have been quietly bleeding for this tool.
The creator has a patreon[1]. I did a one-time payment too because early on it really changed how I used my 3D printer and thought it deserved some support.
I think people like having an option for remote over the network communication. The cloud is not technically required for that. Bambu made it required for no good reason.
Yes, and aside from being able to send and monitor your prints from their mobile app (and there are third party implementation of a similar app), you really don't lose much by using LAN Mode, especially if you pair it with Tailscale.
The mobile app is quite nice.
Print error and print finish notifications. Webcam view when I’m not near my printer. The ability to pause it remotely if something looks off.
I use LAN mode, plus a home assistant plugin to restore the lost functionality. The default webcam is pretty bad so I’ve also mounted a better one to my printer for a live video view that’s at more than 1fps.
The main thing I’ve lost by using lan mode is printing from my phone? I think there are ways to do that. But OrcaSlicer has so many options that are frequently worth adjusting over random presets other creators used; it’s a strictly better experience compared to printing on mobile.
I think there is some niche “cancel printing of one specific object” feature that I dont know how to use without the mobile app. If you are printing many objects at once, and one fails, you can cancel a specific part/object using the mobile app. Not sure how to do that with OrcaSlicer + lan mode, or if it’s even possible. (Edit: OrcaSlicer doesn’t support it. The home assistant plugin might? Bambu studio in lan mode doesn’t support it either, it requires the mobile app)
I can imagine not having to do the “save to sd card, eject, put in printer, fiddle with the printers crappy ui to select the print” flow might be attractive to some. Find the model you want in the web, click “send to printer”, done.
I don’t mind the sd card thing, also happy with my bottom of the barrel ender 3.
At least your use case would be served well by enabling LAN mode, which doesn't let the printer talk to the internet, even if you want it to (and I want mine to).
It was a mistake by BambuLab to piss off and alienate the community. They poked the bear; stung the bee; squashed the frog. This is literally the Barbara Streisand effect in the modern era. Now people are watching. Reputation went out the window already: "If they can sue one of us, they can sue all of us". (Well, threaten to sue at the least, aka applying financial pressure on that developer.)
Incidentally, almost all color 2D printers insert serial number tracing artifacts, and many 2D scanners and photo editing software prevent manipulation of images containing either EURion constellation circles or Counterfeit Deterrence System patterns. Interestingly, I didn't have a problem downloading, manipulating, or attempting to print currency-detected fragment images on iPadOS 18.x.
If Bambu Lab responds to this criticism with lawyers instead of clear technical answers, it will only make the forced cloud requirement look more suspicious.
To me, this is an obvious security risk. These printers are often used in labs, startups, engineering teams, and potentially even government environments. If print data, models, logs, or usage patterns are routed through a company controlled infrastructure, that creates a real opportunity for corporate espionage or data harvesting.
I would not be surprised if Bambu Lab eventually faces the same level of scrutiny that Huawei network devices did.
I’ve been running mine offline for years, I don’t know why other people haven’t been. They’re the only competent and reliable printer that isn’t a project car in itself, but they’re obviously not completely trustworthy. Easily fixed with an air gap, updates work just great from a USB drive.
Bambuddy and tailscale was my solution to losing access to mobile app once I went lan-only. Has video stream ,monitoring and control. Plus home assistant integration via MQTT. Only thing I’m missing is the ‘AI’ spaghetti monitoring. But those are rare for me.
There's also the Openbu or LanBu android apps if you just want a basic app for monitoring from your phone like Bambu Handy did. Although if you want to access your printer from a remote network you'll still need tailscale or similar.
But when it was online, I never checked the app for failed prints. If the print has failed, I'll find out when I'm near enough to it to do something about it.
When offline, it amused me when there was a "hairball" and the printer detected it advising "AI Detecting Print Error".
At what level does an image analysis algorithm become "AI"?
Yeah I’ve had one, still do, it never gets used because it’s a project car. Compared with one button press and coming back to a print in a few hours, it’s a constant nightmare of debugging, print issues, and manually changing filaments that aren’t stored in an airtight container and get wet. It’s not even competition, as much as I would like to support open source tools the Prusa stuff is an order of magnitude more expensive than a A1 Mini that will make a reliable print every time.
It’s like saying a bicycle is a serious contender to a train, they both have kind of similar things going on but you’d have to be insane to suggest that they do as good of a job as one another at the things people actually want to achieve.
I've done zero debugging on my Prusa and it's been pretty much fire and forget. I had one spaghetti print failure in years on it, and it was my own fault for disabling supports and the print falling over :)
Automatic filament changes would be nice for sure, I look forward to upgrading to one of their new INDX models.
idk, my 10 year old makerbot 2 has been pretty reliable, ever since Prusa slicer came out and I tuned a profile for it maybe 6 years ago it's been spitting out quick dimensionally accurate prints. i use it all the time, probably go through a spool every month or two and all i've had to replace is the cooling fan for the extruder once
i'm mostly printing small mechanical parts and i can't say i have any complaints, i assume a modern prusa would be much better, surely there are other FDM printers that are good?
This looks to be a clone of the prior state of the repository that caused all the Bambu drama earlier this week.
I did a ton of research because I didn't understand what people wanted here, and this is what's going on:
Right now, Bambu have adjusted their system into two modalities:
* "default" or "Cloud" mode, where you get an app, remote monitoring, but you have to use Bambu Studio or Bambu Connect to send prints. They implemented this by adding cloud auth to their "internal API;" the client application has to get a token from Bambu's servers, even if the request it eventually makes is a "local" one.
* LAN / Developer mode, where the device displays a token and you put it into your app. This disables all of the remote monitoring but in exchange, clients can send prints locally.
What users want is to "have their cake and eat it too;" they want the local token authentication _and_ the cloud authentication enabled at the same time. This isn't actually possible, so this plugin approximates it by emulating the interface to the cloud authentication to make the "Bambu Network" cloud RPC calls from a local slicer (one of these calls is a local_print call, so ostensibly this allows you to send prints without running them through the cloud, although with all of the online functionality still enabled and required, this seems like a pretty brave thing to trust).
Personally, I find the Bambu reaction distasteful, and there's an argument that the offline mode only exists due to similar outrage, but I don't see the current system as particularly bad and find the appetite to restore "untrustworthy" cloud functionality a bit amusing.
> This isn't actually possible
This is only true due to a firmware they pushed last year. It's an artificial limit.
There's no reason at all a local client couldn't just talk to a local printer without any cloud.
Every problem BambuLabs have here is self-inflicted. They could allow simultaneous cloud and local queue management with or without authentication.
I dont understand what the issue is. Theres not really any benefit in having cloud enabled if local is working fine. I have my bambu printer set to local only, and dont miss the cloud offer one bit.
Sure, but it's their right to enact that restriction on their software. There are more open alternatives like Prusa , Elgoo, or Creality if people prefer a more open/freedom approach. On the other hand, Bambu has a reputation for having most of the best products in the space.
Of course, many prefer to break their license agreement because They Really Want It, in effect daring Bambu to get aggressive with license enforcement. They probably won't...
They have no rights to prevent people modifying and using AGPL software however they want.
They should have no rights to control how people use hardware they bought. ToS for hardware should simply be unenforceable.
People should have full rights to adversarial interoperability, even if it means modifying proprietary software or hardware.
It always surprises me when people (on this site particularly) are more interested in the law as it stands than how things could or should be.
I wonder whether tech has become so exploitative partly because so many of us have lost track of (or never understood) how important civil disobedience has always been in the process of democracy and securing our rights.
As an individual you really don’t have to follow the terms of service! You certainly don’t have to support the [ab]use of ToS, DRM and related tech to screw you at every opportunity!
> many prefer to break their license agreement because They Really Want It
By "many" do you mean Bambu Lab themselves who are violating the AGPL license of Prusa slicer & predecessors with their non-AGPL, proprietary networking plugin?
They're choosing to violate the license because they don't think anyone will actually dare to sue them, and they're probably right. Ascribing some sort of moral righteousness to Bambu's actions and accusing users of breaking their license is hysterical.
A comment defending abusive software terms on a website called HackerNews. Something amusing about that.
If we go a little meta, there's a lot of comments doing the same thing, on plethora of submissions. It's amusing and sad at the same time.
The AGPL covers the line of code that includes the user agent, the only "security" bambu uses.
By attempting to stop users from using their AGPL code they are behaving illegally.
This is HP’s current philosophy towards consumer desktop inkjet and laser printing, and customers universally hate it. No thanks!
It is my right to do with my printer whatever I want.
The hardware yes. Bambu's software, not quite. If you want to flash it with 3rd party firmware & use 3rd party slicers, have at it.
If you want to use Bambu's software against their TOS, OK you wouldn't be alone in that, but there's no moral high ground in it.
Sure there is. When purchased, it was able to do something. Due to an update, the customer has now been misled, because a feature was removed.
In most countries, that would violate consumer rights. There's an ethics argument here.
That's a highly creative interpretation of events. The software license agreement usually upfront covers what can or cannot not change. It is pretty rare in most countries to see successful legal action for changed features, but best of luck.
The ACCC is more than happy to explain unenforceable terms, if you'd like to do business with Australia.
Feel free to consult Steam, Google, Meta and others, if a software license is enough to ignore consumer rights.
I look forward to them sternly changing Bambu Labs' practices!
They will just fine them into oblivion; they are known to fine companies AUD10M to AUD50M for this sort of thing, and from 1st April this year they can now fine up to AUD100M.
Will this mean that Bambu will withdraw from the Australian market? Possibly maybe probably, but the ACCC takes a very hard stance against bait and switch.
The largest ACCC fine to date for a company undertaking anti consumer practices is $483m against an educational provider for misleading students.
I'd be reasonably happy to lodge a complaint if I could find a version that's reasonably articulated. As a Bambu customer in Australia I switched my printer to local mode and its been great.
It's a whole lot better than the US, but AUD100M isn't enough to scare a lot of companies. A law with real teeth would go after an increasing percentage of their revenue for each offense.
Australia is a small enough market to not matter much
Then why did those company fight, and not just leave...?
Worth pointing out also that the US is the odd one out, here. Europe also enforces consumer rights.
A small, more ethical company filling the void Bambu Lab left can grow much faster and eat into Bambu's market share in a relatively short time.
Yes, it's not as simple as that, but it's not that impossible either.
The only place you can change contracts at will on the company side is the US, and even there it probably depends on the state.
This kind of firmware update to remotely disable feature is also illegal in the EU
Taking functionality away from a product after you bought it is a scum move. If the law lets them get away with it, the law should be changed.
When I buy a product, I look at reviews and make my purchasing decision on the features and functionality at the time of sale. If a software update later ruins that, I want the option to get my money back.
No, it’s not creative at all, it’s what happened — I have first hand experience to corroborate this.
Regardless, at least in the US, not only are software-based ToS becoming unenforceable, but there’s a large upswing towards “right to repair” legislation, which, I think, is what you’re arguing against here… and I really think you’re going to be on the wrong side of history with your current line of thinking (despite what Bambu Labs does).
The license agreement being the AGPLv3?
The "agreement" is at best coerced, and under blackmail of hardware you bought and paid for.
At worst, its a fraudulent indefinite rental masquerading as a 'sale'.
And lets discuss 'updates that fuck over your hardware'. In dwcent countries, thats hacking, and a serious criminal charge. But lol, companies are somehow exempt.
Its the people's software though, used under AGPL by Bambu. It never was Bambu's software.
Maybe legally, but morally “you have permanent physical access to this but don’t ’own’ it” and anti-circumvention are debatable.
There’s a small benefit of anti-circumvention where businesses sell hardware for cheaper with restrictions and a TOS that prevents bypassing them. But even that doesn’t apply here because Bambu changed the software after purchase.
Isn't their software based on AGPL'd code?
If so, then yes, the software too
> If specific terms in a contract are unfair, they are not binding on you and the trader may not rely on them.
https://europa.eu/youreurope/citizens/consumers/unfair-treat...
There's absolutely a moral high ground in it. That's the point.
Nobody is arguing against Bambu's legal right to be arseholes.
ESL? look up the definition of the word moral
This reminds me of RMS and GPLv3. Now I personally don't use GPLv3, but this here is literally a case-in-point, and it is not even only limited to the "cloud-only". Because this now includes a company threatening to sue a developer. If they sue one developer, they, by proxy, sue all of them in principle. So RMS was kind of right.
> If you want to use Bambu's software against their TOS
How does the TOS get involved here? I don't use their TOS. Why would or should they be able to enforce it? Note that it also depends on the jurisdiction. For instance, Microsoft's EULA never had any legal bearings in the EU.
> it's their right to enact that restriction on their software
The issue here is less "they put in a restriction" and more "they are trying to bankrupt/imprison consumers for daring to modify the property they purchased."
Ok, so as a heavy user of Bambu printers:
> I didn't understand what people wanted here
Great: very few people care enough to actually try to understand! This is very much appreciated.
> What users want is to "have their cake and eat it too;" they want the local token authentication _and_ the cloud authentication enabled at the same time
No.
What I want is to use any slicer software (specifically OrcaSlicer, which is really good) with Bambu printers without losing functionality.
What most people who do not use 3d printing regularly do not understand is that there is more to 3d printing than just throwing a sliced file over the wall. For example, before I slice, I sync information from the printer so that the list of filaments I have in the slicer reflects what is actually in the printer. This sounds silly to people who imagine a printer with a single spool of filament loaded, but when you have multiple printers, each one with an AMS unit housing 4 spools, this becomes essential.
Please also remember that many people have printers in remote locations (workshop). "LAN mode" is a non-starter unless you set up a VPN.
I also want to monitor my prints using my phone, which is what Bambu Lab sold me: it is part of the functionality of the printer. I do not want to lose that functionality.
In other words, "LAN/Developer Mode" is NOT EQUIVALENT to "Cloud" mode (which used to work well with OrcaSlicer until Bambu killed it).
On our Bambu H2D Pro printers at work, we can print in cloud mode and LAN mode at the same time. Bambu literally has this firmware built but they reserve it for “pro” users. The other thing pro users can do is disable cloud without any developer mode stuff. Of course we do this.
Excellent machines by the way, primarily let down by the proprietary binary Bambu forces users to use for LAN mode which is extremely buggy and slow on Linux, and entirely technically unnecessary.
I think the enterprise “LAN Mode” is actually the thing this repo is emulating / replacing, which the consumer printers (might?) also support, where the cloud auth token is still in play but prints are (ostensibly, in a much more difficult to audit way given the client still needs access to the Bambu servers) sent directly to the printer.
Developer mode doesn’t require the proprietary binary.
There's no technical hurdle to achieving both modes or access types (local and cloud) simultaneously. This isn't a technical issue. Selling "Home" and "Pro" devices that are differentiated is also not necessarily a problem, a company is allowed to sell two products with different features and pricing.
There are two problems here. One is when the manufacturer sells something with some capabilities and later pulls the rug from under the users and decides to arbitrarily take some features away. This should entitle any customer to take an arbitrary amount of money back from the manufacturer. The second problem is that after a customer buys the product they aren't allowed to own it. If I buy a hammer I'm, allowed to cut it open, dissect everything, modify the handle or the head. That's ownership, not some shallow dismissal that user want to "have their cake and eat it too".
If someone sells you a cake then follows you down the street to take the frosting and one of the layers back, and tells you that any attempt to restore the cake is a crime, you'd start questioning whether it's really your cake to begin with, and what exactly are you eating.
Wow I didn’t know about developer mode! I wonder if that will improve things for me…
I'm also trying to get my head around this, as an interested-but-not-directly-involved observer.
> What users want is to "have their cake and eat it too;" they want the local token authentication _and_ the cloud authentication enabled at the same time. This isn't actually possible, so this plugin approximates it by emulating the interface to the cloud authentication to make the "Bambu Network" cloud RPC calls from a local slicer (one of these calls is a local_print call, so ostensibly this allows you to send prints without running them through the cloud, although with all of the online functionality still enabled and required, this seems like a pretty brave thing to trust).
AIUI Bamba has made cloud access all or nothing: you either use local mode, with local slicing, and no cloud feature access at all, or you use cloud mode, with cloud slicing and access to all of the cloud features.
Can anyone explain what the cloud features that people want to retain are? Is it just app control of the printer, and print monitoring? Or are there other things to miss out on?
Being able to push prints and use the printer with direct local connection, while simultaneously having remote monitoring and remote printing when cloud/internet works and is available.
This is not the case of "wanting to have their cake and eat it too", as there is nothing mutually exclusive about these things. It requires no "emulation" or hacks - having a local API open to query state and push print jobs to the queue, while the printer connects to the cloud to publish state and pull the next job, presents no conflict.
Ultimaker has a similar feature set and had full local/cloud simultaneous integration. The only thing you "lost" by pushing a job locally was that when viewed in the cloud portal, the mini 3D model preview in the queue was missing, and only because they never bothered making the cloud solution pull it from the printer for local jobs.
But then they also did like Bambu and killed local printing entirely because they are all enterprise-only now want to sell you their higher Digital Factory subscriptions.
Thanks for confirming.
> Being able to push prints and use the printer with direct local connection, while simultaneously having remote monitoring and remote printing when cloud/internet works and is available.
So isn't an obvious approach to just cut Bambu out altogether and just create a FOSS cloud alternative, supporting the remote aspects that the users want to retain?
> This is not the case of "wanting to have their cake and eat it too", as there is nothing mutually exclusive about these things.
Nothing technically mutually exclusive, but isn't this exactly the choice that Bambu is enforcing? Which is crappy corporate enshittification behaviour, but something they can do if they so choose? (I'm not arguing in their favour - just trying to fully clarify the situation.)
> This looks to be a clone of the prior state of the repository that caused all the Bambu drama earlier this week.
It looks like it might be a clone, but the git history is squashed for some reason.
I would recommend against installing this unless/until someone can do an audit to figure out which commit it was forked from and what the changes are.
Or better yet, find one of any of the other copies of the repository that don't have their git history squashed.
This looks like someone's attempt to capitalize on the drama to bring attention to their foundation (?) but losing git history is not a good thing for code provenance or security.
> attention to their foundation
FULU Foundation is a right to repair group, which explains their interest in this. I, for one, support them. https://www.fulu.org/our-story
I agree with your point about git history, though. https://github.com/FULU-Foundation/OrcaSlicer-bambulab/issue...
There is some context missing, which this video [0] explains.
tl;dr: The original developer does not (or cannot) go into legal battle with Bambu Lab, so Louis Rossmann's project picked up the fight and hosts the (allegedly) troublesome code on their organization. As they have more financial resources, they look forward to the C&D letter.
The point he has (and I agree with that): The original developer is using the un-modified AGPL-code to talk to the cloud API. Bambu Lab states that the modified client pretends to be a Bambu lab client. But in fact, the modified client just uses the code as-is, which is perfectly fine from a AGPL perspective. From my non-lawyer point of view: If Bambu Lab would have made the User Agent a configurable variable, which gets set by some configuration files from outside the code, that get bundled with the binary version, but not the source code, they wouldn't have this leverage.
[0]: https://www.youtube.com/watch?v=1jhRqgHxEP8
Just to confirm so I don't break anything accidentally, I currently have the app version where Bambu Studio is how I send prints to my Bambu P1S and I can look through its camera and see what filament is where and so on, but I also have the token that Home Assistant uses to watch the printer and its camera etc.
This isn't the thing you're talking about. There's a mode where I can send prints directly over the network which disables Bambu Studio, I assume?
You're missing two things from the whole picture: 1. Cloud mode works without local network access, so their server is involved in the transit of the data to the printer. This is pretty minor, but still within their rights to preserve. 2. For printing from the app, they actually run the computationally expensive slicing algorithm on their servers, so this is totally reasonable to protect.
But in this case the users want to use those features locally and are being blocked. Using a resource constraint argument doesn't make sense for it.
It seems more likely they want it as a revenue source at some point.
Pretty sure you can still print locally either via LAN or just SD card. At least I can on my A1.
The current monetization that they are using is that you can charge for a print on their platform and they take a cut of the sale. If you don’t charge for the design, then it is still free hosting and delivery.
I see where the worry is, but at the moment it seems like people are imagining a worse case scenario.
If you turn on LAN mode, it acts exactly like every other printer. You can print directly to it from any slicer over your LAN, or dump gcode on the SD card directly.
People are saying the LAN mode lacks access to the webcam and possibly some other things. That is what this whole controversy is about. It's re-enabling some cloud features as local only and Bambu is calling it privacy or fraud.
I can use the webcam in LAN mode. Just - locally, in the slicer, not the cloud-based app.
They probably want to establish a commercial-use license. If you have a big print farm, you likely need all of those remote capabilities so you're going to need to pay for the license. The schmucks at home will likely continue to get it for free. Locking them into the cloud API by dangling convenient features just ensures most people won't stray into the local-only mode.
> But in this case the users want to use those features locally and are being blocked
No, we aren’t being blocked. Turn on LAN mode, pair regular Orca slicer, ignore Bambu for the rest of eternity. Plenty of people have done it.
> No, we aren’t being blocked. Turn on LAN mode, pair regular Orca slicer, ignore Bambu for the rest of eternity. Plenty of people have done it.
You're just saying that Bambu users feel the need to purposely circumvent Bambu's artificial restrictions to be able to continue to use Bambu hardware they bought and paid for.
No matter how you frame this, this ain't right.
> purposely circumvent Bambu's artificial restrictions
It's a toggle you set in the printer directly, nothing is circumvented. Only the access through their cloud service is impacted, but the printer works locally like any other.
> 2. For printing from the app, they actually run the computationally expensive slicing algorithm on their servers, so this is totally reasonable to protect.
That's an artificial vendor tie-in, and arguably a feature that only involves their client app and their backend. It's understandable if access to their backend is restricted to a subset of their users if that's the business model they wish. Preventing paying customers from using the hardware they bought and paid for by imposing artificial restrictions is not cool.
Is it artificial though?
They've bought a machine that executes gcode and that it does (at least to my understanding) regardless of where that gcode comes from.
If you want special secret sauce gcode from the bambu cloud, you need to use the bambu cloud.
Those are not the same thing, so IMO it is legit what they do there, because it's such a clear-cut split. You own the physical thing but not the ecosystem around it.
___
I would of course personally never buy a bambu lab printer, because they're cloud-tied nonsense that was going to behave exactly like that (the split between hw and ecosystem), but other people knew that too and still bought it, because "what a nice ecosystem".
idk. I just don't think that "right to repair" should mean "right to be saved from the consequences of my own bad actions".
Those bad actions continuing to have no real painful consequences (and with that no real learnings + behavioral correction) after all is why the state of tech has become as bleak as it is right now.
And, honestly, if you can afford a bambu premium machine, there's a 97% chance that you could easily shoulder a total write-off. There's also a 97% chance that your ego can't, but that's the main thing causing all the bad things in the world and should've died a long time ago. Approximately post-highschool.
Nice post. May I ask what you would buy instead (e.g. for the P1S)?
Personally I'd be fine with the LAN mode assuming I don't have to use their cloud even once.
> What users want...
Take a step back. What users want is to be able to use the machine they bought the way they want. The outrage is because Bambu are doing a bait-and-switch: selling an autonomous 3D printer, but switching to a 3D printing service. Enshittification pure and simple.
I don't think they baited and switched? I bought my P1S before the whole LAN mode debacle and even then it was all or nothing on the cloud. I just went with the cloud because they were using some IGMP stuff for the local connection, but I had the printer on a separate VLAN and pfsense IGMP proxying was broken.
A different way of looking at it is that Bambu is saying if you want to use their cloud you have to send everything through their cloud. Stupid? Sure. It's very much a technically solvable problem. But I don't think there was any rug pull (this time; in Jan 2025 they tried...)
I think this is all more out of incompetence than malice. Something bad happens, exposing wildly inadequate programming expertise, they panic and over correct, and the community pushes back. They're great at making 3D printers, terrible at cloud infra.
For me, I want to use orca for slicing there are many more additions to the local code. As both orca and Bambo are from the same open source, the current limitation in the Bambo version is breaking the licensing of the application, and my rights in that software are broken by this addition. Then, during the print, I'm really happy to use the handy app to monitor the progress. This use case was supported when I got the hardware. Now I have to disable the app to get the slicer. I actually like to use both slicers to compare and see progress. They are also terrible at software licensing, don't understand what open source is, and they found their main software on that. They probably should embrace the orca community and use their research for their own customers. Better slicing helps everyone.
> where the device displays a token and you put it into your app.
This sounds really unpleasant to use. Maybe users just want a better UX for the local mode?
I believe it's a one time pairing code, not each print. FWIW I like the design.
It's more of an API key that whatever client or code you're using needs.
it uses MQTT, FTP, and RTSP. the key and serial are the credentials.
Why should I have to send all my prints to Bambu when the printer is sitting right next to me? Why do I have to choose between being able to stop my printer remotely or Bambu not tracking my every move, when it's trivial to have both?
it's because you're the product and they want the designs i think
I don't think so. They can already track popularity very effectively because they control makerworld, and they could have Bambu studio, the app, and the printer phone home too. I don't think they care enough about the tiny tiny minority of users running orca with a LAN only printer.
More likely, it's technical incompetence. It's just easier (for their cloud) to send everything through their cloud
I think OP meant designs which are not on MakerWorld. And I think technical incompetence is not a reason here otherwise they wouldn't gatekeep the access so much.
> clients can send prints locally
Using an AGPL violating mystery meat binary plugin that you run on your host, which potentially compromises any airgap you put around your printer (it attempts to connect to bambu servers, or did last time I checked it) and potentially your entire host.
No, the binaries aren’t necessary in LAN + Developer mode.
Correct - you can send prints over MQTT
Yeah, I have most the 'cloud' functionality all done 100% locally through home assistant. Its been pretty comfy.
Thanks for the cluestick!
Can you read the filaments installed in the printer over MQTT too?
Yes
Here's a good resource: https://github.com/Doridian/OpenBambuAPI
> (...) I don't see the current system as particularly bad and find the appetite to restore "untrustworthy" cloud functionality a bit amusing.
This is a very dubious opinion to hold. Taking your claim about local mode at face value, there is absolutely no reason to disable monitoring when working on LAN mode. You need to go way out of your way to implement that restriction so that it works differently when the thing phones home or not. You are free to criticize implementation decisions that you feel make it "untrustworthy" but those are trivial to address if you think about it.
I really recommend you to reassess your whole philosophical stance on having corporations prevent you from using what you bought and paid for.
Found the corpo cuck
A lot of the distrust toward Bambu is because they originally announced cloud auth would be required even for printing locally in LAN mode, and only backpedalled on that when they saw the backlash.
I'm not sure why their entire domain has been excluded from archive.org but you can still see the original post for now: https://blog.bambulab.com/firmware-update-introducing-new-au...
--
Critical Operations That Require Authorization The following printer operations will require authorization controls:
Binding and unbinding the printer. Initiating remote video access. Performing firmware upgrades. Initiating a print job (via LAN or cloud mode). Controlling motion system, temperature, fans, AMS settings, calibrations, etc.
> I'm not sure why their entire domain has been excluded from archive.org
Because they have a track record of altering their website, gaslighting the community, and then getting caught through archive.org so they simply blocked it, not realizing that other archives exist and then getting caught again.
They tried to alter their warranty terms and got caught. They altered their ToS which would allow them to block prints until the printer firmware was updated. When the community got upset, they not only backpedaled but altered the associated blog post and accused everyone of spreading baseless misinformation because "it's clearly explained in this [edited, backdated] article".
That's precisely the article you linked to. See the original version:
http://archive.today/2025.01.16-173123/https://blog.bambulab...
>I'm not sure why their entire domain has been excluded from archive.org
Think about why they'd make such a request to archive.org.
Reminder about the way Ubiquiti does this, as a vendor who wanted to provide users remote access to their own devices behind NAT: Unifi Cloud handles the auth and connection brokerage through a public portal, but you’re then connected straight to your own gear using your web browser (or one of the apps, if you choose). I can even turn all this off if I want to handle the remote access side of it myself.
Other vendors take note !
The important part here is not just printer support, but whether users can keep using hardware they already own without depending on a vendor cloud path.
Local network support tends to look like a convenience feature until it disappears. Then it becomes obvious that it was part of the ownership model.
> whether users can keep using hardware they already own without depending on a vendor cloud path.
That’s a complete misunderstanding of the current state of affairs. Bambu didn’t take away local network support, and you can use any Bambu printer without any cloud or internet connection.
What you can’t do is use a 3rd party slicer with their cloud servers…
> Bambu didn’t take away local network support
Yes they did. Chronology is important because it speaks to their motives. First they blocked Orca slicer and others from connecting to the printer even when the printer is running in LAN-only mode. Due to extensive backlash they later split "LAN mode" into "Standard mode LAN mode" and "Developer mode LAN mode".
The former, officially recommended, "secure" mode would prevent Orca slicer and others from using the printer.
"Developer mode LAN mode" dropped all form of access control (including existing access code + serial number pairing mechanism), leaving users completely exposed - any device on your network, and any process on your machine can freely take control of the printer. They simultaneously absolved themselves of all customer support responsibilities for anyone using this mode.
They also abandoned all work on features and bugs related to LAN mode (whether they affect standard mode or developer mode). Bambu Slicer is plagued by basic connectivity and usability issues that only affect LAN mode, feature parity is not there and there's been quite literally zero activity on any of the issues I've been following.
https://www.fulu.org/
https://www.youtube.com/watch?v=1jhRqgHxEP8
That’s a vibe coded AI slop website if I’ve ever seen one. It even has a careers page that they didn’t try to edit out.
There’s basically no information there. Is this just a copy of the other GitHub repo that was removed and someone is trying to rebrand it as their own? Or did they do some different work?
That’s an LLM generated website if I’ve ever seen one
the explanation for that is here https://youtu.be/II2QF9JwtLc
basically louis found that not using AI to design his website drastically reduced the hits he would get from google.
Wait, why would the method in which the HTML that Google indexes was generated matter?
(I get that web vitals might be taken into account, but you don't need a slop generator to make a static page)
From what I gathered from (part of) the video, it's not about the HTML, it's the copy. Basically Google is accidentally/intentionally optimizing for copy that sounds like it came from an LLM or a LinkedIn lunatics post.
I'm skeptical but I don't have time to watch the entire video so I don't want to cast an initial judgement on if he's correct or if it just has to do with his specific copy.
It's not about the HTML. It's about the wording of the content. The more he had AI reword things, the better his ranking became.
google search evaluates based on their content and how they look. apparently, according to louis, AI generated websites get a higher score.
Makes sense, since AI is also doing the ranking.
It’s still AI slop, even if your favorite youtuber built it.
yes, but that is not the problem here. the problem is that google search favors AI slop that makes this the preferred method of webdesign.
there is a huge difference between creating AI slop because i am lazy (which i think most people doing that are) and creating AI slop because otherwise google gives your website a bad rating.
now you and i may not care about google ratings, but many other people do, and the end result will be that all websites that want good ratings will end up being AI slop.
somehow we need to send google a message to stop that.
> somehow we need to send google a message to stop that.
...
The Google excuse doesn’t even hold water when you consider that the content of the website is so bad that it’s not even going to register for the relevant search terms. It’s just empty AI slop copy.
What are they even trying to rank for? It doesn’t make sense.
That doesn't excuse the fake careers page
i think it does. you have to think through the development process here. if we start with the promise that an AI generated site gets more hits, then you'd want to change as little as possible from what the AI generates by hand. yes it's dumb, but the whole premise of generating a website with AI is dumb to begin with.
i'd say that when louis discovered that AI websites work better, it broke him in that regard. the choice is now creating a website that i own, as in "this is mine, i made this". or a website that works with google. but i'd want to distance myself from that website as far as possible. "i didn't make this myself, i needed this for google. i don't want to touch it"
It's not fake? Why do you think it is fake?
Because there's no jobs? No apply button? Nothing actually there except a few lines of text?
Maybe they don't have any openings at this time.
I considered buying bambu lab A1, bout watching this and previous dramas I rather go with different vendor. Are there any good alternatives for newcomers? I like hacker nature and openness of Prusa, but I’m worried if it is good printer as a first one…
Prusa printer are really good. Well at least a few month after the first release :D They tend to release banana products that ripe at the customers.
But for example I had some problems with my linear rods, talked to support for just a few minutes and 2 days later I had replacement parts at my door. This was a few years back though.
Also they give firmware updates, and even hardware upgrade for years! This IS really nice and I'm not sure any other printer manufacturer that sells to private people does this.
Yes, your upfront price is a bit higher. I say it's worth it.
I got a second hand Prusa Mk3s about a year ago as my first printer, around 300 € perhaps. I'm still enjoying it a lot, even though I'm now eyeing one of their upcoming (more expensive) models.
I think it depends mostly on how you expect to use it. There may be alternatives that give you perfect prints with minimal fuzz. But for me it was great to have a machine I dare play around with. Like getting a tractor before a race car :)
I've only had one Prusa printer, a MINI+ and it's been an absolute workhorse and easy to repair using the official instructions (I assembled my unit myself and pulled a zip-tie too tight, which caused the part cooling fan cable to break). You do pay a premium. I, personally, also found PrusaSlicer to have better presets and usability than OrcaSlicer or it's forks.
it honestly depends on your budget. prusa is definitely overpriced for what you get. but, i bought one anyway specifically because of their stance on OSS, and this kind of bullshit the bambu is pulling. even though bambu objectively has a better or at least equal product for significantly less money.
You have to consider that you do not own the product from bambu.
So to say you spend significantly less money for a product that will be changed whenever bambu sees fit to whatever extend they see fit.
I regret my bambu purchase a lot. I have to keep up with all the ways bambu wants to lock in my hardware and take it basically away from me.
Less money because you get significantly closed product likely susbidised by state to dominate the open competition.
Just make sure never, ever to buy from them again. It's the same story as Synology with their forced reliance on specific hard drives. As long as there are still other providers out there...
Synology works with any hard drive. I bought a new unit and installed WD drives in it. No issues.
They did revert this because of public backlash:
https://arstechnica.com/gadgets/2025/10/synology-caves-walks...
What is Bambu’s motivation here? What do they get for damaging their credibility like this? Just usage data? Training a model on everyone’s STL files?
Wild speculation here obviously, but it could be a regulation play--there's a lot of potential legislation that would regulate what you can legally 3D print, which would warrant a system to be the age-verification equivalent for 3D printing.
If this is the angle then I'm even more suspicious that they're secretly pushing for the legislation so when it goes into effect they'll effectively be the only game in town.
This is admittedly a bit tinfoil hat, but they wouldn't be the first company to attempt to legislate away the competition.
I've wondered the same thing because lately I've noticed a bunch of consumer companies forcing cloud-required models where it's not necessary and many/most users have no need for whatever features cloud connectivity may provide. Yet the companies keep insisting on it even when there's significant user blow back and bad brand PR. When they even bother to comment on "why", the answers never make much sense.
When it's companies based in the U.S. or EU, like Chamberlain / LiftMaster garage door openers, it's pretty obvious they plan to monetize some cloud services subscription for upgraded features beyond the free basic tier as well as probably selling consumer data.
However, the China-based companies like Bambu Lab (and many others) are more puzzling because meaningful ongoing subscription revenue seems unlikely. Especially in the case of lower-end consumer tech peripherals where the companies usually invest as little as possible in their websites, ongoing feature updates or direct end-user support. Which makes no sense if they really aspire to build long-term subscription revenue. Here's my theory: the Chinese government is quietly compelling them to require cloud connections to China-based data centers as a long-term strategy.
I'm not even saying the companies are some direct arm of the Chinese government or planting nefarious firmware. I think that's too likely to be caught if done at mass scale and it's not even necessary. As long as the cloud servers are in Chinese data centers, the Chinese government can get consumer IP addresses and usage data just from passive packet sniffing and if things turn icy with some foreign countries, they can cause a lot of turmoil simply by selectively blocking packets at the firewall to brick millions of consumer devices.
I know it maybe sounds paranoid and, to be clear, I'm not claiming Bambu Labs specifically is doing this. I actually came up with this theory before I ever heard of Bambu Labs because I have a lot of inexpensive Chinese home automation devices and was surprised by their bizarre insistence on forcing cloud connectivity despite there being no apparent business model incentive and these smaller-scale Shenzen hardware companies showing zero enthusiasm for making a real business out of cloud services. Their cloud implementations are almost invariably the bare minimum possible and seem woefully underfunded. After all, for a low-margin hardware peripheral, every dollar spent running a no-revenue cloud after the sale is pure overhead in a business that live or dies by pennies. It's almost like requiring a cloud connection is an export tax the company is paying just to be left alone to sell their hardware overseas.
For home automation gear, cloud-connectivity is a non-starter in my book. In some cases, it's literally built into our walls, so I only buy devices which will work on a local-only subnet or on which I can install open source firmware like Tasmota or ESPHome.
>lately
it's been going on since the fucking cloud-into-everything fad started ~15 years ago
This. No conspiracy tin foil hat bs, just money. Everything got cloud because investor story time, just like everything has AI now, in every talk I have with either my boss, potential partners and clients its: “where is the AI”? (Source: i am in China). There are a couple of other things that other can maybe highlight, like how every one is blocking Chinese IP’s and vice versa, maybe something on the legislative side also? Not sure. Something something malice/incompetence
Probably regulations, there are a few states trying to make it illegal for felons to own 3D printers by EOY. These things are about to get regulated like firearms, which is wild.
More strictly than firearms, in fact.
Some of the proposed 3d printer laws will require printers being sold to be capable of evaluating what you are using them for and blocking “bad” usages. I’m not aware of any such legislation around firearms.
Bambu had any credibility to lose? Isn't this behavior exactly what was expected from them?
People just ignored it because, shiny!
Squashing the git history is not cool.
Presumably the original dev that implemented the changes for this functionality that pulled the repo does not want to be associated so some level of squashing was required but yeah, the whole history was maybe a bit silly.
> This version of OrcaSlicer restores full BambuNetwork support for Bambu Lab printers
I thought that was the point, that people didn't want to be tethered to their servers?
People want the option.
There are many reasons one might prefer OrcaSlicer over Bambu Studio. One might be perfectly fine using Bambu's cloud services while preferring OrcaSlicer for different reasons; this is for those people.
Others might not want to use Bambu's cloud services at all; OrcaSlicer as it currently exists is fine for them.
this is it for me
i bought the dang thing, let me decide how I use it.
> i bought the dang thing, let me decide how I use it.
Amazing how controversial this statement is here in 2026.
there's not enough appeal with the investors and stock holders.
they're going to try to make everything you have a subscription, starting with the homes you might try to buy. they don't even live here, but there's no laws stopping them, because your representatives personally benefit from letting things go for certain corporations/people (the same thing after the Citizens United decision)
People want remote access to their printers, a feature which seems to be tied to Bambu servers.
I have an Ender3 that I use plugging in a microsd card to do prints with. What am I missing here? Seems like you can do the same with these printers. People want to use the cloud?
Even with an Ender3 many, including myself, would connect it to a raspberryPi with octoprint to be able to send prints over the network. The SD card flow gets very tedious very quickly.
Oh god. OctoPrint, I forgot about that tool. Jesus, I'm still subscribed after all of these years. I do not want to know how much money I have been quietly bleeding for this tool.
Subscribed? It's just free software that you can put on a Pi or something. Not sure what you'd be paying for.
The creator has a patreon[1]. I did a one-time payment too because early on it really changed how I used my 3D printer and thought it deserved some support.
[1] https://octoprint.org/support-octoprint/
I think people like having an option for remote over the network communication. The cloud is not technically required for that. Bambu made it required for no good reason.
Doesn’t it have a lan mode?
Yes, and aside from being able to send and monitor your prints from their mobile app (and there are third party implementation of a similar app), you really don't lose much by using LAN Mode, especially if you pair it with Tailscale.
The mobile app is quite nice. Print error and print finish notifications. Webcam view when I’m not near my printer. The ability to pause it remotely if something looks off.
I use LAN mode, plus a home assistant plugin to restore the lost functionality. The default webcam is pretty bad so I’ve also mounted a better one to my printer for a live video view that’s at more than 1fps.
The main thing I’ve lost by using lan mode is printing from my phone? I think there are ways to do that. But OrcaSlicer has so many options that are frequently worth adjusting over random presets other creators used; it’s a strictly better experience compared to printing on mobile.
I think there is some niche “cancel printing of one specific object” feature that I dont know how to use without the mobile app. If you are printing many objects at once, and one fails, you can cancel a specific part/object using the mobile app. Not sure how to do that with OrcaSlicer + lan mode, or if it’s even possible. (Edit: OrcaSlicer doesn’t support it. The home assistant plugin might? Bambu studio in lan mode doesn’t support it either, it requires the mobile app)
I can imagine not having to do the “save to sd card, eject, put in printer, fiddle with the printers crappy ui to select the print” flow might be attractive to some. Find the model you want in the web, click “send to printer”, done.
I don’t mind the sd card thing, also happy with my bottom of the barrel ender 3.
I have an Ender 3 too. And I have a Bambu machine - that I leave offline and use via microSD card as the Ender got me used to.
I get it. The convenience of networking - when it works FOR the customer - is great.
But networking controlled by corporations is a path to enshittification.
At least your use case would be served well by enabling LAN mode, which doesn't let the printer talk to the internet, even if you want it to (and I want mine to).
The problem is trust. I don't want to get into an adversarial relationship with my printer over networking.
I could enable LAN mode and trust the mode does what it says.
I could trust others firmware reverse engineering to verify LAN mode does what it says.
I could isolate it on it's own wifi and I could block it at the home firewall from accessing the internet, to be sure.
But it was easier to simply leave it off my network.
Yeah, fair enough. I have a VLAN with no Internet access for those devices, it's convenient.
It was a mistake by BambuLab to piss off and alienate the community. They poked the bear; stung the bee; squashed the frog. This is literally the Barbara Streisand effect in the modern era. Now people are watching. Reputation went out the window already: "If they can sue one of us, they can sue all of us". (Well, threaten to sue at the least, aka applying financial pressure on that developer.)
Imagine if traditional printers were this big of a pain to use… oh
Incidentally, almost all color 2D printers insert serial number tracing artifacts, and many 2D scanners and photo editing software prevent manipulation of images containing either EURion constellation circles or Counterfeit Deterrence System patterns. Interestingly, I didn't have a problem downloading, manipulating, or attempting to print currency-detected fragment images on iPadOS 18.x.
As long as 3d printers are less than 50% harder to use than normal printers, they're dimensionally easier per capita.
For a moment I thought this was a way to get cloud printing restored to bambu printers without leaving lan-mode, would have been nice
If Bambu Lab responds to this criticism with lawyers instead of clear technical answers, it will only make the forced cloud requirement look more suspicious.
To me, this is an obvious security risk. These printers are often used in labs, startups, engineering teams, and potentially even government environments. If print data, models, logs, or usage patterns are routed through a company controlled infrastructure, that creates a real opportunity for corporate espionage or data harvesting.
I would not be surprised if Bambu Lab eventually faces the same level of scrutiny that Huawei network devices did.
I’ve been running mine offline for years, I don’t know why other people haven’t been. They’re the only competent and reliable printer that isn’t a project car in itself, but they’re obviously not completely trustworthy. Easily fixed with an air gap, updates work just great from a USB drive.
They are an adversarial player in the market, actively trying to lock users into an ecosystem that is incompatible with other printers.
Like Adobe's 'creative' software and Onshape, they are working as hard as possible to make YOU pay more to have less.
As long as Onshape let THEIR servers work for MY public projects for free I don't see how your "make YOU pay more" statement applies.
I tried it but switched back to the online mode because being able to remotely check in via the app is very useful to check the print hasn't failed.
Bambuddy and tailscale was my solution to losing access to mobile app once I went lan-only. Has video stream ,monitoring and control. Plus home assistant integration via MQTT. Only thing I’m missing is the ‘AI’ spaghetti monitoring. But those are rare for me.
There's also the Openbu or LanBu android apps if you just want a basic app for monitoring from your phone like Bambu Handy did. Although if you want to access your printer from a remote network you'll still need tailscale or similar.
Another feature locked behind the app is individual part cancelling which is nice for partial print failures.
Mine is now offline.
But when it was online, I never checked the app for failed prints. If the print has failed, I'll find out when I'm near enough to it to do something about it.
When offline, it amused me when there was a "hairball" and the printer detected it advising "AI Detecting Print Error".
At what level does an image analysis algorithm become "AI"?
If the print has failed you can stop it from the app to prevent it becoming a huge mess and possibly causing damage to the printer.
I'm curious what concise phrase you'd display to convey the same information to that audience.
"Computer Vision Model and Nozzle Telemetry Analysis Detect Print Error"?
"Print Error Detected"?
I laughed pretty hard at this, and you're right. Problem solved.
“Print Error Detected (Maybe?)”
This isn’t a PC Load Letter we can trust!
> They’re the only competent and reliable printer that isn’t a project car in itself
Prusa.
Yeah I’ve had one, still do, it never gets used because it’s a project car. Compared with one button press and coming back to a print in a few hours, it’s a constant nightmare of debugging, print issues, and manually changing filaments that aren’t stored in an airtight container and get wet. It’s not even competition, as much as I would like to support open source tools the Prusa stuff is an order of magnitude more expensive than a A1 Mini that will make a reliable print every time.
It’s like saying a bicycle is a serious contender to a train, they both have kind of similar things going on but you’d have to be insane to suggest that they do as good of a job as one another at the things people actually want to achieve.
I've done zero debugging on my Prusa and it's been pretty much fire and forget. I had one spaghetti print failure in years on it, and it was my own fault for disabling supports and the print falling over :)
Automatic filament changes would be nice for sure, I look forward to upgrading to one of their new INDX models.
idk, my 10 year old makerbot 2 has been pretty reliable, ever since Prusa slicer came out and I tuned a profile for it maybe 6 years ago it's been spitting out quick dimensionally accurate prints. i use it all the time, probably go through a spool every month or two and all i've had to replace is the cooling fan for the extruder once
i'm mostly printing small mechanical parts and i can't say i have any complaints, i assume a modern prusa would be much better, surely there are other FDM printers that are good?
Two words: Good luck!
At this poting BL is just like USA tech companies, touch their food and you are toasted. Sell your printer while you can get the its worth back.
Our food toasts people when touched?
That was my takeaway; TIL. Perhaps a "USA tech compan(y)" will productize this.
I like toasts. Taste better than people.