Bambu Lab Authorization Control System: Difference between revisions
→Impact on third-party integration and user choice: Remove <syntaxhighlight> as this wiki doesn't seem to actually have that enabled |
|||
| Line 62: | Line 62: | ||
* <code>version</code>: A fixed value of 1.0.0 for compatibility | * <code>version</code>: A fixed value of 1.0.0 for compatibility | ||
A complete command must be formatted as: | A complete command must be formatted as: | ||
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 | |||
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 80: | Line 82: | ||
This can be characterised as a significant post-purchase reduction in functionality for existing owners who bought their printers with the understanding they could use third-party software and home-automation tools, but also only affects users actively choosing to use Bambu Cloud at the same time. The inability to revert these changes, combined with the mandatory nature of the update for new printers, is used to demonstrate how manufacturers can use software updates to unilaterally modify the capabilities of hardware products after purchase, although in this case the changes affect only people already choosing to use the cloud service<ref name="bambulab-forum-3643/9">https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/9</ref>. | This can be characterised as a significant post-purchase reduction in functionality for existing owners who bought their printers with the understanding they could use third-party software and home-automation tools, but also only affects users actively choosing to use Bambu Cloud at the same time. The inability to revert these changes, combined with the mandatory nature of the update for new printers, is used to demonstrate how manufacturers can use software updates to unilaterally modify the capabilities of hardware products after purchase, although in this case the changes affect only people already choosing to use the cloud service<ref name="bambulab-forum-3643/9">https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/9</ref>. | ||
For users that would want to use a third-party slicer while using their cloud service, Bambu would require those users to download and install Bambu Connect in order to send gcode wirelessly over LAN or over the cloud. While Bambu claims that they were in contact with SoftFever, the developer of OrcaSlicer, as of writing, SoftFever still does not have any keys for Bambu Connect and the new firmware is only available as opt-in beta at the moment.<ref name=":1">https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q&s=19</ref> | For users that would want to use a third-party slicer while using their cloud service, Bambu would require those users to download and install Bambu Connect in order to send gcode wirelessly over LAN or over the cloud. While Bambu claims that they were in contact with SoftFever, the developer of OrcaSlicer, as of writing, SoftFever still does not have any keys for Bambu Connect and the new firmware is only available as opt-in beta at the moment.<ref name=":1">https://x.com/fever_soft/status/1880630570809795034?t=qJyh4SGFZFllcYrqexGW-Q&s=19</ref> | ||
== Impact on functionality == | == Impact on functionality == | ||