github maziggy/bambuddy v1.3.3b1-daily.20261120
Daily Beta Build v1.3.3b1-daily.20261120

pre-release34 minutes ago

Note

This is a daily beta build (2026-11-20). It contains the latest fixes and improvements but may have undiscovered issues.

Docker users: Update by pulling the new image:

docker pull ghcr.io/maziggy/bambuddy:daily

or

docker pull maziggy/bambuddy:daily


**Tip:** Use [Watchtower](https://watchtower.nickfedor.com) (image `nickfedor/watchtower`) to automatically update when new daily builds are pushed.

Added

  • Print notifications can name who sent the job (#3584, requested and contributed by abezukor in #3601) — Print started, completed, failed and stopped notifications have two new template variables: {submitted_by}, the user who sent the job from the web UI or from a slicer signed in with their personal access code, and {submitted_by_email}, that user's email, so a webhook bridge can turn the user into a chat mention. Both are empty when nobody is known, such as a print started on the printer itself. The email is only filled while an admin turns on Submitter's email in notifications under Settings > Notifications (off by default): users who can edit templates and providers can't otherwise read user emails. Wiki updated.
  • A Connect slicer page for users without Settings access (#3602, requested by paulleonartcalvo) — Personal slicer access codes are meant for every user, but they, the virtual printers and the CA certificate were only in Settings > Virtual Printer, which needs Settings access. A new Connect slicer page, from the account menu in the sidebar (the person icon, which now also holds Change password), shows a signed-in user their access code, the virtual printers they may send to with it, with address, serial number and model, where their files go and whether the slicer shows a printer's live status, and the CA certificate with its installer. It lists exactly the virtual printers the sign-in accepts the user's code for. Administrators can add instructions in markdown in Settings > Virtual Printer, e.g. "connect to the VPN first", and send users the page's link. The CA certificate and its installer can now be fetched by any signed-in user; they only hold the public certificate.
  • Personal access codes show who sent a file to a virtual printer (#1430) — A slicer signs in to a printer with one access code, so a virtual printer never knew who sent a file: in a school or makerspace, queue jobs and files had no owner. With auth on, every user now has a personal access code, at the top of Settings > Virtual Printer (copy it, or make a new one, which retires the old). Entered in Bambu Studio or OrcaSlicer instead of the virtual printer's own code, it works on any virtual printer in File Manager, Review or Queue mode, and what that slicer sends is the user's: the File Manager file, the queue jobs (which wait for a reviewer when the user's jobs must) and, in Review mode, the pending upload, whose file stays the sender's when someone else approves it. Each sign-in checks the user's account is active, that they may upload to the File Manager (plus queue jobs in Queue mode) and, for a virtual printer with a target printer, that the printer is one of theirs and they may see it, so a change of permissions or a new code takes effect at once. Sending files is all a personal code allows: the slicer's commands to the target printer (stop, pause, G-code, AMS) go through only for users with the printer control permission, checked at every command. An upload waiting for review keeps its own copy, so a later file of the same name can't replace it. The virtual printer's own code keeps working as before, without an owner. Not for Proxy mode. The slicer's camera view through a virtual printer with a target printer works with a personal code too, for a user allowed to watch that printer's camera: the printer checks the camera's code itself, so the virtual printer now signs the slicer in there with the printer's own code, and on port 322 the slicer sees the virtual printer's certificate (the one it already trusts for MQTT and FTP) instead of the printer's. The virtual printer's FTP sign-in now refuses an address for a minute after five wrong codes, as its MQTT sign-in already did, and on both a good sign-in no longer resets the count.
  • A script adds the virtual printer certificate to the slicers — Bambu Studio and OrcaSlicer only connect to a virtual printer whose certificate is in their printer.cer file, and every slicer update or reinstall puts the original file back, so the certificate had to be added by hand again. The Slicer certificate card under Settings > Virtual Printer now downloads a script for Windows or Linux / macOS with this Bambuddy's certificate already in it. It finds Bambu Studio and OrcaSlicer, adds the certificate, and keeps the original file next to it. It changes nothing where the certificate is already there, and it removes an older certificate of the same Bambuddy, which would otherwise stop the slicer from connecting. On Windows it is a double-click: it asks for administrator rights, and it installs a task that adds the certificate again at every start, at every sign-in and once an hour, so a slicer update no longer breaks the connection (/uninstall removes the task). On Linux and macOS it runs with bash, and is run again after a slicer update. Wiki updated.
  • A virtual printer can be an H3C (#3442, requested by mgera-git) — Settings > Virtual Printer now offers the H3C as a model. Bambu Studio recognises a printer by its serial, so a virtual H3C gets one like a real H3C (32X...). A proxy virtual printer for an H3C takes the model from its target.
  • A smart plug's temperature auto-off can wait for the bed (#3464, requested by EmcetPL, contributed by Keybored02 in #3539) — With Turn Off Delay Mode set to Temp, a plug turned off once the nozzle cooled, which takes a few minutes, while the bed stays hot much longer: a plug that powers the printer cut it before the print could be taken off a cool bed, and before the Bed Cooled notification was sent. Temp mode now has Wait for: Nozzle / Bed, and the bed has its own threshold (35 °C by default, the Bed Cooled notification's default). Existing plugs keep waiting for the nozzle.
  • Choose which notifications get the camera photo (#2877, requested by HappyPuppy21) — Attach Photo on a notification provider sent the snapshot with every event that has one, so a channel that should show the finished print also got a photo at the start and at 25, 50 and 75 percent. With Attach Photo on, the provider's settings now list the photo events it sends, and unticking one sends that event without the photo. Every event keeps its photo until it is unticked, and the provider card names the events that go without one.
  • BIQU Panda Breath on the printer card (#1466, requested by embed-3d) — A Panda Breath chamber heater with firmware 1.0.4 or later can connect to an MQTT broker, and Bambuddy now follows it there. Under Settings > Network > MQTT Publishing, turn on BIQU Panda Breath; it uses the broker set there, and lists each Panda Breath that reports with the printer it is bound to. The printer card of that printer gets a Panda Breath tile with the chamber temperature it reads and its target; clicking it turns the heater on or off, picks Auto, Always on or Drying, and sets a target from 0 to 60 °C. The tile stays on the card while the printer is switched off, since the heater keeps running. The device is matched by the printer serial number it reports, so it needs to be bound to its printer in its own web interface. Changes need the printer control permission for that printer. Not tested on a real device yet. Wiki updated.
  • Limit which filaments a group may print with (#3522, requested and contributed by paulleonartcalvo in #3567) — A group can now be limited to some filaments, as it can to some printers (#1727). In the group editor, Limit filaments under Filament access turns it on, with rules that either Block these filaments or Allow only these filaments. A rule names a material type (PETG, matched exactly, so PETG-CF is a different one) or a slicer filament ID (GFG03 for Bambu PETG Matte, the ID an AMS slot reports). A member may use a filament if any of their limited groups allows it; a user in no limited group, an admin, and every user with auth off are not limited. Queueing a file that needs a filament the user may not use is refused with the filament named. The print dialog says so before submitting, greys out the slots the group can't use and never picks one automatically. The queue never sends a job to a slot holding such a filament: it picks another slot, or holds the job with the reason on its row and starts it once the rules or the loaded spools allow it. That covers jobs from every source, including webhooks, pipelines and virtual printers, and "Print anyway" does not bypass it. Wiki updated.
  • Every user can choose the interface language (#3623, requested by balin77) — The language picker was only in Settings > General, which needs Settings access, and it also changed the language of the whole install. A user without Settings access, such as a helper who only manages spools, could not switch the interface to their language. The account menu in the sidebar (the person icon) now has a Language picker; with authentication off, a globe icon in the sidebar footer opens it. It changes the language of this browser only, needs no permission and never changes the install-wide setting. The picker in Settings > General is now called SpoolBuddy display language, which is what it sets; it still switches the interface of the browser it is changed in.
  • Optionally run queued jobs whose filament is loaded first, with a maximum wait (#3587, requested and contributed by balin77 in #3627) — A job whose filament was not on its printer (wrong colour or type, or not enough left on the spool) was staged and waited for someone to press Start, and a printer could stand idle while jobs behind it would have fitted. Settings > Workflow > Queue & Dispatch > Loaded Filament First now skips such a job instead: jobs behind it that fit run first, the queue order stays as it is, and the job starts by itself once its filament is loaded. Its row reads "Waiting for filament: … · priority in N h". After the Maximum wait (48 hours by default, counted from when the job was queued or its scheduled start; empty for no limit) the job gets priority: its printer (for an "Any model" job, the first idle printer in the configured printer order) is kept free for it, and the Job Waiting notification is sent once; without a limit it is sent once when the job starts waiting. A printer behind an auto-on smart plug is not switched on for a job whose filament its last-known trays don't have. Print Anyway, staged jobs and the plate-clear confirmation behave as before. Off by default, so nothing changes until it is switched on; queue rows now show the filament-wait reasons translated.

Changed

  • Virtual printer cards start collapsed — Settings > Virtual Printer opened every virtual printer's card with all its settings, so a few of them filled the page. Each card now shows only its header (name, mode, model, status) until it is clicked.
  • Virtual printers put uploads in the File Manager, not the archive — An archive is a print that happened, but a virtual printer archived every file the slicer sent, in Archive, Review and Queue mode, before it ever printed. Uploads now go to the File Manager, and the archive gets the file when it prints, like any other File Manager print. Archive mode is now File Manager mode; virtual printers set to it switch over on upgrade, and archives they created before stay as they are. Each virtual printer card has a File Manager folder (by default a shared top-level folder named Virtual Printer; external folders can't be picked). The same file sent again under the same name into that folder doesn't make a second copy. Review mode stays: pending uploads now wait at the top of the File Manager page (the sidebar badge moved there too), and Add to File Manager stores them in the virtual printer's folder with their tags, notes and project (approving now needs the library:upload permission as well as queue:create, since it adds a file); the panel is translated now too. Queue mode stores the file and queues it from there, and a new switch, Remove from File Manager once it prints (off by default), takes it out of the File Manager when its print starts. With Save AMS mapping on, the slicer's tray pick still reaches the archive for reprints: the queue job keeps it until the print creates the archive, shows the saved-mapping badge meanwhile, and offers it under Mapping when edited. The virtual printer's archive-name setting (file name or 3MF title) applies to the archive made when the print starts. Wiki updated.
  • A queue virtual printer shows where its jobs go, and its target can be cleared — In Print Queue mode a virtual printer without a target printer sends each job to the next free printer of its model, but the card's target list only said "Select a printer...", and once a printer was picked there was no way back. The first entry now reads Any available [model] and switches the virtual printer back to that, and a line under the list says where the jobs go. The access code stays the same, so the slicer stays bound. In the other server modes the entry reads None; proxy mode still needs a printer. Wiki updated.
  • The "job assigned" notification is sent once the job can start on its printer (#3522, contributed by paulleonartcalvo in #3567) — An "Any model" job was announced as assigned the moment the queue picked a printer for it, before the queue had mapped its filaments to that printer's slots. The notification now follows that step. For every user, also one without filament rules, a job that fails right after the assignment because its filaments can't be mapped on that printer is no longer announced as assigned first; it sends the failure only. A job held by its creator's filament rules is given back to the pool without the notification, so it is not sent again on every pass of the queue.
  • With billing on, a reprint is charged at the spools it prints with (#3580, requested and contributed by paulleonartcalvo) — An archive keeps the cost of its first print (#1378), and every later print of it was charged from that figure: a reprint on a spool bought at another price, or mapped to another spool in the print dialog, was billed at the old price. Each print is now priced when it starts, from its plate's planned filament at the spools mapped for it, and charged from that; a failed or cancelled print is charged its share of it, as before. The archive card still shows the first print's cost. A first print of one plate of a multi-plate file is now charged from that plate's own figure too, not from the whole file's cost scaled to the plate's share. A print with no spool mapping to price it from is charged from the archive's cost, as before. The budget a queued reprint reserves is priced the same way when the queue item has a spool mapping, so the reservation and the charge agree; without one it is the archive's cost until the queue maps the job's filaments at dispatch and prices it again. In Spoolman mode the reservation finds a spool as the charge does: by its RFID tag first, then by its slot assignment. In the built-in inventory a spool priced 0 counts as free, so a print only on such spools is charged nothing and reserves nothing; in Spoolman a price of 0 means the spool has no price, and it is charged at the default rate. A built-in spool with no price is not free: it is charged at the default rate, and with a default rate of 0 it does not price the print, which is then charged from the archive's cost. A completed print with no measured cost is logged in the Print Log at what it was charged. A print whose price was not worked out by the time it ends (it failed within seconds, or Bambuddy restarted) is priced at its end. With billing off, none of this is worked out and Spoolman is not asked for prices when a job is queued.

Fixed

  • About 400 texts that were hardcoded in English are translated, and the language check catches new ones (#3638, reported by mohan456-wqs) — Many labels, tooltips, placeholders and messages were written straight into the screens instead of going through the translations, so they stayed English in every language. Among them: the printer card's temperature, fan and nozzle controls, jog buttons and Build Plate Check, the camera viewer's buttons and reconnect message, the archive filters, collections, list headers and export menu, the file manager, the filament selector in the print dialog, tag management, the archive comparison, the timelapse editor, the API browser, the log viewer, the keyboard shortcuts, the print calendar and filament trends, the dashboard widget controls, external links, project pages and many toast messages. They now come from the language files in all 16 languages. Sentences that wrapped a number, like "Reconnecting in 5s...", are one text with the number in it, so each language can put it where it belongs. npm run check:i18n now also fails when a screen shows English text that does not go through a translation; brand, model and unit names stay allowed.
  • 193 texts that were missing from every language are translated, and the language check catches new ones (#3631, reported by mohan456-wqs, Simplified Chinese contributed in #3637) — The code used 193 text keys that no language file had. Most of them carried an English fallback, so they stayed English in every language: parts of the SpoolBuddy pages (settings, diagnostics, inventory, AMS, writing tags), the System page, Support, smart plug search, AMS history, wallet messages and more. 32 had no fallback, so the screen showed the raw key instead of a text, for example in the profile compare dialog, the preset templates, the smart plug search fields and the Spoolman save-failed message. All 193 are now in all 16 languages. The language check (npm run check:i18n) only compared the language files with each other, so it never noticed a key that none of them had; it now also fails when the code uses a key that is missing from the English file.
  • A virtual H2C reports the right model to the slicer — The H2C comes as two models: older units (O1C, serials starting 094, like the H2D) and those from 2026 (O1C2, serials starting 31B8B). Bambu Studio only syncs printer information with a virtual printer that reports the printer's own one, and says "Printer not connected" otherwise, but the virtual printer list showed both as "H2C". The list now names each H2C entry with its serial family, and says to pick the one whose serial starts like the printer's. A proxy virtual printer takes the right one from its target printer's serial, and a virtual O1C2 now has a serial starting 31B8B like a real one, instead of the H2D's 094, so the slicer also shows it the H2C's HMS texts. An existing virtual O1C2 gets a new serial with this: add it in the slicer again once.
  • A slicer whose clock is a little behind can connect to a virtual printer again — A virtual printer makes a new certificate every time Bambuddy starts, and it was valid only from that second on. Bambu Studio on a computer whose clock ran even a minute behind saw a certificate that was not valid yet, refused it, and reported only "-1" when connecting with the access code, which looks exactly like a missing certificate. New certificates now start a day back (a printer certificate never before its CA), so a restart no longer locks out such a computer. Nothing needs to be imported again.

Security

Don't miss a new bambuddy release

NewReleases is sending notifications on new releases.