Bambu Lab Authorization Control System: Difference between revisions

Line 31:

== Issues with LAN Mode Requiring Authorization ==

Before recent firmware updates, Bambu Lab printers had the ability to be controlled over LAN without requiring cloud services or authentication with manufacturer. This allowed users to integrate their printers into private networks & maintain full control without having to rely on the manufacturer's server. However, the new authorization system mandates that even LAN-based operations go through an authentication process using Bambu Connect<ref>https://wiki.bambulab.com/en/software/bambu-connect</ref>.

Before recent firmware updates, Bambu Lab printers had the ability to be controlled over LAN without requiring cloud services or authentication with manufacturer. This allowed users to integrate their printers into private networks & maintain full control without having to rely on the manufacturer's server. However, the new authorization system mandates that even LAN-based operations go through an authentication process using Bambu Connect<ref>https://wiki.bambulab.com/en/software/bambu-connect</ref> which is unnecessary.

This change has drawn criticism for many good 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.

* '''Loss of Offline Independence''': Before, users could have entirely 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.

* '''Increased Complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control<ref>https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643</ref>.

Line 75:

=== Permanent Nature of the Update ===

Once a printer is updated to the new firmware, users cannot revert to previous versions that ~~allowed~~ fuller third-party integration. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.\

Once a printer is updated to the new firmware, users cannot revert to previous versions that allow fuller third-party integration. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.\

The manufacturer states this change is required for security, but community members note that many of the security vulnerabilities being addressed stem from Bambu's own cloud-centric design choices rather than inherent risks of local network control<ref>https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/12</ref>. The update forces users into Bambu's ecosystem of applications & cloud services, regardless of their preferences or needs for local network automation.

Line 94:

Previously, third-party software such as OrcaSlicer<ref>https://github.com/SoftFever/OrcaSlicer/issues/8063</ref> could interact with Bambu Lab printers via the open-source Bambu Studio and proprietary network plug-ins. While Bambu Connect provides a limited URL-based API to initiate prints, most functionality previously openly available is now restricted to Bambu's ecosystem<ref>https://forum.bambulab.com/t/this-new-auth-system-will-make-me-sell-my-printers/135400/9</ref>.

Previously, third-party accessories such as Panda Touch would ~~be able to give~~ users ~~the ability~~ to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D pad by default for printer control whereas Panda Touch is a full-color touch screen that had a small battery so that way users could reposition and detach their Panda Touch off their printers if needed. Users would be able to queue up jobs, jog printer motors, and connect to multiple printers at once in order to monitor print jobs. According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch to ~~not~~ update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch. <ref name=":0" />

Previously, third-party accessories such as Panda Touch would allow users to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D-pad by default for printer control whereas Panda Touch is a full-color touch screen that had a small battery so that way users could reposition and detach their Panda Touch off their printers if needed. Users would be able to queue up jobs, jog printer motors, and connect to multiple printers at once in order to monitor print jobs. According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch not to update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch. <ref name=":0" />

== Communication with Panda Touch Developers ==

Line 115:

This approach has been interpreted by many as a calculated move by Bambu Lab to enforce tighter control over its ecosystem. Primary criticisms of Bambu were:

* '''Lack of Transparency''': The limited warning to OrcaSlicer devs suggests that Bambu Lab prioritized internal rollout schedules over community engagement with existing customers.

* '''Lack of Follow-Through:''' As of writing, SoftFever, OrcaSlicer's lead developer, still does not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Bambu's original announcement prominently mentioned OrcaSlicer and gave the impression that Bambu is actively providing the necessary assets so that SoftFever would be able to implement the new software architecture so that OrcaSlicer users are able to still use OrcaSlicer to send gcode to their printers without needing Bambu Connect to be installed as a separate program. The lack of active cooperation does not reflect favorably upon Bambu as it seems like ~~that~~ their announcement used OrcaSlicer's name to try to make it seem like ~~that~~ Bambu is trying its best to make sure that developers have what they need, but in reality, their inaction seems to show that Bambu is not making a sincere attempt to ensure that OrcaSlicer remains supported. <ref name=":1" />

* '''Lack of Follow-Through:''' As of writing, SoftFever, OrcaSlicer's lead developer, still does not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Bambu's original announcement prominently mentioned OrcaSlicer and gave the impression that Bambu is actively providing the necessary assets so that SoftFever would be able to implement the new software architecture so that OrcaSlicer users are able to still use OrcaSlicer to send gcode to their printers without needing Bambu Connect to be installed as a separate program. The lack of active cooperation does not reflect favorably upon Bambu as it seems like their announcement used OrcaSlicer's name to try to make it seem like Bambu is trying its best to make sure that developers have what they need, but in reality, their inaction seems to show that Bambu is not making a sincere attempt to ensure that OrcaSlicer remains supported. <ref name=":1" />

* '''Disregard for Open-Source Collaboration''': OrcaSlicer is widely used in the community; it is an open-source effort to improve the 3D printing experience for all customers. By abruptly altering the compatibility landscape, Bambu Lab is seen as undermining good-faith initiatives to improve the ecosystem for everyone. The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect represents a broader industry trend of closing off ecosystems that were once open, removing customer choice, privacy, & freedom.

* '''Token Support for Third-Party Tools''': While Bambu Connect provides a workaround for third-party slicer use, it significantly restricts functionality & complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools.<ref>https://wiki.bambulab.com/en/software/bambu-connect</ref>

Line 144:

ChazLayyd's Bambu Lab Klipper Conversion project is currently in an incomplete stage. <ref>https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion</ref> <ref>DhazLayyd's Discord Community

https://discord.gg/W6B5mBejuC</ref> While it was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that ~~runs~~ Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.

https://discord.gg/W6B5mBejuC</ref> While it was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that run Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.

=== Advocacy for Open Ecosystem Support ===

Line 248:

# '''Reduced Functionality''': Features like remote monitoring, advanced slicing options, & integration with custom setups are no longer possible, which impacts small businesses & advanced users.

# '''Privacy Risks''': Users' print data, including designs & settings, are now processed through Bambu’s cloud servers, giving the company access to information on how users use their hardware.

# '''Locked Hardware''': If a user disagrees with these changes, they can’t simply switch back to the older version software—they're stuck with the new version & locked into Bambu’s system.

# '''Locked Hardware''': If a user disagrees with these changes, they can’t simply switch back to the older version of software—they're stuck with the new version & locked into Bambu’s system.

# '''Reduced resiliency''': In an emergency where internet access is lost, the 3D printer cannot be used to create items ~~which~~ may be used to repair or replace items vital to an emergency response. This functionality is vital for small and or remote households and communities.

# '''Reduced resiliency''': In an emergency where internet access is lost, the 3D printer cannot be used to create items that may be used to repair or replace items vital to an emergency response. This functionality is vital for small and or remote households and communities.

== The Bigger Picture ==

@@ Line 31: / Line 31: @@
 == Issues with LAN Mode Requiring Authorization ==
-Before recent firmware updates, Bambu Lab printers had the ability to be controlled over LAN without requiring cloud services or authentication with manufacturer. This allowed users to integrate their printers into private networks & maintain full control without having to rely on the manufacturer's server. However, the new authorization system mandates that even LAN-based operations go through an authentication process using Bambu Connect<ref>https://wiki.bambulab.com/en/software/bambu-connect</ref>.
+Before recent firmware updates, Bambu Lab printers had the ability to be controlled over LAN without requiring cloud services or authentication with manufacturer. This allowed users to integrate their printers into private networks & maintain full control without having to rely on the manufacturer's server. However, the new authorization system mandates that even LAN-based operations go through an authentication process using Bambu Connect<ref>https://wiki.bambulab.com/en/software/bambu-connect</ref> which is unnecessary.
 This change has drawn criticism for many good 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.
-* '''Loss of Offline Independence''': Before, users could have entirely 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.
+* '''Loss of Offline Independence''': Before, users could have entirely 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.
 * '''Increased Complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control<ref>https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643</ref>.
