Owner
Private toolingThe other half of the queue. What friends have sent, the file itself, and the states a job moves through: from a phone standing next to the machine instead of from a terminal.
The queue runs itself between prints. A part that arrives is sliced and started on its own: as long as this page knows the plate is empty. Nothing here can see the bed, so that one fact has to come from you, once per part you lift off.
This machine is gone
The plate
Checking…Reading the machine…
Why this is a button and not something the printer knows
No camera, no sensor and no field in the printer's protocol reports what is lying on the bed. A finished part sits there for as long as nobody lifts it off, and Idle and Finished are job states, not plate states. Bambu's own cloud dispatched queued jobs onto occupied plates in August 2023 and bent nozzles doing it.
So the claim comes from you, and it lasts until something prints on that plate: because printing on it is the only thing that can make it false again. One tap per part removed, not one per job. The same button is on every "print finished" notification, so the usual place to press it is your lock screen.
Starting a print also needs Developer Mode on at the machine. That requires LAN Only mode, which costs Bambu Handy, cloud printing and over-the-air firmware updates, and switching it on changes the printer's access code. With it off the printer accepts the file, says yes, and never starts.
Filament
–Read off the printer's own tags. Describe a slot yourself when it is holding something the printer cannot identify: after changing a spool, press Refresh rather than waiting.
Where these numbers come from
Each slot shows a Bambu filament id, because that id is what the slice stamps into the file, and it is the only reason a job can go to a particular tray instead of the spool on the back. Remaining comes off the tag as well: no tag, no percentage, rather than a hopeful 100%.
Your description wins over the printer's until you reset it, and each card says which of you it is quoting, field by field.
Reading the AMS…
Waiting
–Drag a card by its grip to reorder: the top one prints next. Slicing and starting happen on their own; you only step in to change the order or to overrule a verdict.
Which verdicts are the machine's, and which are yours
When the printer reports FINISH or FAILED against a job this hub started, the job closes itself and the notification goes out. It only ever moves a job out of printing, never back in.
What it cannot do is tell a good print from a bad one. A part that came off the plate at layer 300 finishes the file and reports FINISH like any other, and this printer latches that state: the agent's log holds 414 consecutive FINISH reports over 6 h 55 m with the part still on the bed. So Done and Failed stay on a printing card, because you are standing in front of it and it is not.
A print you started by hand is never closed automatically: the machine is reading its own filename off the SD card, not one the hub gave it. Stopping a print closes its job as failed, because a stopped print produces no part. Keyboard: focus a grip, arrow keys to move, Home and End for the ends, Escape to abandon.
Reading the queue…
Camera
Not knownA still every few seconds while something is printing. The last frame of each finished part stays on its row under Closed.
Waiting for the queue…
Why stills, and what the badge is telling you
The printer serves its camera over RTSPS on port 322 and no browser can play RTSP, so the machine grabs one frame at a time with ffmpeg and posts it here. Frames are only ever taken while the printer is running or paused: a camera pointed at a bed in a house is not a webcam.
Three things have to agree before there is a picture: this switch, ALLOW_CAMERA in the machine's own config, and LAN Mode Liveview ticked on the printer's screen. When one of them is missing the badge and the panel say which: the machine reports its own reason rather than leaving you to guess between them.
The time under a frame is when it arrived, not when the shutter went; nothing on the wire carries that. The hub refuses to serve a live frame older than about three minutes, so what you see is inside that window, and a refresh that stops getting through is called out rather than left looking live.
What it has cost
–Over prints you have closed out as done, and nothing else.
Reading the ledger…
Nobody has had anything printed yet.
Stays in this browser. Never sent to the hub, never stored beside anybody's job.
How the totals are worked out, and why this is not a bill
Only prints closed as done count. Filament is the slicer's weight at the hub's price per gram; electricity is the printer's rated draw across the estimated hours. Kept apart because they are not the same size: filament is worth saying out loud, electricity is pennies beside it.
It is an invitation, never a charge. Nothing here can take money and no total is a debt. The number exists so a friend who wants to cover their own filament has somewhere to send it, and so you never have to be the one who brings it up.
Notifications
Not knownFree push to your phone via ntfy, no account, no sign-up. The machine has its own topic already; you only have to subscribe to it once. Treat it like a password: anyone who knows the string reads every push.
- Install ntfy from your phone's app store.
- Add a subscription and paste in the topic below.
- Tap Push a test. Your phone should buzz.
Replacing it stops the old one working immediately: use that if the string has been seen by somebody it should not have been. You will have to re-subscribe on every phone.
What comes through here
A part arriving, a part sliced and ready, a print starting, a print finishing or failing, and the plate being confirmed clear: in that order, so a glance down the notifications reads as what the machine did. Failures that need hands (a slice that did not come back, a send that did not start) come through too.
The print finished push carries a Cleared the plate button, so the whole cycle can be run from a lock screen. That button holds a single-use token, never the owner code: a notification body sits on ntfy's servers, and the owner code opens this console, the queue and the machine's own deletion.
The code your friends type
Pick a tierSomething they can remember and say out loud. Capitals, spaces and hyphens are all ignored – WordWord, word word and WORD-WORD would all be one code.
Friends will type –
What you are trading away, and what still protects you
A code you invented is easier to guess than one the hub invented, and there is no way around that. A generated one is two words out of 1024: about a million combinations. A chosen one is worth however unlikely it is that somebody thinks of it.
What stands behind it: eight wrong guesses from one address and that address is refused for fifteen minutes, and you get a push the first time it happens. A few hundred obvious codes are refused outright before they can be saved. And a stolen friends code buys a place in your queue and nothing else, no filenames but their own, no controls, no way into this console.
Your personal code cannot be set here, deliberately. That one opens this page and can delete the machine and every job on it, so it stays a generated forty-bit code nobody invented. The old friends code stops working the moment you save; friends' existing job links are separate credentials and keep working.
Closed –
Nothing closed yet.
Remove this machine
–This cannot be undone, and there is no export first. The queue goes, every stored model and every sliced G-code goes off the disk, the filament library goes, every stored camera frame goes, the machine's status history goes, and the machine itself stops existing on the hub: the drop page will not list it and the setup code that claimed it is long dead. Friends' job links stop working in the same second.
Counting what is here…
Why the slug, and what you get back
The slug is the one string specific to this machine that is not a credential, so typing it is a deliberate act that cannot be arrived at by a mis-tap. It travels in the request body too, and the hub refuses outright if the two disagree: this page arming its own button is not what makes the delete legal.
The counts above are what this console has loaded: the hub serves the last 500 jobs. The authoritative numbers are the ones the hub reports back after the delete, verified by re-reading the database and the disk. They should be zero in every column, and if any come back non-zero this page says so instead of congratulating you.
It refuses while the machine is busy: a print the printer is reporting now, or a send or stop the machine is still working on. It is the machine's word that counts, not a row here that still says printing, so a printer that has been in a cupboard since June can be removed however many jobs nobody closed. Afterwards you are signed out, because the owner code lived on the row that just went.