Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Categories
Random page
Top Contributors
Recent changes
Contribute
Create a page
How to help
Wiki policy
Adapt videos to articles
Articles in need of work
Help
Frequently asked questions
Join the discord!
Help about MediaWiki
Consumer_Action_Taskforce
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Bambu Lab Authorization Control System
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
Purge cache
General
What links here
Related changes
Special pages
Page information
Cargo data
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Issues with LAN mode requiring authorization== [[File:Bambu Connect App - Lan Device Discovery without Bambu Login.png|thumb|Bambu Connect App - Lan Device Discovery without Bambu Login]] Bambu Lab printers have the ability to be controlled over both cloud and LAN. This allowed users to integrate their printers into private networks and maintain full control without having to rely on the manufacturer's server while also allowing cloud access. The new authorization system mandates that even LAN-based operations must go through an authentication process using Bambu Connect to retain full control.<ref name="bambu-connect">https://wiki.bambulab.com/en/software/bambu-connect</ref> Full local access is still possible and unchanged for those not using the cloud. This change has drawn criticism for many reasons: *'''Privacy concerns''': Requiring authentication for LAN mode raises concerns about data being unnecessarily exposed to Bambu Lab's servers, even for local-only operations, though previously, the printer was also connected and could be controlled by the cloud even when sending prints locally. **Confidentiality required by US Law - This is in conflict with those that have to comply with 18 CFR Β§ 3a.61, 32 CFR Β§ 117.15, 32 CFR Β§ 2001.47, and other restrictions. *'''Loss of offline independence while also using cloud''': Before, users could have hybrid offline setups. The requirement for authentication removes this option unless users revert to older firmware versions, which Bambu does not allow people to do once they have updated to the firmware using the new scheme. *'''Increased complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control while retaining cloud functionality.<ref>https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643</ref> It is worth noting that: *LAN-Only mode in Orca Slicer is implemented by passing API Calls to the installed proprietary Bambu Network Plug-In (unlike BTT and other solutions that did indeed communicate with printer directly via MQTT protocol). *Plug-In provides controls for Printers "Critical Operations" (as classified by the Firmware Announcement article) and displays these controls within the window of Orca Slicer. *Using intermediary Plug-In does not manifest as "direct access through network plugin". It is still a Proxy communication, even if user experience is presented as direct communication (same slicer window). *Bambu Connect moves the Network Plug-In functionality outside of the window of Orca Slicer thus appearing as separate window and presents the appearance of "indirect" communication channel to the printer. *While the user experience is different, the flow remains unchanged Orca Slicer slices model -> Orca Slicer Calls API of Bambu Proprietary Software -> Bambu Proprietary Software controls the printer. Additionally, Bambu Connect software (downloaded and installed on 19.01.2024 (2025?) prior to the backlash response) seems to have functionality of adding LAN-Only printers without the requirement of Bambu Account authentication (Same behavior as Network Plugin used in Orca Slicer) ===Precedents and comparisons=== Critics have likened this potential functionality to similar cases in other industries where manufacturers remotely restrict product features. Notable examples include [[HP]]'s printer firmware updates that [[HP Instant Ink|rendered third-party ink cartridges unusable]] and Tesla's software locks on second-hand vehicles. These parallels suggest a broader trend of manufacturers [[Retroactively amended purchase|using software to control hardware capabilities post-purchase]].<ref>https://www.classaction.org/hp-printer-lawsuit</ref><ref>https://www.wired.com/story/tesla-remote-disable-used-car-features/</ref> ===X1E firmware 01.01.02.00 LAN only connection "BUG"=== Newly received X1E printers with firmware 01.01.02.00 will not connect to the Bambu Studio using the Lan only method password. Bambu Studio identifies the un-logged printer but will not allow a connection to the printer. Only after connection / account paring is done over the Bambu Handy app by giving internet access to the PC and Printer then utilizing the cloud service connection will Lan only communication and login work.<ref>https://forum.bambulab.com/t/connect-x1e-to-stand-alone-computer/101474</ref>
Summary:
Please note that all contributions to Consumer_Action_Taskforce are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (see
Consumer Action Taskforce:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:
Cancel
Editing help
(opens in new window)