@@ Line 75: / Line 75: @@
 === Permanent Nature of the Update ===
-Once a printer is updated to the new firmware, users cannot revert to previous versions that allowed fuller third-party integration. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.\
+Once a printer is updated to the new firmware, users cannot revert to previous versions that allow fuller third-party integration. This creates a one-way transition that permanently removes capabilities users had when purchasing their printer. While Bambu Lab presents this as optional for existing users, all new printers will ship with the restricted firmware pre-installed, eliminating user choice entirely<ref>https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</ref>.\
 The manufacturer states this change is required for security, but community members note that many of the security vulnerabilities being addressed stem from Bambu's own cloud-centric design choices rather than inherent risks of local network control<ref>https://forum.bambulab.com/t/bambu-studio-1-10-2-public-beta/134549/12</ref>. The update forces users into Bambu's ecosystem of applications & cloud services, regardless of their preferences or needs for local network automation.
@@ Line 94: / Line 94: @@
 Previously, third-party software such as OrcaSlicer<ref>https://github.com/SoftFever/OrcaSlicer/issues/8063</ref> could interact with Bambu Lab printers via the open-source Bambu Studio and proprietary network plug-ins. While Bambu Connect provides a limited URL-based API to initiate prints, most functionality previously openly available is now restricted to Bambu's ecosystem<ref>https://forum.bambulab.com/t/this-new-auth-system-will-make-me-sell-my-printers/135400/9</ref>.
