Manual contents

🔌 Local network printers

In 30 seconds

Over the local network, BolloPrint talks to your printers inside your workshop, through the local agent, without going through the manufacturer's cloud.
It's the route for almost every brand, the one that gives you the camera and, on the machines that allow it, pause, resume and cancel.
There are three steps: install the agent on a computer in the workshop, connect it to your account and add the printers, which nearly always show up on their own.
There's no need to open ports on the router: the agent calls BolloPrint, not the other way round.

Over the local network, BolloPrint talks to your printers directly in your workshop, without going through any manufacturer's cloud. That needs a go-between inside your network: the local agent.

It's in Settings → Printers, Local agent tab.

Why it's the recommended route

It works with almost every brand. Bambu Lab, Prusa, Elegoo, FlashForge, Anycubic and Creality (in beta), Snapmaker, and the ones running Klipper underneath (QIDI, Sovol, Voron, RatRig…). The model-by-model detail is in Compatible printers.
You can send commands: pause, resume and cancel the print in progress, on the machines that allow it (Bambu machines, with Developer Mode turned on: see Connection types).
You get a camera: live from the printer's page (as video, where the camera provides it), a photo right away when you ask for it, and a final photo of how each print turned out. If the job doesn't come with a thumbnail, also a photo of the inside every few minutes while it prints.
It doesn't depend on the manufacturer. Not on their cloud working, nor on them keeping their service open.
It survives internet outages. If your connection goes down, the agent keeps reading the printers and stores what happens; when the line comes back, it sends everything. You don't lose the history for those hours.

The agent doesn't open your network to anyone. It's the one that calls us, so there's no need to open ports on the router, have a fixed IP, or configure anything on the firewall. It works just the same behind an ordinary home router.

The three steps

Install the agent on a computer in the workshop that's always switched on: a NAS, a Windows PC, Home Assistant or any computer with Docker.
Connect it to your account: in one click if it's a package or an installer, or by pasting its manifest if it's Docker or Kubernetes.
Register the printers it's going to manage.

Steps 1 and 2 depend on where you install it, and each option has its own page: pick yours in The local agent. Here we carry on with step 3.

Adding printers

The ones that show up on their own

