Firmware updates are supposed to improve the hardware you already own. Bambu Lab's authorization-control firmware patches vulnerabilities, but it also changes who decides which software and accessories control your printer.
Once installed, the printer checks whether commands come from official or authorized software. That distinction matters. The update doesn't brick your printer, ban third-party filament, or make every print dependent on the internet. It does, however, remove direct network-control capabilities that owners had when they bought their machines and puts Bambu Lab in charge of the approved route back in.
Local printing survived, but the open door didn't
Bambu Connect puts a middleman in front of every third-party job
Before the authorization control update, software such as OrcaSlicer and local integrations could communicate directly with supported Bambu printers through the existing network interface. After updating, unauthorized programs can still read some status data, but critical control commands are rejected. Bambu Lab's answer is Bambu Connect, an app that passes an exported job to the printer through an authorized path.
Bambu says standard LAN mode through Bambu Connect needs neither an internet connection nor a Bambu account. Local printing, then, has not disappeared. That said, claims of something working offline and remaining under the owner's control are not the same promise. A previously direct workflow now depends on proprietary middleware, and independent software must either accommodate Bambu's system or surrender part of its integration.
The practical loss is clearest with third-party tools. Bambu's original announcement explicitly warned that updated firmware would stop unauthorized software and hardware from initiating prints, moving axes, or running calibrations. A Home Assistant setup may continue receiving MQTT status messages, for example, while losing the ability to control the machine. Accessories that relied on the same interface now face a similar downgrade.
Developer Mode is an escape hatch with a price tag
Keep the cloud or keep control, but not both
After severe community backlash, Bambu Lab added Developer Mode under LAN mode. It opens MQTT, FTP, and the live stream, disables authorization verification, and restores much of the behavior advanced users expect. The catch is that this Developer Mode is local-only and cannot connect to Bambu Cloud. It also must be enabled manually and is explicitly unsupported by Bambu Lab.
That creates an artificial choice. Owners can either keep cloud features, including convenient remote access through the Bambu Handy app, and accept Bambu's authorized software path. Or they can reclaim direct local control, give up the cloud, and assume responsibility for any resulting issues.
Before the authorization change, third-party control and Bambu's online services weren't presented as mutually exclusive options. Calling the escape hatch Developer Mode also frames ordinary local ownership as an advanced, risky exception rather than a normal capability of the hardware you already paid for.
Staying on an older firmware isn't a solution either. It preserves existing workflows, but it also means skipping newer security fixes, bug patches, and new features. Bambu itself acknowledges that trade-off while encouraging users to update. A choice between secure current firmware and the integrations a product supported at purchase is technically a choice, but not a very consumer-friendly one.
Security is a fair goal. Making Bambu the gatekeeper isn't
Section 7.4 reserves leverage over hardware you already paid for
Bambu Lab does have a legitimate security argument: a network-connected machine contains heaters and fast-moving parts. Authentication, encrypted communications, signed updates, and safer defaults are reasonable goals. The problem is not that Bambu secured the printer; it's that the company secured it by making itself the gatekeeper instead of offering a documented, owner-controlled authorization method.
Its terms of use further add to this concern. Section 7.4 says products may automatically search for and download update packages and may block new print jobs before an important update is installed. Bambu says firmware installation remains the user's choice, and there's no evidence that it plans to start disabling printers out of the blue. Still, the written policy reserves leverage over future use of hardware customers already paid for.
The printer you bought isn't the one you have now
Offline printing still works, but interoperability took the hit
This is why the controversy is bigger than one slicer or accessory. A Bambu printer with the new firmware can still print offline, and Developer Mode keeps a path open for tinkerers. But the default product is less interoperable than it was on the day you bought it.
You must now choose among proprietary mediation, reduced cloud functionality, or aging firmware. That is not a catastrophic loss of functionality, but it is a reduction of capability — and a reminder that connected hardware can change after it enters your home, even when the metal and motors remain entirely yours.