Supported Printers

Supported Printers

Printbuddy supports several printer ecosystems. Support is provider-based, so choose the provider that matches the printer interface you actually use.

Supported provider families

Bambu Lab

Use the Bambu Lab provider for Bambu printers that expose local LAN access.

Supported / compatible families include:

• Bambu Lab H2 family: H2C, H2D, H2D Pro, H2S
• Bambu Lab X1 family: X1 Carbon, X1E
• Bambu Lab P1 family: P1P, P1S
• Bambu Lab P2 family: P2S
• Bambu Lab A1 family: A1, A1 Mini

Typical requirements:

• Printer reachable on the same local network.
• LAN access / Developer Mode enabled where required by the printer firmware.
• Printer IP or hostname.
• Access code.
• Serial number when required for local MQTT/FTP workflows.

Klipper / Moonraker

Use a Moonraker provider for Klipper printers managed through Fluidd, Mainsail, or another Moonraker-compatible stack.

Provider choices in Printbuddy:

• klipper
• fluidd
• mainsail

They all use Moonraker as the actual printer API.

Typical requirements:

• Moonraker URL, commonly http://<printer-ip>:7125.
• Optional Moonraker API token if authorization is enabled.
• Optional camera URL for the printer camera stream or snapshot.

PrusaLink

Use PrusaLink for printers exposing the local PrusaLink HTTP API.

Typical requirements:

• PrusaLink URL, commonly http://<printer-ip>/.
• PrusaLink username/password or API secret as required by your printer.
• Optional camera URL if your camera is not exposed through the same interface.

Current capabilities:

• Status/job polling through PrusaLink HTTP endpoints.
• Uploading sliced .gcode and .bgcode files to the printer's USB storage.
• Listing and deleting files from the printer's USB storage.
• Starting already uploaded files through PrusaLink when the printer accepts the request.
• Pause, resume, and cancel job actions where the printer exposes a current job ID.

For modern PrusaLink printers such as the CORE One, file operations use USB storage paths such as /api/v1/files/usb/<file-name>.gcode. These are not Bambu FTP paths and not Moonraker gcodes paths.

Current PrusaLink limitations:

• PrusaLink USB file download is not currently implemented in Printbuddy, so the File Manager download action is hidden for Prusa printers.
• Bambu-style print speed control is hidden for Prusa printers.
• Manual movement, extrusion, temperature-target, raw G-code, and Moonraker-style control panels are hidden for Prusa printers.
• Queue/re-slice actions are not shown in the Prusa printer File Manager for files that are already on USB storage.

Prusa Connect

Use Prusa Connect when connecting through the Prusa Connect Mobile API instead of local PrusaLink.

Typical requirements:

• Prusa Connect printer UUID.
• Prusa Connect token.
• API base URL defaults to https://connect-mobile-api.prusa3d.com.

Prusa Connect support is intentionally separate from local PrusaLink support. Cloud file workflows are more limited than local printer APIs and should not be assumed to match PrusaLink USB-file behavior.

Capability differences

Not every provider supports the same actions.

Examples:

• Bambu-specific AMS, calibration, FTP, and LAN/MQTT behavior is Bambu-only.
• Moonraker actions use Moonraker HTTP/WebSocket APIs and G-code scripts where supported.
• PrusaLink actions use PrusaLink HTTP endpoints, not Moonraker G-code transport.
• Prusa Connect cloud file workflows are more limited than local printer APIs.

If a button or setting is hidden for a printer type, that usually means the underlying provider does not safely support that operation yet.