The agent looks for printers on your network and the ones it finds appear in the Local agent tab, at the end of Printers on the local network, under Found on the network (with more than one agent, "Found by" and each one's name), with their brand and model. Click Add and that's it. If it isn't yours or you don't want it, Ignore. When there are any, you'll also see a notice above the tabs.

If it's a printer you already have through Bambu Cloud, it says so ("It's "P1S-02", which you already have through Bambu Cloud") and the button is Also connect over LAN: it doesn't create a new printer, it adds the local route to the one you already have.

Some will ask you for an access code before connecting; the card itself tells you whether it's going to.

A printer may also appear marked as Coming soon: we know what it is, but we can't connect it yet. If it's one you need, tell us — it helps us decide the order.

The Bambuddy virtual printer

If you use Bambuddy to manage your Bambu Lab printers, its print queue presents itself on your network as one more printer, and the agent finds it. We recognise it and it carries the Virtual · Bambuddy label: in Found on the network, when you add it, on its card, in Settings → Printers and on its page.

It is not a machine: it is Bambuddy's print queue.
What it shows is a copy of the status of another of your printers, which may be out of date.
You can still add it, but it takes up a slot in your plan like any printer. If you don't need it, deactivate it in the Printers tab or disconnect it.

The ones you have to add by hand

If the printer doesn't appear, click Add by IP in Printers on the local network, in the Local agent tab. Not appearing is normal in two cases: when the agent is on a different network from the printers, and when it runs on Docker Desktop. Neither costs you anything: added by hand it works exactly the same, with camera and with controls if that machine has them.

This opens Add printer by IP, which has three steps:

Printer: pick your printer's brand and click Next. Klipper and Other resin printer (ChituBox) are at the end, under Generic. The card decides how we talk to the printer, so watch out for these cases:
- Elegoo swaps the brand list for Which Elegoo do you have?: Saturn, Mars, Jupiter or Centauri Carbon, Neptune 4 (all) or Centauri Carbon 2. All brands takes you back to the list.
- A Snapmaker U1 is Snapmaker, not Klipper.
- A Klipper printer whose brand isn't listed, or a self-build, is Klipper.
- A resin printer with a ChituBox board that isn't an Elegoo is Other resin printer (ChituBox).
If you're not sure which to choose, Not sure? See the list of compatible printers takes you to the list by brand. If your brand isn't listed, the Open a case button is for telling us about it.
Details: fill in what it asks for and click Connect. Required fields carry a red asterisk.
- Which agent connects it?: only shows up if you have more than one agent. The ones that aren't online appear in the list, but can't be chosen.
- Printer IP: you'll find it on the printer's screen (Settings → Network) or in your router. If it uses another port, add it after: 192.168.1.50:5000.
- The printer's code, if that brand asks for one. The field is named the way each brand names it (see the table below).
- Name (optional): whatever you want to call it.
You don't type the model or the serial number: the agent asks the printer for them. At the end, the Remember box tells you what has to be turned on in the printer before connecting.
Connection: you'll see the agent look for the printer at that address and connect to it. If all goes well, click Done and it's in your list. If not, it explains in plain words what went wrong and what to check, and underneath, folded under Show technical detail, is the original message (copy it if you ask us for help). Back takes you to the details to fix them.

This is what each card asks for in the Details step:

Card	What to type
Bambu Lab	LAN access code, required. It's the one the printer shows in Settings → Network → Access code, with LAN Mode enabled.
Prusa	PrusaLink password, required. The printer generates it and shows it in Settings → Network → PrusaLink. It isn't your Prusa Connect password.
FlashForge	Check code, required. It's the one shown in the network menu on the printer's screen, with LAN Only enabled.
Anycubic	It doesn't ask for anything, but first you have to turn on LAN Mode on the printer (Settings → Network → LAN Mode).
Creality	It doesn't ask for anything.
Elegoo → Centauri Carbon 2	Access code (optional). Leave it empty unless you've set a code on the machine's screen (Settings → Network); in that case, type that code.
Klipper, Snapmaker and the brands running Klipper (QIDI, Sovol, Voron, RatRig, Artillery, Two Trees and Elegoo → Neptune 4)	API key (optional). Only if you configured an access key in your Klipper (Moonraker); you'll find it in Mainsail or Fluidd, under Settings → API key. If it's one the agent found and it refused the connection without a key, the field is called Moonraker API key and is required.
Elegoo → Saturn, Mars, Jupiter or Centauri Carbon, Longer and Other resin printer (ChituBox)	They don't ask for anything.

💡 Reserve the IP on your router

If the router changes the printer's address, we look for it on your network again by ourselves, but it'll be down for a while. Reserving its IP by MAC — or giving it a fixed IP — avoids the gap.

Editing or removing a printer

In Printers on the local network, in the Local agent tab, each printer says which agent drives it, and in its ⋮ menu you have:

Edit: change the name, the address, the access code or the agent that manages it. You can also get here from the Printers tab, with Edit local connection in the machine's menu.
Disconnect: the printer stops being connected through this agent.

To stop it counting towards your plan without removing it, switch it off with its switch in the Printers tab.

About Disconnect: if it had another route (for example, the Bambu cloud), it carries on through that one. If this was its only route, it leaves the list and stops counting towards your plan. Nothing is lost: it keeps its number and its history, and if you add it again —because the agent finds it, or by IP— it comes back exactly as it was, even if its IP or its code has changed.

What each status means

Status	What's going on
Online	All good: the agent sees it and is receiving its data.
Connected but not sending data	The agent has connected and the printer isn't telling it anything. Usually the machine only allows a few connections at a time and already has another one open (the phone app, the slicer).
Not responding at that address	Check that it's switched on and on the same network as the agent.
Responds but refuses the connection	Almost always the wrong access code, or LAN mode disabled on the printer.
All of an agent's printers disconnected at once	The problem isn't the printers: it's their agent, which isn't responding. The machines may be perfectly fine. In the Local agent tab, open it with Edit and look at its Status.

Carry on here

🧩 The local agent — where to install it (with a page for each option), how it connects, when it's worth having more than one and what to do when something goes wrong.
🔗 Connection types — what you can do with each family.
🖨️ Compatible printers — whether yours can be connected, and how.