-Previously, third-party accessories such as Panda Touch would be able to give users the ability to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D pad by default for printer control whereas Panda Touch is a full-color touch screen that had a small battery so that way users could reposition and detach their Panda Touch off their printers if needed. Users would be able to queue up jobs, jog printer motors, and connect to multiple printers at once in order to monitor print jobs. According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch to not update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch. <ref name=":0" />
+Previously, third-party accessories such as Panda Touch would allow users to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D-pad by default for printer control whereas Panda Touch is a full-color touch screen that had a small battery so that way users could reposition and detach their Panda Touch off their printers if needed. Users would be able to queue up jobs, jog printer motors, and connect to multiple printers at once in order to monitor print jobs. According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch not to update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch. <ref name=":0" />
 == Communication with Panda Touch Developers ==
@@ Line 115: / Line 115: @@
 This approach has been interpreted by many as a calculated move by Bambu Lab to enforce tighter control over its ecosystem. Primary criticisms of Bambu were:
 * '''Lack of Transparency''': The limited warning to OrcaSlicer devs suggests that Bambu Lab prioritized internal rollout schedules over community engagement with existing customers.
-* '''Lack of Follow-Through:''' As of writing, SoftFever, OrcaSlicer's lead developer, still does not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Bambu's original announcement prominently mentioned OrcaSlicer and gave the impression that Bambu is actively providing the necessary assets so that SoftFever would be able to implement the new software architecture so that OrcaSlicer users are able to still use OrcaSlicer to send gcode to their printers without needing Bambu Connect to be installed as a separate program. The lack of active cooperation does not reflect favorably upon Bambu as it seems like that their announcement used OrcaSlicer's name to try to make it seem like that Bambu is trying its best to make sure that developers have what they need, but in reality, their inaction seems to show that Bambu is not making a sincere attempt to ensure that OrcaSlicer remains supported. <ref name=":1" />
+* '''Lack of Follow-Through:''' As of writing, SoftFever, OrcaSlicer's lead developer, still does not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Bambu's original announcement prominently mentioned OrcaSlicer and gave the impression that Bambu is actively providing the necessary assets so that SoftFever would be able to implement the new software architecture so that OrcaSlicer users are able to still use OrcaSlicer to send gcode to their printers without needing Bambu Connect to be installed as a separate program. The lack of active cooperation does not reflect favorably upon Bambu as it seems like their announcement used OrcaSlicer's name to try to make it seem like Bambu is trying its best to make sure that developers have what they need, but in reality, their inaction seems to show that Bambu is not making a sincere attempt to ensure that OrcaSlicer remains supported. <ref name=":1" />
 * '''Disregard for Open-Source Collaboration''': OrcaSlicer is widely used in the community; it is an open-source effort to improve the 3D printing experience for all customers. By abruptly altering the compatibility landscape, Bambu Lab is seen as undermining good-faith initiatives to improve the ecosystem for everyone. The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect represents a broader industry trend of closing off ecosystems that were once open, removing customer choice, privacy, & freedom.
 * '''Token Support for Third-Party Tools''': While Bambu Connect provides a workaround for third-party slicer use, it significantly restricts functionality & complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools.<ref>https://wiki.bambulab.com/en/software/bambu-connect</ref>
@@ Line 144: / Line 144: @@
 ChazLayyd's Bambu Lab Klipper Conversion project is currently in an incomplete stage. <ref>https://github.com/ChazLayyd/Bambu-Lab-Klipper-Conversion</ref> <ref>DhazLayyd's Discord Community
-https://discord.gg/W6B5mBejuC</ref> While it was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that runs Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.
+https://discord.gg/W6B5mBejuC</ref> While it was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that run Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.
 === Advocacy for Open Ecosystem Support ===
@@ Line 248: / Line 248: @@
 # '''Reduced Functionality''': Features like remote monitoring, advanced slicing options, & integration with custom setups are no longer possible, which impacts small businesses & advanced users.
 # '''Privacy Risks''': Users' print data, including designs & settings, are now processed through Bambu’s cloud servers, giving the company access to information on how users use their hardware.
-# '''Locked Hardware''': If a user disagrees with these changes, they can’t simply switch back to the older version software—they're stuck with the new version & locked into Bambu’s system.
+# '''Locked Hardware''': If a user disagrees with these changes, they can’t simply switch back to the older version of software—they're stuck with the new version & locked into Bambu’s system.
-# '''Reduced resiliency''': In an emergency where internet access is lost, the 3D printer cannot be used to create items which may be used to repair or replace items vital to an emergency response. This functionality is vital for small and or remote households and communities.
+# '''Reduced resiliency''': In an emergency where internet access is lost, the 3D printer cannot be used to create items that may be used to repair or replace items vital to an emergency response. This functionality is vital for small and or remote households and communities.
 == The Bigger Picture ==