Short answer
Controlling 3D printers remotely and safely means keeping printers off the internet, sending commands through an agent on the farm, and tying every physical step to a separate human confirmation. In AMENT Hive the Farm Connector talks to printers on the local network and connects out only to Hive; uploading a file and starting a print are separate confirmations, commands that are not delivered within 2 minutes are dropped, and the AI can never issue them. Live monitoring works; sending and remote commands are live but still being validated on real printers.
Key takeaways
- Never expose a printer to the internet; let an app at the farm connect outwards only.
- Uploading a file and starting a print should be two decisions, and the right to start kept narrow.
- Just before a start, re-check the plate, the printer's state, the filament and the file's target printer.
- A command that is not delivered in time should never run later, and every request should be logged.
- In Hive, sending and remote commands are live but being validated on real printers; do your first runs standing at the printer.
What are the risks of controlling 3D printers remotely?
Remote control is tempting: start a print from home in the evening, give a printer that finished at night its next job, see a problem from a trade fair and pause the print. But a 3D printer is a machine with heaters and moving parts. The result of a remote command happens in a room with nobody in it.
- Exposing the printer: forwarding a router port to reach the printer's web interface opens that interface to the whole internet.
- A forgotten part on the plate: a remotely started print tries to print on top of this morning's plate.
- Wrong file, wrong filament: a file sliced for another printer, or a spool in the wrong colour, costs a whole plate.
- A command that arrives late: when the connection drops, a queued "start" can run hours later, after everything has changed.
- Nobody knows who did what: when several people can reach the same printer, nobody can tell afterwards why a print stopped.
A good remote setup closes these risks with rules. Below we describe those rules and how AMENT Hive applies them, and for each part we say plainly what has and has not yet been tried on real printers.
The Farm Connector: connected without exposing printers
The Farm Connector is a small app installed on a computer that stays on at the farm. A Mac mini, an old laptop or a small Linux machine will do. It talks to printers on the local network and connects outwards only to Hive, over encrypted HTTPS. Nothing from outside opens a connection into the farm network, and no port forwarding is needed.
- 1
Install and pair
Download the app from the Connector page in Hive, open it and approve "Connect this Mac" in your browser. The pairing code works once and expires quickly.
- 2
Scan the network
The Connector finds printers on the local network by itself. Klipper, Creality and Snapmaker printers are added without an access code.
- 3
Add Bambu printers
On each Bambu printer's screen turn on LAN Only and Developer Mode, type the access code it shows into Hive's bulk-add table, and save them all at once.
- 4
Confirm the link
A device the Connector reports does nothing until you link it to a printer in Hive.
From version 0.12 the Connector installs signed updates by itself and rolls back if a new version fails. Because updates are signed, harmful code cannot be pushed to Connectors even if the Hive server were compromised. Keeping the computer awake needs the owner's explicit approval. If the Connector drops or a printer becomes unreachable, Hive shows an alert. The Mac app and Linux setup are live; the Windows Connector has not yet been tried on real hardware (🧪).
Which printers are supported, and how far?
Monitoring a printer and sending it files and commands are different things. The table shows what Hive does on which printers today, and whether it has been tried on a real printer.
| Printer | Live monitoring | Sending and starting | Pause, resume, stop |
|---|---|---|---|
| Bambu Lab A1, A1 mini, P1S, P2S, X1, H2D | ✅ | 🧪 FTPS + MQTT, with AMS slot mapping | 🧪 |
| Klipper / Moonraker printers | ✅ | 🧪 through Moonraker | 🧪 |
| Creality K2, K2 Plus, Hi | ✅ | 🧪 through Moonraker | 🧪 |
| Snapmaker U1 | ✅ | 🧪 through Moonraker | 🧪 |
| Creality K1C (stock firmware) | ✅ monitoring only | Not supported | Not supported |
Live status shows progress, time remaining, temperatures, errors and loaded filaments. Camera views are available on Creality, the Bambu A1 and P1 series and Moonraker cameras; frames are only fetched while someone is watching, and the Connector never writes them to disk.
Sending files to printers: why two separate confirmations?
The most important rule of remote printing is that putting a file on the printer and starting the print are not the same button. An upload is preparation you can undo; a start switches on heaters and moves the toolhead and bed.
- Preparation: Hive or the assistant picks the printer, checks the filament, slices the file for that printer if needed and prepares a proposal card. This step has no physical effect.
- First confirmation, upload: a person presses "Upload to printer". On Bambu the file goes over FTPS and the AMS slots are mapped; on Klipper it is uploaded through Moonraker. Nothing starts.
- Second confirmation, start: only an owner or production manager can press "Start print". The command is handed to the Connector once.
- Confirmed by the printer: Hive shows "Printing" only when the printer itself reports that it is printing this file. "Command sent" and "printer printing" are different states.
Pre-start checks
The moment you press Start, the server runs these checks again. If any one fails, nothing starts, and you are shown what is missing and, where possible, a one-tap fix.
- Is the plate clear? Someone must have confirmed it was cleared after the last print; ticking the box is logged as "build plate cleared".
- Is the printer idle, online, and is its latest report fresh?
- Does the loaded filament match the material and colour the file needs?
- Was the file sliced for this printer model, and is the file type right for it?
- Is another plate shown as printing there, or is one of the orders on the plate on hold?
Remote pause, resume, stop and calibration
Once a print is running, the remote actions people need most are pausing or stopping it when they spot a problem. In Hive these are buttons on the printer panel that only appear when they apply right now.
- Pause: only while the printer is printing. It pauses at a safe point; the part stays on the plate and the heaters may stay on.
- Resume: only when the print is paused. Fix the cause first: filament loaded, nozzle clear, nothing in the way.
- Stop: while a print is running or paused. This cannot be undone; the unfinished part stays on the plate and has to be removed by hand.
- Clear error (Bambu): after you have fixed the problem, clears the error message on the printer's screen. It does not fix the cause, and a paused print stays paused.
Pause, resume and stop work on Bambu and Klipper/Moonraker printers, not on the stock Creality K1C, and need an up-to-date Connector. All of them are live but not yet tried on real printers (🧪). When a printer reports an error code, Hive explains what it means and what to do in plain language, and when a Bambu printer pauses itself because of a problem you get a notification. Those explanations are 🧪 as well. For the common faults themselves, see our troubleshooting guide.
Remote calibration: the strictest conditions
Calibration moves the toolhead and bed, and the nozzle touches the plate. On Bambu you can run bed levelling and vibration compensation (plus motor noise calibration on the A1 and A1 mini); on Klipper, homing and a bed mesh. That is why it has the strictest conditions of any command:
- The printer must be idle and not in maintenance.
- The Connector must be online, and the printer's latest report no more than a couple of minutes old.
- Someone must have checked at the printer and confirmed the plate is empty.
- There must be no file on its way to that printer and no started plate on it.
Safety rules: delivered once, 2 minutes, fully logged, no AI
Every remote command follows the same rules. They are enforced on the server, not in the interface, so it does not matter which app you press the button in.
| Rule | What it means |
|---|---|
| Permission | Only an owner or production manager can start prints or send remote commands, by confirming in the app. |
| Live check | The server re-checks the printer's current state every time; pause, for example, only works while printing. |
| Delivered once | The command is handed to the Connector once, and the Connector acknowledges it. |
| 2 minutes | If a command does not reach the Connector within 2 minutes it is dropped and never runs later. |
| Logged | Every request, refused ones too, is recorded with who asked and when. |
| Short command list | No jogging, no temperature changes, no firmware restarts, no hand-typed G-code. |
The AI can never issue these commands
Hive's assistant can read your printers, explain an error, and prepare a print with an approval card. It cannot upload a file, start, pause or stop a print, run a calibration or clear an error. After explaining an error, the most it can do is show you the right button. The same limit applies when you connect an outside app such as Claude over MCP. Camera failure detection only reads the camera and tells you; it never stops a print on its own.
Field validation: what has been tried, and what has not
Remote control is the area of Hive where we move most carefully. Live monitoring, the Connector, finding printers on the network and the filament view work (✅). The following are live but have not yet been tried on real printers (🧪):
- Sending files to and starting prints on Bambu printers
- Starting prints on Moonraker printers
- Writing a slot's colour to the printer, and Bambu's "Try code" button
- Remote pause, resume, stop, clear error and calibration
- Plain-language error explanations and pause-on-error notifications
- The Windows Connector
The first runs will happen on our first farms, with the farm owner watching. If you would like to do those runs together on your farm, start a 14-day free trial of Hive; we can set it up and do the first sends with you, standing at the printers.
Frequently asked questions
Do I need to expose my printer to the internet for remote control?
No. The Farm Connector talks to printers on the local network and connects outwards only to Hive, over encrypted HTTPS. You do not need port forwarding on your router or to open the printer's interface to the outside.
Can Hive's assistant start a print for me?
No. The assistant can prepare a print and show an approval card, but it cannot upload files, start prints or issue commands such as pause, stop or calibrate. Each of those steps is a person's confirmation in the app.
If the internet drops, will a waiting command run later?
No. Starts and remote commands that do not reach the Connector within 2 minutes are dropped and never sent later. By the time the connection returns the printer may be in a different state, so old commands are not kept waiting.
Why do Bambu printers need Developer Mode?
Bambu only lets third-party software send prints over the local network when Developer Mode is on. In that mode Bambu Handy and the Bambu cloud do not work. The rule comes from Bambu and applies to every third-party tool working on the local network.
Have Hive's remote control features been tested on real printers?
Live monitoring and the Connector work. Sending files, starting prints and remote commands such as pause, stop and calibration are live but not yet tried on real printers; the first runs will happen on our first farms with the owner watching.