Skip to content
thereprocase / All projectsHOME-AUTOMATIONSource on GitHub ↗

BAMBU BRIDGE / LOCAL PRINTER TOOLS

Your P1S.
One shared endpoint.

Print from Orca with the AMS or external spool, watch the camera, and connect your phone and Home Assistant through one bridge.

Run the bridge on your own server. Reach it over your LAN or Tailscale; it talks to the printer on the printer’s local network.

Independent community software. Not affiliated with or endorsed by Bambu Lab.

Actual Bambu Bridge viewer showing a gold sample vessel at layer 186 of 300Open full image ↗
ACTUAL VIEWER / Synthetic model and sample progress. The solid region follows the reported layer; the ghost shows the remainder.
LAN

Your printer, connected with its access code.

3D

See the current layer in the context of the whole job.

API

Share one bridge across your local clients.

Orca · one P1S endpoint

Four colors from the AMS. Or a job from the external spool. Use the same printer entry, address and native access code in Orca for both.

Bambu Bridge presents your P1S to Orca over a private LAN or Tailscale connection. Upload a sliced job, select its filament source, follow printer status and view camera frames through the bridge.

AMS JOB

Map four colors to four slots.

In Orca’s Print plate dialog, map the sliced filaments to the live AMS slots. The gateway forwards that job’s mapping to the printer.

EXTERNAL-SPOOL JOB

Choose the spool outside the AMS.

Select the external spool for that print. Keep the same endpoint and code—there is no connection to swap or server setting to change between jobs.

A separate Bridge P1S, alongside your printer.

The bridge has its own persistent serial. Your physical P1S keeps its own entry, address and credentials, so local discovery cannot replace the bridge connection. Upgrading from 0.4.0 or earlier? Run a fresh setup command for the new identity.

  1. Prepare the bridge. Install the v0.6.0 preview and follow the native setup guide to select the server’s private or Tailscale address.
  2. Set up this computer. In your HTTPS dashboard, open Settings → Connect Orca to your printer and enable Orca access. On Windows, close Orca and copy the setup command. Paste it into Windows PowerShell and follow the prompts; it sets the address, code and certificate together.
  3. Open Orca and check. Select Bridge P1S in Device, press Play for the camera, then click Check this computer in the dashboard. Printer and camera have separate live checks. Manual setup remains available for macOS and Linux.

The choice belongs to the print. Select AMS or external spool in Orca, then use the Device view for printer status and the shared camera stream.

Preview with live protocol checks. Real P1S AMS/external status, camera JPEG frames, a read-only command response and file listing have been verified. Automated tests cover uploads and print-command forwarding. A completed print through the installed Orca UI remains unverified. Read the validation record.

The bridge has the Tailscale IP

YOUR CLIENTS

OrcaSlicer

Native P1S printing + camera

Browser + phone

Dashboard + 3D viewer

Home Assistant

Entities + automations

Private LAN
or Tailscale
OWNS THE TAILSCALE IP

Bambu Bridge

Looks like a P1S to Orca. Relays uploads and commands, shares status and camera frames, and serves the dashboard and API.

Printer LAN
protocols
YOUR HARDWARE

Physical P1S

Uses its ordinary local network address. Tailscale runs on the bridge host and client computer; it is not installed on the printer.

One server between your clients and the printer. The bridge shares its MQTT and camera sessions and handles file transfers as needed. Orca uses a separate native access code; the printer’s original code stays on the server. Keep native access on your private network or tailnet.

The browser workspace

Dashboard status preview: printing at 62 percent, 38 minutes remaining, temperatures, fan speeds and AMS PLAOpen full image ↗
ACTUAL DASHBOARD / Synthetic printer state. Camera and recent-job panels omitted from this status preview.

Know what is happening at a glance.

Progress, remaining time and the current layer sit above temperatures, cooling and AMS information. Pause, stop and light controls stay within reach.

  • Print state comes first. Preparing, printing, paused and finished have different status treatments.
  • Disconnected data is marked. The dashboard dims old values and shows a reconnecting message when the link drops.
  • Camera when available. The full dashboard includes a continuous camera stream and a shortcut to the 3D viewer.

Read the 3D view

The 0.6.0 browser viewer estimates toolhead motion along sliced extrusion with distance weighting and inferred straight travel. Layer animation uses reported remaining time and observed layer durations, resynchronizes on reported layer changes, and freezes while paused or offline. Position, speed and travel are inferred; this is not measured XY. Reopen the server-hosted 3D viewer after updating; no APK is needed.

Open 3D from the dashboard to orbit the job, zoom in, or scrub through layers. Return to Live to follow the printer’s reported layer.

  • Solid below, ghost above. See the reported build height against the complete model.
  • Model or sliced toolpath. Mesh geometry is shown when available; supported sliced archives can supply toolpaths instead.
  • A progress visualization. The older pictured mesh view tracks Z. In 0.6.0, sliced paths have an estimated moving toolhead; mesh views show the reported layer without inventing XY.

Viewer links can use a separate read-only visualization token, so sharing a view does not require sharing the master API key.

The Android companion

Keep live printer status, camera snapshots, filament tools, and the 3D viewer together on your phone. The app connects to your bridge over your LAN or Tailscale using the same bridge API key.

Android v0.20.1 preview · ARM64 · Android 7 or newer. Install the signed APK as an update to keep your saved connection and printer settings. A running Bambu Bridge server is required. This 3D viewer update needs no new APK.

Two ways Home Assistant fits

Integration: bring the printer into HA.

The custom integration connects to your existing bridge using its base URL and API key. Each registered printer becomes a device with status, temperature and progress sensors, a camera and controls.

Use those entities and bridge events in your own dashboards and automations—for example, a notification when a print completes.

Add-on: host the bridge inside HA.

The Supervisor add-on runs the bridge itself on Home Assistant OS. If you already run the bridge elsewhere, point the integration there.

The add-on is installed locally from the supplied source. It and the integration serve different purposes; you still configure the integration to expose entities.

Install and configure

You need a P1S on your LAN, its access code, and a host running Python 3.12 or newer—or the supplied container / Home Assistant add-on setup.

  1. Prepare the printer. Use LAN-Only Mode and Developer Mode where offered. Review the firmware and access-code limitations in the compatibility notes.
  2. Start the bridge. Follow the setup guide, configure a bridge API key, and register your printer with its local address and access code.
  3. Open the dashboard. Connect a browser on your network to the bridge, then add Home Assistant or another client when needed.
GET THE SOURCE
git clone https://github.com/thereprocase/bambu-bridge.git
cd bambu-bridge

Open source / documented boundaries

Live view in 0.5.0. The dashboard streams every camera frame at the printer’s own rate and reconnects automatically. The 3D viewer opens print toolpaths directly and prepares running jobs in the background.

AGPL-3.0-only. Source, installation guides and the versioned release are public. Third-party notices are retained.

Preview images use the actual application with synthetic data and an original procedural sample model. They are illustrations of the interface, not a live printer session. Automated TLS tests and live P1S protocol checks are recorded separately. Native Orca support is a preview; a completed print through the installed Orca UI remains unverified. Firmware compatibility depends on the documented LAN setup.