Bambu Lab Authorization Control System: Difference between revisions
m deduplicate <ref> |
m deduplicate <ref> |
||
| Line 29: | Line 29: | ||
== Issues with LAN mode requiring authorization == | == Issues with LAN mode requiring authorization == | ||
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>https://wiki.bambulab.com/en/software/bambu-connect</ref> Full local access is still possible and unchanged for those not using the cloud. | 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: | This change has drawn criticism for many reasons: | ||
| Line 56: | Line 56: | ||
=== Changes to third-party access === | === Changes to third-party access === | ||
The new authorization system replaces direct network API access with a more limited URL-based interface through Bambu Connect. Third-party software can only interact with the printer by sending specific URL commands to Bambu Connect<ref | The new authorization system replaces direct network API access with a more limited URL-based interface through Bambu Connect. Third-party software can only interact with the printer by sending specific URL commands to Bambu Connect<ref name="bambu-connect" />. The interface requires three parameters: | ||
* <code>path</code>: The absolute file system path to the 3MF file (e.g., /tmp/cube.gcode.3mf) | * <code>path</code>: The absolute file system path to the 3MF file (e.g., /tmp/cube.gcode.3mf) | ||
| Line 64: | Line 64: | ||
A complete command must be formatted as:<blockquote><syntaxhighlight lang="text"> | A complete command must be formatted as:<blockquote><syntaxhighlight lang="text"> | ||
bambu-connect://import-file?path=%2Ftmp%2Fcube.gcode.3mf&name=Cube&version=1.0.0 | bambu-connect://import-file?path=%2Ftmp%2Fcube.gcode.3mf&name=Cube&version=1.0.0 | ||
</syntaxhighlight></blockquote>This interface only allows basic file transfer and print initiation. All other printer-control functions previously available to third-party software are now exclusive to Bambu's own applications. The path and name parameters must be URL-encoded using encodeURIComponent or equivalent functions<ref | </syntaxhighlight></blockquote>This interface only allows basic file transfer and print initiation. All other printer-control functions previously available to third-party software are now exclusive to Bambu's own applications. The path and name parameters must be URL-encoded using encodeURIComponent or equivalent functions<ref name="bambu-connect" />. | ||
=== Reduced home-automation capabilities === | === Reduced home-automation capabilities === | ||
| Line 83: | Line 83: | ||
== Impact on functionality == | == Impact on functionality == | ||
While some functionality remains unauthenticated like in previous firmware versions (sending status information from the printer over the network, starting a print job using SD cards), the most important features now require authentication through a new closed-source client called Bambu Connect<ref | While some functionality remains unauthenticated like in previous firmware versions (sending status information from the printer over the network, starting a print job using SD cards), the most important features now require authentication through a new closed-source client called Bambu Connect<ref name="bambu-connect" />. These restricted features include: | ||
* Initializing prints via LAN or cloud mode | * Initializing prints via LAN or cloud mode | ||
| Line 116: | Line 116: | ||
* '''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" /> | * '''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, and freedom. | * '''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, and freedom. | ||
* '''Token support for third-party tools''': While Bambu Connect provides a workaround for third-party slicer use, it significantly restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools | * '''Token support for third-party tools''': While Bambu Connect provides a workaround for third-party slicer use, it significantly restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools<ref name="bambu-connect" />. | ||
* '''Power imbalance''': As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users. | * '''Power imbalance''': As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users. | ||
== Community-driven workarounds and technical alternatives == | == Community-driven workarounds and technical alternatives == | ||